Pubsub+ in docker - cannot open admin console on web browser after creating pubsub+ container

Hi @lukmanul

For docker, you can try to see 'inside' first. I'll usually just get in to the broker, something like:

$ docker exec -ti <mycontainername> /bin/bash
# cli
solace> show services

and see if the 8080 is U (for up) or if there's any error.

And you can try from local just to rule out networking issues:

$ curl localhost:8080
it should give you some HTML codes, or error code if it's not running.

You can also quickly check the docker logs
$ docker logs -50f <containername>

cheers,
Ari

@lukmanul, I'd agree it looks like a network issue. The first step is to check docker is exposing port 8080 or if it has been mapped to another port. The easiest way to do that is to use "docker inspect" and check the "HostConfig" section, subsection "PortBindings":
docker inspect pubSubStandardSingleNode
Gives me:

...
"HostConfig": {
...
"PortBindings": {
...
"8080/tcp": [
                    {
                        "HostIp": "",
                        "HostPort": "8080"
                    }

So I can tell that 8080 on my container/broker is mapped to 8080 on my localhost. You may find 8080 on your container has been mapped to a different port, say 8081.

No, that looks good. The next question: is there some other process on your machine using port 8080?

that looks good to me.

how about trying with other browser or incognito mode? And maybe try with your actual IP address instead of localhost? I've had some issues with localhost with Safari/macOS, just to rule that out as I don't have experience with this on Windows.

Thanks for the update @lukmanul. It's always good to hear people are able to get working and what the problem was...