Connection to Supbase fails
Hi I'm having issues connecting to supabase, it worked before I restarted the project now it fails
19 Replies
Project ID:
f307186f-df9f-435e-96e8-d7d17da7dffaf307186f-df9f-435e-96e8-d7d17da7dffa
I'm no expert but that kinda looks like you're storing sessions in memory, which is fine in dev but in prod it can lead to memory leaks and is all around not a good option
to fix that you'd need to store sessions in persistent memory, like a db
oh wait there's a dif error below it
Thats not the issue that makes it crash
Ye
Thats just an alert, doesn't matter to me
yea idk anything about that error, someone else might be able to help
Is there a live chat I can talk to
Cause idk what I'm supposed to do
on hobby plan, community support is all you have ( communtiy support = this help thread )
if you upgrade to pro plan then you can talk to the team directly via email
tbh though, from the looks of the error is doesn't really seem like it's an error caused my railway, seems more like your database isn't accessible from railway which is likely your databases fault
Maybe you need to whitelist IPs?
I mean its accesible from anywhere, but where can I find railway's IP?
here's the us west container's IP range: https://utilities.up.railway.app/cidr-list?value=us-west1
you can use this to check if your database is accessible from railway
https://utilities.up.railway.app/port-check?host=<your database host>&port=<your databases port>
just so you know, deployments have dynamic ips, you would either have to whitelist all ips (0.0.0.0/0) or whitelist all 26 cidr ranges from the link fragly sent
Still the same error
are you utilizing the private network
WHat do you mean by that? Like allowing certain IPs on supabase?
If so, no
If you mean this
No again, I mean its enable but I don't use it in code
okay try disabling it
and then redeploy your service
Oh
Feel like it working
okay then you'd need to increase the connection time-out to supabase since private networking is interfering with the initial connection