#support

Accessing Docker Containers on Server via Browser

TLDR Jamshedkhon was unable to access Docker containers running on a server. Syed suggested using the server's IP and checking firewall rules to resolve the issue.

Powered by Struct AI
16
5mo
Solved
Join the chat
Apr 26, 2023 (5 months ago)
Jamshedkhon
Photo of md5-3c955fc368fedc07f9d2587d78e4d4be
Jamshedkhon
09:13 AM
Image 1 for
Syed
Photo of md5-f16c6ead78bebb6489e7ed7b121f5ce9
Syed
08:03 PM
show the output of
docker ps
Apr 27, 2023 (5 months ago)
Jamshedkhon
Photo of md5-3c955fc368fedc07f9d2587d78e4d4be
Jamshedkhon
04:26 AM
Image 1 for
Syed
Photo of md5-f16c6ead78bebb6489e7ed7b121f5ce9
Syed
04:39 AM
as per this image your containers are running. you can open browser and type
http://localhost:3301
Jamshedkhon
Photo of md5-3c955fc368fedc07f9d2587d78e4d4be
Jamshedkhon
04:40 AM
those docker containers are running in server
04:41
Jamshedkhon
04:41 AM
not in my local machine
Syed
Photo of md5-f16c6ead78bebb6489e7ed7b121f5ce9
Syed
04:41 AM
so you can type ip of your server instead of localhost
04:41
Syed
04:41 AM
also check any firewalld, iptables rules, or security group in case of ec2
Jamshedkhon
Photo of md5-3c955fc368fedc07f9d2587d78e4d4be
Jamshedkhon
04:42 AM
is there any default firewall on GCP
04:42
Jamshedkhon
04:42 AM
I have installed signoz on gcp instance
Syed
Photo of md5-f16c6ead78bebb6489e7ed7b121f5ce9
Syed
04:43 AM
i worked on aws, i can tell from aws perspective. yes definitely there is a default security group in aws, if we do not allow ports, connection will not work
04:43
Syed
04:43 AM
gcp also has must this kind of rules
04:43
Syed
04:43 AM
you need to allow all the ports used by signoz
Jamshedkhon
Photo of md5-3c955fc368fedc07f9d2587d78e4d4be
Jamshedkhon
04:44 AM
ok, thanks. I will check, if nothing changes I will write again😅
Syed
Photo of md5-f16c6ead78bebb6489e7ed7b121f5ce9
Syed
04:44 AM
ok 👍
04:44
Syed
04:44 AM
try to telnet from your local to server ip, see if connection is established