Remove private networking from my account
hey! can I please get private networking feature removed from my account?
26 Replies
Project ID:
N/AN/A
removed??
I think no?
why do you want to remove it
we're using planetscale and prisma. when we've turned on the private networking feature and after the services got re-deployed, prisma was trying to connect to mysql database on port
3306
rather than connecting to the exposed pscale db url present in DATABASE_URL
is railway polluting project level envs?also you're not part of priority boarding, so I don't know how you even enabled it
our servers are down due to this and we've tried to create a new project but still private networking got turned on
are you on the teams plan by chance?
no we’re on just developer plan
ps: they weren't any such issues prior turning on the private networking feature
heya! i'm part of the team and i'm part of priority boarding. i'm the one who turned on private networking
it sounds like you should be on the teams plan, the hobby plan is meant for hobby use cases only
I do fail to see how private networking would interfere with a properly setup app trying to connect to the database, but either way, while you upgrade your account I will ask the team
we're migrating to teams plan within next 2 days. i'm not entirely sure why is prisma connecting to mysql db on port
3306 just after turning on private networking?I'm not either
will tag the team in shortly
sure
Flagging this thread. A team member will be with you shortly.
have tried to deploy the server on a different railway project (with private networking turned on)
when the deployment starts, prisma tries to connect to mysql db at port
3306. prisma throws an error and when the deployment restarts (on-failure restart) the correct database url is used
PN wouldn't affect anything here
Are you expecting a different port? What's the port in your database_url?
here's how the db url looks. i've brought in "PN" as the issue got triggered right after turning on PN.
not sure what might be the exact reason behind it.
Can you connect to it via that connstring using a SQL client?
yep, i can
Did it work previously? Could you try pushing a new deploy to print the value of
DATABASE_URL? The only thing that could've gone wrong here is the redeploy step after PN was enabled, but I don't see how that'd change your DATABASE_URLyep, it did work earlier without any kind of issues. i'll push a new deploy
If all looks correct after ^, you could try adding a
connect_timeout=30 to your conn string. There is a slow init issue with PNs currently (a few seconds), so I think the private networking init might be racing with other network interfaces. The default for Prisma is pretty low IIRC
Hey folks, just checking in - any luck here?hey there! sorry for the late reply. i had a look into the issue and it's cause of the slow init speed of PNs. last night, i've increased the connection timeout in the connection string and it's working perfectly fine.
All good, glad it's working!