4 months ago
Hi,
I tried deploying my applications and i see this errorInvalidArgumentException
Given URI "tcp://centerbeam.proxy.rlwy.net:46505" does not contain a valid host IP (EINVAL)
13 Replies
4 months 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!
4 months ago
Are you running migrations currently in the build process? You may benefit from moving that Laravel step to a pre-deploy command.
Status changed to Awaiting User Response Railway • 4 months ago
angelo-railway
Are you running migrations currently in the build process? You may benefit from moving that Laravel step to a pre-deploy command.
4 months ago
It is on pre deployment. The thing is that the service was working before but i had overdue invoice and service was terminated. I just paid now so i am not sure why the deployment won't work?
Status changed to Awaiting Railway Response Railway • 4 months ago
henryo
It is on pre deployment. The thing is that the service was working before but i had overdue invoice and service was terminated. I just paid now so i am not sure why the deployment won't work?
4 months ago
Oh that explains it, the URL changed, it's expecting a different value for the TCP proxy.
Status changed to Awaiting User Response Railway • 4 months ago
angelo-railway
Oh that explains it, the URL changed, it's expecting a different value for the TCP proxy.
4 months ago
How do i fix this please?
Status changed to Awaiting Railway Response Railway • 4 months ago
Status changed to Awaiting User Response Railway • 4 months ago
4 months ago
Also i see that when i visit my laravel api endpoint
Attachments
Status changed to Awaiting Railway Response Railway • 4 months ago
angelo-railway
Where do you have the DB coded in your deployment?
4 months ago
You mean the DB URL?
Status changed to Awaiting User Response Railway • 4 months ago
4 months ago
The DB_URL has the postgres internal url string in the variables
Status changed to Awaiting Railway Response Railway • 4 months ago
4 months ago
I also have the same for redis
4 months ago
This is the problem
centerbeam.proxy.rlwy.net:46505 this url for one of my service
4 months ago
I have fixed it by recreating the proxy for the service and the deployment works now
Status changed to Solved henryo • 4 months ago
Status changed to Solved christian • 4 months ago