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

PubSub+ Event Broker
1

Hi,
I am testing pubsub+ in docker that I pull from docker hub after that running docker container and open port for admin as well. But when I try to access admin console from http://localhost:8080, it’s nothing happen. So what should I check first to get the issue?

Thanks in advance.
Lukman

2

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

3

Hi @arih,
The port 8080 is actually Up.

image.png
image.png638×150 1.32 KB

I think this is because networking issues. Connection refused.
image.png

Thanks.

4

@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.

5

Hi @TomF,
This is the detail of docker inspect mycontainername command:

image.png
image.png314×413 1.28 KB

am I in the correct path? or any other configuration need to be set?
Thanks.

6

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

7

There is no conflict port on my local PC, I have make sure them by checking listening port running on my resource monitor.

8

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.

9

Hi all,
I got it, it’s running well when I change my IP to http://192.168.99.100:8080 instead of http://localhost:8080. Simply just checking docker info and then got this detail IP :slight_smile:

image.png
image.png869×641 17.1 KB

10

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