rawlinp commented on issue #4810: URL: https://github.com/apache/trafficcontrol/issues/4810#issuecomment-647796273
TR likely isn't listening on port 53 yet because it is not starting up successfully to due issues in your environment. This issue means it can't connect to your Traffic Monitor to `GET` the CrConfig: ``` WARN 2020-06-19T17:31:56.620 [AsyncHttpClient-Reaper] com.comcast.cdn.traffic_control.traffic_router.core.util.PeriodicResourceUpdater - Failed request http://tm.myawesomecdn.com:80/publish/CrConfig?json: java.net.ConnectException: https://tm.myawesomecdn.com:443/publish/CrConfig?json ``` There are likely errors in the TM error log that indicate why it's not serving TR the CrConfig. Additionally, this error indicates that something is wrong, either with TO or your TR credentials: ``` WARN 2020-06-19T17:31:46.165 [pool-2-thread-1] com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - Failed Http Request to https://ops.myawesomecdn.com/api/1.3/cdns/name/mac_cdn/sslkeys.json Status 401 ``` Make sure your TR user has valid credentials in `traffic_ops.properties`. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
