Docker deployed but have no answer from postman
Project ID: cd4ba81b-6c4a-4395-ab96-6db05d8eed0f
Hi there!
I'm new in Docker and just testing it. I have created an API using Nest.js and microservices, and I have created a Docker Compose wich works fine locally. I have deployed all my images to docker hub, and have deployed the client to Railway (just that service for testing). It is well deployed, with no errors and I have all the necessary logs in console. The problem is where I launch any request from postman, I get no answer, just like the screenshot. After some time, I get a TimeOut error.
I'm so lost on this, and have no idea on how to continue. Anyone can help? 🙂
Thanks!
Solution:Jump to solution
services on railway are currently only exposed on port 443, so as long as you specify https, port 443 is implied, meaning you need to remove 3000 from that URL
10 Replies
Project ID:
cd4ba81b-6c4a-4395-ab96-6db05d8eed0fSolution
services on railway are currently only exposed on port 443, so as long as you specify https, port 443 is implied, meaning you need to remove 3000 from that URL
That works. Thank you very much! Another question, do you know if it’s possible to automate docker deploys? I mean, when you push to a gh repo it automatically deploys to railway. Is there any way to do the same when I create a new tag of my docker image?
railway doesn't offer a native way to do that unfortunately, may I ask why you don't have railway build and deploy the image?
I do it, but doing it manually is annoying while I’m on a develop environment where I have different pushes. Btw if there is no other option I’ll do it manually. Thank you!
I assume you use the latest tag? if so, you can redeploy the deployment via it's 3-dot menu, and if there's a new image that one will be grabbed and deployed
I tried, but it redeployed the previous tag. Maybe I did something wrong. I’ll try tomorrow again and will let you know. Thanks for everything, Brody!
if you aren't using a latest tag than it will indeed deploy the same tag, so in the case of using a fixed tag you would need to go into the service settings source, remove it's image and put the new image and tag in, then deploy thr changes.
Do I need to specify with :latest in the image name or it is not necessary?
the latest tag would be assumed if left out
personally I'd still specific it anyway just for clarity sake