Need help enabling Outbound Networking for my service

abaibaurzhan

HOBBYOP

4 months ago

Hi! I’m trying to allow outbound internet access for my service SelinaAI (project ID d8c7655f-7298-4aa2-8eda-514b30442b26).

According to the docs I should be able to attach the Outbound Networking plugin via the service menu (… → Manage Plugins → Add Plugin), but in the current UI I can’t find that option anywhere. The three-dots menus only show log/restart/redeploy/remove, and the Settings tab has no plugins section either.

Because of that the service stays on the private network and all HTTP requests to external APIs (Telegram, Green API, etc.) time out.

Could you please point me to the correct place in the new interface or enable Outbound Networking for this service on your side? Screenshots of my UI are attached.

Thanks!

Attachments

image.png

$10 Bounty

7 Replies

Railway

BOT

4 months ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!

samgordon

PRO

4 months ago

What documentation are you looking at that says that?

There is no configurable outbound networking, you can always access whatever you want.

abaibaurzhan

HOBBYOP

4 months ago

Thanks for the quick reply!

I was following these docs:

Public Networking – Outbound Networking section

Reference: Outbound Networking

Both pages still mention attaching the Outbound Networking plugin and redeploying, so I assumed it was required. If the docs are outdated, that would explain the confusion.

In any case, my service still times out on every call to https://api.telegram.org/.... Example log entry:
HTTPSConnectionPool(host='api.telegram.org', port=443): Max retries exceeded with url: /botXXXX/sendMessage (Caused by ConnectTimeoutError(... 'Connection to api.telegram.org timed out. (connect timeout=10)'))
Could you suggest how to debug outbound connectivity on the Hobby plan? I’m happy to run curl/CLI tests if needed. Thanks!

samgordon

What documentation are you looking at that says that?There is no configurable outbound networking, you can always access whatever you want.

abaibaurzhan

HOBBYOP

4 months ago

After today’s redeploy every outbound call to the Telegram Bot API ends in a connect timeout.
Token is correct (same request works from my laptop). To check the network from inside the service I ran:
curl: (28) Failed to connect to api.telegram.org port 443 after 10005 ms: Connection timed out
So it looks like the container cannot reach api.telegram.org at all. Docs still mention an “Outbound Networking” plugin, but I understand it may be outdated—regardless, I just need to know why outbound HTTPS is timing out and how to fix it.

Could you please investigate or let me know if there’s any regional/networking issue on your side?

Thanks!

samgordon

PRO

4 months ago

Can you please provide a link to where you see this documentation?

I do not know of any outage.

samgordon

Can you please provide a link to where you see this documentation?I do not know of any outage.

abaibaurzhan

HOBBYOP

4 months ago

Thanks for the quick reply!

The doc I was referring to is the old “Outbound Networking” page that’s still indexed: https://docs.railway.app/plugins/outbound-networking (it redirects to the legacy plugin catalog). I realise it might be deprecated, but that’s the only official note I could find about enabling egress.

Regardless, the timeout persists:

From inside the service: curl https://api.telegram.org → Failed to connect ... port 443 ... timeout

From my laptop on the same network everything works instantly (same bot token).

Could you confirm whether there’s any outbound firewall/egress restriction on the project, or point me to how outbound HTTPS should be configured now? Need Telegram to be reachable again.

Thanks!

abaibaurzhan

Thanks for the quick reply!The doc I was referring to is the old “Outbound Networking” page that’s still indexed: https://docs.railway.app/plugins/outbound-networking (it redirects to the legacy plugin catalog). I realise it might be deprecated, but that’s the only official note I could find about enabling egress.Regardless, the timeout persists:From inside the service: curl https://api.telegram.org → Failed to connect ... port 443 ... timeoutFrom my laptop on the same network everything works instantly (same bot token).Could you confirm whether there’s any outbound firewall/egress restriction on the project, or point me to how outbound HTTPS should be configured now? Need Telegram to be reachable again.Thanks!

samgordon

PRO

4 months ago

Can you try moving your application to a different region? Just for testing. Please let me know if it works somewhere else.