Hi All,
I’m running Solace PubSub+ in a Docker container on an Ubuntu VM using the following command: Inside the VM, I’m able to use TryMe via ws://<vm-ip>:8008
successfully.
docker run -d -p 8080:8080 -p 55555:55555 -p 8008:8008 -p 1883:1883 -p 8000:8000 -p 5672:5672 -p 9000:9000 -p 2222:2222 --shm-size=2g --env username_admin_globalaccesslevel=admin --env username_admin_password=admin --name=solace solace/solace-pubsub-standard
However, when I try to access TryMe from outside the VM, I encounter the following error.
All the required ports (8080, 55555, 8008, 1883, 8000, 5672, 9000, 2222, including 80, 443, and 9443) are open and accessible from outside — I can even telnet to these ports from the host machine.
Could someone please advise if I’ve missed any configuration steps or if there’s a network restriction I should look into?
Thanks in advance!
Hi there, I’m Solly AI, I generate responses to your questions using the power of the Solace Agent Mesh:
Please remember that AI technology can make mistakes so ensure that you read our Disclaimer.
AI Generated responses are a work in progress, your help in evaluating my response would be awesome! If my response makes sense, please mark it as a solution or give a
. If my response doesn’t make sense for your topic, please react to it with a
.
Looking at the documentation, when accessing TryMe from outside a VM running a Solace software event broker in Docker, there are a few key networking considerations:
- When running in Docker, localhost or 127.0.0.1 from inside the container refers to the container itself, not the host machine
- The TryMe interface uses WebSocket protocol (ws://) to connect to the event broker
- Proper port mapping is required between the Docker container and the host VM
To resolve connectivity issues:
- Create a Docker network to enable communication between containers:
docker network create solace-net
- Connect your event broker container to the network:
docker network connect solace-net <container-name>
-
Ensure proper port mapping when starting the container, particularly port 8008 for WebSocket connections
-
When accessing TryMe from outside the VM, use the VM’s IP address instead of localhost
Relevant sources: