3 months ago
I've got a few services deployed - one of them is a go application which is a grpc server. its internal networking in railway says that it supports ipv6, and the server is listening on [::]port
previously, it was on 0.0.0.0:port, listening for ipv4 connections
now, no applications seem to be able to connect to it unless it listens on ipv6 address, except for a python grpc client, which seems completely unable to connect despite various debugging efforts.
The odd thing was that this environment was working perfectly fine until very recently. Im not quite sure when things broke, but Im curious if there have been any internal railway networking upgrades that may be impacting this?
2 Replies
@Railway fyi you've got some scammers here trying to bring people to separate support channels
incase someone also has this issue, the fix was copying everything into an entirely new environment, which allowed internal networking to have both ipv4 and ipv6 support