zikunz commented on issue #3549: URL: https://github.com/apache/trafficcontrol/issues/3549#issuecomment-1494920094
@ocket8888 Thank you for your reply! > That's normal, it would only print anything if it fails. > > > Thank you for the clarifications. > commands like `atc trafficops` or `atc trafficportal` seem to be waiting indefinitely. I apologize for the mistake. What I intended to convey was `atc ready --wait trafficops` or `atc ready --wait trafficportal` seemed to be waiting indefinitely. > That would be because Traffic Portal does not listen on either of those ports. Nothing listens on port 60443, so I'm not sure where you even got that. It's _similar_ to port 6443 which _is_ used by Traffic _Ops_ - not Traffic _Portal_. Port 8080 is used by Traffic _Server_. Traffic _Portal_ listens on port 444, so that's where you should look for it. > > You can see all these ports while the containers are running with `docker ps`. Thank you for pointing it out! I was looking at line 27 of https://github.com/apache/trafficcontrol/blob/master/traffic_portal/conf/configDev.js and this caused confusion. However, I tried to visit https://localhost:444/ just now, it could be loaded but I saw the errors in the below screenshot. <img width="642" alt="Screen Shot 2023-04-04 at 04 02 35" src="https://user-images.githubusercontent.com/75139323/229615922-e6271ba4-7c67-47c4-96d6-dcf9f93767c8.png"> > For further help, please reach out in our Slack server. I just sent an email to [email protected] requesting a Slack invite. Thank you so much for your help! -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
