WordPress setup issues? (New Timer) ForbiddenYou don't have permission to access this resource.
Hello! I'm looking to potentially migrate a majority of our companies heroku applications and wordpress websites over to railway.app, just wanted to give it a test and am struggling to setup heroku (apologies first time!)
Project ID: 6902c949-4f5a-4122-964a-4a5d3e317c9e
I'm currently on a trial plan, and have tried using this template which I found by going from https://railway.app/templates -> https://railway.app/template/EP4wIt. I didn't modify any of the configuration (just wanted to see if i could get it up and running first) have waited ~ 25 mins now and when attempting to access the site an error occurs with:
Forbidden
You don't have permission to access this resource.
Apache/2.4.57 (Debian) Server at primary-production-c5f5.up.railway.app Port 80
When looking into the logs for the application I can see this error:
AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.php,index.html,index.php,index.html) found, and server-generated directory index forbidden by Options directive
I have a bit of experience with Docker, but much less with WordPress (mostly work with node!) the wordpress movement is more of an important piece at the moment for our business requirements.
Any guidance would be massively appreciated thank you 😄 and looking forward to hopefully centralizing all of our deployments!
Solution:Jump to solution
Forgot to update the start command, my bad. Could you delete the project and deploy the template again?
Or change the start command in the “Primary” service to:
/bin/bash -c "echo 'ServerName 0.0.0.0' >> /etc/apache2/apache2.conf && echo 'DirectoryIndex index.php index.html' >> /etc/apache2/apache2.conf && echo 'upload_max_filesize = 50M' >> /usr/local/etc/php/php.ini && echo 'post_max_size = 50M' >> /usr/local/etc/php/php.ini && docker-entrypoint.sh apache2-foreground"...6 Replies
Project ID:
6902c949-4f5a-4122-964a-4a5d3e317c9e@Jack - wordpress template issue
Oh shoot wait
Solution
Forgot to update the start command, my bad. Could you delete the project and deploy the template again?
Or change the start command in the “Primary” service to:
/bin/bash -c "echo 'ServerName 0.0.0.0' >> /etc/apache2/apache2.conf && echo 'DirectoryIndex index.php index.html' >> /etc/apache2/apache2.conf && echo 'upload_max_filesize = 50M' >> /usr/local/etc/php/php.ini && echo 'post_max_size = 50M' >> /usr/local/etc/php/php.ini && docker-entrypoint.sh apache2-foreground"I've done that too, update template without updating it's start command
@Jack worked flawlessly. Thank you very much 😎 !