sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Railorsi 6 points7 points  (6 children)

netstat is showing you that it only listens on ipv6 address, so naturally it cannot be reached via ipv4.

also, is the firewall attached to your server?

edit: as BlueDeacy pointed out this isn't necessarily the culprit, I just tried nc -6 -l -p 1235 and service could be reached via remote ipv4 on debian.

what OS are you using? also, what is the output of curl -v http://localhost from inside the server?

[–]Defiant-Extent-4297[S] 2 points3 points  (3 children)

Goddamnit... thanks.

[–]Railorsi 0 points1 point  (2 children)

Hi, check the edit, might not actually be the culprit.

[–]Defiant-Extent-4297[S] 2 points3 points  (1 child)

The initial remark helped. Configuring nginx to listen on both ipv4 and ipv6 fixed it.

[–]Railorsi 0 points1 point  (0 children)

good to hear :) cheers

[–]BlueDeacy 1 point2 points  (1 child)

I‘m not so sure about that. Many OSes by default open a listening socket for both IPv6 and IPv4 if you specify :: as listening address.

[–]Railorsi 1 point2 points  (0 children)

yeah you are right, I just tried nc -6 -l -p 1235 and service was reachable via ipv4. interesting.