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

**URL:** <https://community.solace.com/t/pubsub-in-docker-cannot-open-admin-console-on-web-browser-after-creating-pubsub-container/339>\
**Category:** Solace Event Broker\
**Created:** [July 27, 2020, 7:09am UTC](https://community.solace.com/t/pubsub-in-docker-cannot-open-admin-console-on-web-browser-after-creating-pubsub-container/339 "2020-07-27T07:09:42Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![lukmanul](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/lukmanul/32/194_2.png) [@lukmanul](https://community.solace.com/u/lukmanul)\
**Post date:** [July 27, 2020, 7:09am UTC](https://community.solace.com/t/pubsub-in-docker-cannot-open-admin-console-on-web-browser-after-creating-pubsub-container/339/1 "2020-07-27T07:09:42Z")

</div>

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](http://localhost:8080), it’s nothing happen. So what should I check first to get the issue?

Thanks in advance.  
Lukman

---

<div class="post-metadata">

**Author:** ![arih](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/arih/32/130_2.png) [@arih](https://community.solace.com/u/arih)\
**Post date:** [July 27, 2020, 7:30am UTC](https://community.solace.com/t/pubsub-in-docker-cannot-open-admin-console-on-web-browser-after-creating-pubsub-container/339/2 "2020-07-27T07:30:55Z")

</div>

Hi @lukmanul

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

```auto
$ 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

---

<div class="post-metadata">

**Author:** ![lukmanul](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/lukmanul/32/194_2.png) [@lukmanul](https://community.solace.com/u/lukmanul)\
**Post date:** [July 27, 2020, 8:28am UTC](https://community.solace.com/t/pubsub-in-docker-cannot-open-admin-console-on-web-browser-after-creating-pubsub-container/339/3 "2020-07-27T08:28:19Z")

</div>

Hi @arih,  
The port 8080 is actually Up.

 ![image.png](https://canada1.discourse-cdn.com/solace/original/2X/1/15b5545abba25b1382f2c8fd36363c5d2ee789c6.png)

I think this is because networking issues. Connection refused.  
 ![image.png](https://canada1.discourse-cdn.com/solace/original/2X/3/3eec1c7fa9fb87400f2979660b58e10280b2b943.png)

Thanks.

---

<div class="post-metadata">

**Author:** ![TomF](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/tomf/32/1749_2.png) [@TomF](https://community.solace.com/u/TomF)\
**Post date:** [July 27, 2020, 8:46am UTC](https://community.solace.com/t/pubsub-in-docker-cannot-open-admin-console-on-web-browser-after-creating-pubsub-container/339/4 "2020-07-27T08:46:59Z")

</div>

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

```auto
...
"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.

---

<div class="post-metadata">

**Author:** ![lukmanul](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/lukmanul/32/194_2.png) [@lukmanul](https://community.solace.com/u/lukmanul)\
**Post date:** [July 27, 2020, 9:06am UTC](https://community.solace.com/t/pubsub-in-docker-cannot-open-admin-console-on-web-browser-after-creating-pubsub-container/339/5 "2020-07-27T09:06:37Z")

</div>

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

 ![image.png](https://canada1.discourse-cdn.com/solace/original/1X/f7cab13a7ca960b505ec69c7fea5dae160751845.png)

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

---

<div class="post-metadata">

**Author:** ![TomF](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/tomf/32/1749_2.png) [@TomF](https://community.solace.com/u/TomF)\
**Post date:** [July 27, 2020, 9:36am UTC](https://community.solace.com/t/pubsub-in-docker-cannot-open-admin-console-on-web-browser-after-creating-pubsub-container/339/6 "2020-07-27T09:36:39Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![lukmanul](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/lukmanul/32/194_2.png) [@lukmanul](https://community.solace.com/u/lukmanul)\
**Post date:** [July 27, 2020, 10:00am UTC](https://community.solace.com/t/pubsub-in-docker-cannot-open-admin-console-on-web-browser-after-creating-pubsub-container/339/7 "2020-07-27T10:00:41Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![arih](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/arih/32/130_2.png) [@arih](https://community.solace.com/u/arih)\
**Post date:** [July 27, 2020, 10:05am UTC](https://community.solace.com/t/pubsub-in-docker-cannot-open-admin-console-on-web-browser-after-creating-pubsub-container/339/8 "2020-07-27T10:05:35Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![lukmanul](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/lukmanul/32/194_2.png) [@lukmanul](https://community.solace.com/u/lukmanul)\
**Post date:** [July 27, 2020, 10:21am UTC](https://community.solace.com/t/pubsub-in-docker-cannot-open-admin-console-on-web-browser-after-creating-pubsub-container/339/9 "2020-07-27T10:21:11Z")

</div>

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

 ![image.png](https://canada1.discourse-cdn.com/solace/original/2X/7/7ebbd1976f9d3e09c12380acfc1ac54e38f868a9.png)

---

<div class="post-metadata">

**Author:** ![TomF](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/tomf/32/1749_2.png) [@TomF](https://community.solace.com/u/TomF)\
**Post date:** [July 27, 2020, 10:37am UTC](https://community.solace.com/t/pubsub-in-docker-cannot-open-admin-console-on-web-browser-after-creating-pubsub-container/339/10 "2020-07-27T10:37:25Z")

</div>

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