Hey there, I’ll raise this with the team to investigate but for a possible unblock could you please try to recreate the service and push to it?

Hello!

We're acknowledging your issue and attaching a ticket to this thread.

We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.

Please reply to this thread if you have any questions!

I'll try to duplicate the service and see. Thank you

still stuck on creating containers. let me give it some time

still failing

I deleted all of my services since I could not get this to work.... let me know if you have an idea on how to make this work. I'm using render as well but would love to use railway due to the new railway metal!

Hi Steven,

Thank you for the update. Could you try to recreate one of the services and point us to the new service? It'll help us reproduce and investigate what's causing the issue here, so we can help get you unblocked.

Regards,
Christian

Would you be able to look at the deleted service?

I'm also curious if you have a solution for leaving ports open even if there's not a listener yet. my service doesn't bind to the part due to a dependency. Would railway be able to support that?

Would you be able to look at the deleted service?

When you delete your services, they are deleted permanently, and we are not in a position to investigate further.

As for ports, you can set the $PORT variable per the Docs. If this doesn't address your need, please elaborate on your use case, and we can assess and comment.

That makes sense. It looks like it auto finds the port that is open. I'll try to set it up again and see how I can get it to work since render is currently not working on this rather niche use case... Thanks for the response. I'll follow up once I have it all running. Let me try use the config as code too since that seems to be pretty well documented

Hi Steven, that sounds great! Let us know of any questions along the way.

Cheers,
Christian

Okay I lied, I have it here! https://railway.com/project/181aeb76-7ca1-4698-ab7b-fa7c69e9cd54/service/4d7bf3e4-4ce1-4898-9e52-6f65fad6d490/variables?environmentId=aa28f2f1-2b7e-4c8d-af62-5e6ca3981309

but now it's working oddly enough. Potentially a weekend downtime? I'll continue to play around with this thank you!

never mind, it's stuck again creating the containers. Can you take a look? https://railway.com/project/181aeb76-7ca1-4698-ab7b-fa7c69e9cd54/service/8b7cb240-850e-4471-b597-fc47eaf7c872?environmentId=aa28f2f1-2b7e-4c8d-af62-5e6ca3981309

This is what I'm seeing!

Hi Steven,

Your containers are failing to start because the start command can't be parsed — you're missing a closing quote at the end of your command.

Let me know if you need help updating the config.

ugh.... apologies... I knew it'd be something simple. I'll be moving to IaaC anyways. Thanks!

Thanks for the update. We've used this as feedback to add error messaging in the build logs. Going forward, Railway will inform you of errors with your start command.

✅ The internal ticket Deployment stuck on creating containers has been marked as completed.