Pending bounty | Railway | Page 1

azure fog Aug 15, 2025, 4:10 PM

#

Hello, does bounties works only if I'm on a pay tier? I've a solved bounty but it is still in pending, I was wondering if I need to be on a paid account to get the bounty?

thanks

ripe vineBOT Aug 15, 2025, 4:10 PM

#

Project ID: N/A

azure fog Aug 15, 2025, 4:11 PM

#

N/A

heavy ice Aug 15, 2025, 4:20 PM

#

I don't see any pending bounties, can you link to the thread?

azure fog Aug 15, 2025, 4:32 PM

#

https://station.railway.com/questions/next-js-fetch-request-failing-when-fetc-90e7bf23

Railway Help Station

[NextJS] Fetch request failing when fetching API from it self

I need help troubleshooting a fetch request from middleware. It fetches internal API endpoint with following URL:${env.BASE_URL}/api/auth/post
The BASE_URL is set in variables like this: http://${{RAILWAY_PRIVATE_DOMAIN}}:8080
Everything works in development (as always) but fails when deployed
Fetch returns no error message. Replacing fetch ...

heavy ice Aug 15, 2025, 5:18 PM

#

The OP did not mark a specific message as solved, without that there would not be a payout.

azure fog Aug 15, 2025, 5:33 PM

#

so why I can see this in my message? and the thread is marked as solved?

heavy ice Aug 15, 2025, 5:39 PM

#

I missed that, my apologies, but that message did not solve their issue, and the information provided in that message is incorrect for the issue they raised.

For private networking you must listen on :: not 0.0.0.0 -

https://docs.railway.com/guides/private-networking#communicating-over-the-private-network

azure fog Aug 15, 2025, 8:59 PM

#

It did solve it, but I understand if that's not 100% correct, thanks

heavy ice Aug 15, 2025, 9:02 PM

#

Sorry, but listening on 0.0.0.0 would not allow the user to connect to their service privately. The private network is IPv6 only, and thus listening on :: is a hard requirement.

#

!s

#Pending bounty