10 months ago
Je viens de passer au plan pro, est ce que les données de récupération dans la base de données seront maintenant beaucoup plus rapide
21 Replies
10 months ago
Hey gaddi,
We only offer support in English, so please keep any further communication in English 
There is no performance difference between our different plans, however, you do get higher resource usage limits.
For a database, the higher limits are unlikely to make a difference in the performance.
Hope this helps !
-Nico
Status changed to Awaiting User Response Railway • 10 months ago
itsrems
Hey gaddi,We only offer support in English, so please keep any further communication in EnglishThere is no performance difference between our different plans, however, you do get higher resource usage limits.For a database, the higher limits are unlikely to make a difference in the performance.Hope this helps !-Nico
10 months ago
Indeed I had a problem related to the data recovery which is becoming slower and slower. Since the information in the database is becoming more and more consistent or numerous So I thought that, updating to a higher plan could increase the quality of data recovery, since I have a higher CPU with the pro plan. So the pro plan will not be able to solve my problem.
Status changed to Awaiting Railway Response Railway • 10 months ago
Status changed to Awaiting User Response Railway • 10 months ago
Status changed to Awaiting Railway Response Railway • 10 months ago
gaddi245
autorack.proxy.rlwy.net
10 months ago
Is this the link?
10 months ago
Your link should look something like railway.com/project/<projectId>/service/<serviceId>
However the link you just sent is one of our TCP proxies, which leads me to believe your services are talking to your database over the public network instead of our private one.
You should use the .railway.internal domain when passing the url to your services - this is faster and does not incur any egress costs.
Status changed to Awaiting User Response Railway • 10 months ago
itsrems
Your link should look something like railway.com/project/<projectId>/service/<serviceId>However the link you just sent is one of our TCP proxies, which leads me to believe your services are talking to your database over the public network instead of our private one.You should use the .railway.internal domain when passing the url to your services - this is faster and does not incur any egress costs.
10 months ago
How come? So I can change
Status changed to Awaiting Railway Response Railway • 10 months ago
10 months ago
Do I need to delete autorack.proxy.rlwy.net:58092 What should I do, I don't want to make a mistake and have things deleted.. If you can help me. Thank you
Attachments
10 months ago
If you want to access the database publicly (ex: you want to use the data panel, or connect from your own machine), you can leave it.
What you'll need to do is to go to the services that use your db and replace autorack.proxy.rlwy.net:58092 with postgres.railway.internal in the DATABASE_URL env variables.
Status changed to Awaiting User Response Railway • 10 months ago
10 months ago
Here is the link to my project, I can't seem to get it working
Status changed to Awaiting Railway Response Railway • 10 months ago
10 months ago
Help me please
10 months ago
How do I change the database to postgres.railway.internal?
10 months ago
I just deleted the public network, how do I use the private network?
10 months ago
I've updated your services to use ${{Postgres.DATABASE_URL}} in their DATABASE_URL env variables - should be g2g !
Status changed to Awaiting User Response Railway • 10 months ago
itsrems
I've updated your services to use ${{Postgres.DATABASE_URL}} in their DATABASE_URL env variables - should be g2g !
10 months ago
In all honesty, I don't understand where I should use g2g.
Status changed to Awaiting Railway Response Railway • 10 months ago
10 months ago
The service is no longer working
10 months ago
you are here, the services no longer work
10 months ago
Sorry about that. I've reverted the change and added $10 in credits to your account.
It looks like your apps migrate the db during the build step, which requires using the public networking. You should try to use pre-deploy commands: https://docs.railway.com/guides/pre-deploy-command, which run between the build and deploy step, to run your migrations.
Our builders do not have access to the private network, which caused the failure when swapping to it.
Status changed to Awaiting User Response Railway • 10 months ago
itsrems
Sorry about that. I've reverted the change and added $10 in credits to your account.It looks like your apps migrate the db during the build step, which requires using the public networking. You should try to use pre-deploy commands: https://docs.railway.com/guides/pre-deploy-command, which run between the build and deploy step, to run your migrations.Our builders do not have access to the private network, which caused the failure when swapping to it.
10 months ago
Can you explain to me about the credit, is it on the Visa card you added it or how?
Status changed to Awaiting Railway Response Railway • 10 months ago
10 months ago
I added it to your workspace - which means your next bill will be $10 cheaper.
Status changed to Awaiting User Response Railway • 10 months ago
itsrems
I added it to your workspace - which means your next bill will be $10 cheaper.
10 months ago
ok, thanks
Status changed to Awaiting Railway Response Railway • 10 months ago
Status changed to Solved chandrika • 10 months ago