Wrong port is detected for PHP service using Nixpacks
lolautruche
TRIALOP

2 years ago

When deploying a service using Nixpacks PHP provider, port 9000 is automatically detected by Railway. The problem is that it's the PHP-FPM port, not the Nginx port, which is 8080 according to my deploy logs. The PHP container generated by Nixpacks exposing the 2 ports.

I had to manually set the port in the service settings to ensure HTTP traffic is correctly handled by Nginx.

10 Replies

Anonymous
TRIAL

a year ago

Having the same issue now


Railway
BOT

a year ago

An internal ticket has been attached to this thread. Updates will be relayed in this thread, so keep an eye out!

Status changed to In Progress Railway about 1 year ago


a year ago

For now you would have to set 8080 manually.


Status changed to Awaiting User Response Railway about 1 year ago


brody

For now you would have to set 8080 manually.

Anonymous
TRIAL

a year ago

The generated domain doesn't allow that. I get the option only with custom domain?


Status changed to Awaiting Railway Response Railway about 1 year ago


a year ago

It does, you can always change it after the fact -

Attachments


Status changed to Awaiting User Response Railway about 1 year ago


Anonymous
TRIAL

a year ago


I don't see it


Status changed to Awaiting Railway Response Railway about 1 year ago


a year ago

The UI element is shown on hover


Status changed to Awaiting User Response Railway about 1 year ago


Anonymous
TRIAL

a year ago

This is weird, I do not see the icons. But I can see the tooltips when I leave the cursor there for a while. And the cursor shows as a pointer. There's no visible icon there


Status changed to Awaiting Railway Response Railway about 1 year ago


Anonymous
TRIAL

a year ago

I have been able to edit the port, thank you. Maybe the icons not showing is something to look into.


a year ago

It's possible you have a browser extension interfering, we would need more reports in order to look into it, but either way, glad you found the edit button!


Status changed to Awaiting User Response Railway about 1 year ago


Anonymous
TRIAL

a year ago

Alright, I only have DeepL extension enabled on Chrome by the way


Status changed to Awaiting Railway Response Railway about 1 year ago


Loading...