-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't connect to the app no matter what. Deployed through Docker. #724
Comments
DEFAULT_DOMAIN should be 'subdomain.domain.com' |
If you look at line 72 of Line 72 in 041aed5
So the "localhost" part is just hard-coded to the console message and doesn't actually represent what interface it is listening on. But I have the same problem, so I started a shell in the running Docker container: /usr/src/app # netstat -pant
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 172.30.9.212:49266 172.30.11.197:6379 ESTABLISHED 92/node
tcp 0 0 172.30.9.212:56462 172.30.22.203:443 ESTABLISHED 117/ssm-session-wor
tcp 0 0 172.30.9.212:34610 172.30.22.203:443 ESTABLISHED 69/ssm-agent-worker
tcp 0 0 172.30.9.212:50558 172.30.4.76:6379 ESTABLISHED 92/node
tcp 0 0 172.30.9.212:47344 172.30.8.97:5432 ESTABLISHED 92/node
tcp 0 307 172.30.9.212:56464 172.30.22.203:443 ESTABLISHED 117/ssm-session-wor
tcp 0 0 172.30.9.212:34596 172.30.22.203:443 ESTABLISHED 69/ssm-agent-worker
tcp 0 0 :::8080 :::* LISTEN 92/node As you can see on the last line, |
Actually, I just noticed this: /usr/src/app # netstat -pant
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 :::8080 :::* LISTEN 94/node
tcp 0 0 ::ffff:172.30.7.235:8080 ::ffff:192.168.20.83:64268 ESTABLISHED 94/node
tcp 0 0 ::ffff:172.30.7.235:8080 ::ffff:172.30.16.5:45094 ESTABLISHED 94/node
tcp 0 0 ::ffff:172.30.7.235:8080 ::ffff:172.30.3.230:36746 ESTABLISHED 94/node
tcp 0 0 ::ffff:172.30.7.235:8080 ::ffff:172.30.36.238:11826 ESTABLISHED 94/node Connections are making it to the container; the 192.168.20.83 is my workstation making a direct connection to the container (172.30.7.235). The other three are AWS load balancers trying to make a connection. But they eventually timeout So that means the node app is just... ignoring the connections? |
@Jas-SinghFSU were you able to resolve this issue ? |
No matter what I do, I can't access the server. I get connection timeout errors or "refused to connect" errors. My server's local IP address is 10.0.0.239 and that's the address I want to host it at.
No matter what I do, the log for the container says
Even though I never specified
localhost
as the domain, it always tells me that the app is read on localhost:3030. I have tried to access localhost:3030 on my server and still get 'The site can't be reached'. I also have my ownsubdomain.domain.com
but when I put that into theDEFAULT_DOMAIN
it doesn't work either.Here are my configs, what am I doing wrong?
Compose config using portainer
docker.env
The text was updated successfully, but these errors were encountered: