As I was following this tutorial https://www.digitalocean.com/community/tutorials/how-to-install-wordpress-with-lemp-on-ubuntu-18-04, I came a long way. But then after step 5, Wordpress doesn’t start on my website.
The website keeps displaying the html message that I programmed at step 4 of this tutorial https://www.digitalocean.com/community/tutorials/how-to-install-linux-nginx-mysql-php-lemp-stack-on-ubuntu-20-04, which I installed in this file: /var/www/your_domain/index.html
I have to say that the OS I am using is Ubuntu 20.04 (spec Ubuntu 20.04.1 LTS (GNU/Linux 5.4.0-45-generic x86_64)), but I don’t think that the problem is there.
My best guess is that the problem must have something to do with a redirection. Can anyone help me out here? There are also similar questions below the tutorial, but the answers proposed are not working for me.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hi there @KatoVonKatz,
There are a couple of things which could be causing this problem.
/var/www/html/
, you would need to remove theindex.html
file from there, you can do that with the following command:This needs to be done as WordPress uses an
index.php
file and thatindex.html
is not part of the WordPress core files anyway.Change the
/var/www/wordpress
part if this is not the directory where you installed WordPress at.Let me know how it goes! Regards, Bobby
@bobbyiliev , I will start a new threat here, because I can’t reply to you anymore via the above.
Yes, I did get an error report when I requested the nginx error log, but I can’t replicate that anymore.
But… now that I have the website up and running, as soon as I activate the code below, my website is down with an HTTP ERROR 500 message.
As soon as I remove the command, the website is active again. So, this really is the problem. I will share with you my error log. Maybe this has something to do with the transition from Ubuntu 18.04 to Ubuntu 20.04?