3 months ago
Hello Railway Support Team,
I have recently deployed a service, which make outbound API call to my gitlab api.
Which is failing with "Max retries exceeded with url:" port 443.
Can you please help me fix this?
If that is an issue with
- DNS resolution from my service container
- restriction of port
- some additional networking or config issue.
Please do let me know if my service name or id required or anything else is needed to resovle this.
3 Replies
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
If it’s self hosted gitlab, make sure the url works from outside your VPN/network and isn’t IP-allowlisted/firewalled...Also check it’s not IPv6-only (railway outbound IPv6 isn’t supported)
3 months ago
Thanks Team for the response.
But We did check all of these already.
out gitlab is self hosted but the API works outside our network/VPN.
and we have IPv4 also (not IPv6-only). No IP whitelisting is needed.
Can you please us how can we further investigate this or
how can we use curl from our service to test the request?
We are using Django app. Please do let us know if anything else is needed!
dharmateja
If it’s self hosted gitlab, make sure the url works from outside your VPN/network and isn’t IP-allowlisted/firewalled...Also check it’s not IPv6-only (railway outbound IPv6 isn’t supported)
3 months ago
Hi Team,
Thanks for the support.
We have fixed this issue. It is working.
We were listing https (443) request on port 8080 which I think was not enabled as outbound call from Railway.
We have corrected the Routing rule at our end and its working as expected.
We can now close the Thread/ticket.
Status changed to Open brody • 3 months ago
Status changed to Solved brody • 3 months ago