a month ago
Railway Team,
We’re experiencing persistent “Connection Refused” errors when connecting to our Redis instance over private networking.
Project: AEX-R
Service: Redis + Token Broker, Token Refresh Bee, AEX-R Trading Engine
Region: us-west2
Redis URL:[rediss://default:************@redis-secure.railway.internal:6379/0], [redis://default:***********@redis.railway.internal:6379]
Error: [Connection Refused]
Steps we’ve taken:
- Verified Private Networking is enabled for both services
- Confirmed same project and region
- Restarted both services
Can you please confirm if there’s a network or routing issue on the Redis host, or if additional configuration is required?
2 Replies
a month 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!
a month ago
Hey there!
I looked into our networking and this seems to be a service issue. I was able to connect to your redis via https://redis.io/insight/ and everything appeared functional.
I'll push this to the community for help debugging the application issue.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open noahd • about 1 month ago