[GitHub] [trafficcontrol] smalenfant opened a new issue, #7253: Failed to load default certificate when changing hostname for Traffic Router

[GitBox <gi...@apache.org>]

smalenfant opened a new issue, #7253:
URL: https://github.com/apache/trafficcontrol/issues/7253

   ## This Bug Report affects these Traffic Control components:
   - Traffic Router
   
   ## Current behavior:
   Looks like Traffic Router creates a default self-signed certificate. 2 files seems to be generated:
   
   - keyStore.jks
   - fqdn.crt
   
   When one changes the hostname of the server. A new certificate is not generated and Traffic Router complaints with a few messages like:
   
   ```
   ERROR 2022-12-14T20:11:54.307 [Thread-21] org.apache.traffic_control.traffic_router.secure.CertificateRegistry - Failed to load default certificate. Received class java.lang.NullPointerException with message: null
   ERROR 2022-12-14T20:11:54.308 [Thread-21] org.apache.traffic_control.traffic_router.secure.CertificateRegistry - Failed to initialize the API Default certificate.
   ```
   
   ## Expected behavior:
   
   Traffic Router should regenerate a new certificate that matches the hostname.
   
   
   ## Steps to reproduce:
   
   - Install Traffic Router on a VM
   - Change the hostname of the VM
   - Restart Traffic Router
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org