2 years ago
I have a server that runs successfully locally with the rest of my infrastructure components. The build works fine but when the deploy goes out, railway says "Completed" and when attempting to curl my domain, i get a connection refused. This had worked previously (read: two weeks ago) and stopped working suddenly. The main change was using a railway-hosted clickhouse instance as opposed to clickhouse cloud, but I'm not sure how that would affect it.
34 Replies
2 years ago
Is this in regards to the "airtunnel" service?
Stopping Container
level:
"info"
deployment: 4eb0f393-ce08-4498-a55a-5e7afde2d88d
replica: 02f1d179-2859-4733-b33f-4d6a05a3dedd
service: c2505f8e-e8b8-41a8-b06c-756705a997a0
im seeing this in logs
2 years ago
stopping container is fine in this instance since that's the last deployment being removed
2 years ago
I'm seeing a lot of failed to connect logs but I can still open the site
2 years ago
would you have some extra context on what is failing to connect?
oh? can you send a screenshot of you connecting? Because I can't even connect
2 years ago
I'm not connecting to anything, I just open the website
it also seems that although my database is being served on 8123, it only accepts requests via 443?
2 years ago
2 years ago
mind telling me your region?
2 years ago
publicly, yes it would only accept traffic on port 443
2 years ago
I am also considering to be us-east
ah yeah, i'm using the public address right now because i was worried the private address was an issue
2 years ago
looks like the public domain for Clickhouse returns OK
and you're just visiting https://airtunnel.io ?
2 years ago
correct
2 years ago
are you perhaps behind some kind of firewall
2 years ago
also, fwiw the completed state is just a UI bug
2 years ago
glad you figured it out, and looks like there are still no error logs, am I good to mark this as solved?