WordPress app not reachable — “The Railway has not arrived at the station
nerfeoz
HOBBYOP
9 months ago
I deployed a WordPress site with Apache + PHP on Railway, but when I try to access my project (both via the Railway public domain and my custom domain diariohabana.com), I only get this error:
It looks like Railway is not detecting my service on the correct port.
Here are the details:
- The app runs with Apache and PHP 8.2.
- My site is WordPress running entirely on Railway, with the database in MariaDB.
- Domain is managed through Hostinger with DNS on Cloudflare.
- I cannot access the site from the Railway public URL or from my custom domain.
- In my
.envfile I hadPORT="80". I believe this might be the cause, since Railway assigns a dynamic$PORT.
I’ve attached my .env and JSON configuration for reference. Could you please help me identify the error?
Specifically:
- Should Apache listen on
$PORTinstead of hardcoding80? - Is there a recommended way to configure WordPress/Apache on Railway so it binds correctly to the port Railway expects?
- Do I need a
Procfileor just adjustments in Apache configs?
Thank you very much!
1 Replies
Railway
BOT
9 months ago
Hey there! We've found the following might help you get unblocked faster:
- 📚 Migrate from DigitalOcean to Railway
- 🧵 PHP FPM Laravel Majestic Monolith Port Configuration
- 🧵 port configuration
If you find the answer from one of these, please let us know by solving the thread!