ocket8888 commented on issue #3549:
URL:
https://github.com/apache/trafficcontrol/issues/3549#issuecomment-1494875984
> upon running `atc ready`, nothing is printed on the console
That's normal, it would only print anything if it fails.
> commands like `atc trafficops` or `atc trafficportal` seem to be waiting
indefinitely.
That is strange - because those aren't valid commands. What _should_ happen
in that case is you get an exit failure code and a usage message. This is what
I see when I try that:
```shellsession
$ atc trafficops
Usage: atc OPERATION
Valid OPERATIONs:
build Build the images for the environment, but do not start it
connect Connect to a shell session inside a dev container
exec Run a command in a dev container
ready Check if the development environment is ready
restart Restart the development environment
start Start up the development environment
stop Stop the development environment
```
> Additionally, attempting to access the Traffic Portal interface via
https://localhost:60443/ or https://localhost:8080/ has not been successful.
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`.
For further help, please reach out in our Slack server.
--
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]
