Keywords: WordPress - Amazon Web Services - Technical issue - Otherbnsupport ID: 9d7dee1e-0827-c33d-f09e-7ea88459469cDescription: I just went through the process of getting a Let's Encrypt certificate and installing certbot after a successful installation of Wordpress. Now when I go to the site demo.criticalinformatics.com it displays the bitnami "Awesome! WordPress is now installed." page and not my Wordpress site. When I click on the "Access WordPress" link I get a 404 "The requested URL /wordpress/ was not found on this server."

I was checking the configuration files of Apache and you have commented the configuration in the httpd-vhosts.conf configuration file, so that won't work.Is there any reason for that?

Could you please try to un-comment that file and restart the Apache webserver with sudo /opt/bitnami/ctlscript.sh restart apache? Then you will be able to access your server at demo.criticalinformatics.com.

I am sorry, I should specified better which files do you have to modify.

The file I was talking in my previous post is /opt/bitnami/apps/wordpress/conf/httpd-vhosts.conf. In this file there are defines the virtualhosts of yourr application. Last time I checked that file thanks to the support tool all the lines of the virtualhosts were commented.So Apache won't be able to serve any virtualhost as all the configuration is commented.

Could you please revert the configuration you made in your last post and uncomment the lines of the file I mentioned before?Do not forget to restart Apache after you modify that, just in case. You can do it executing sudo /opt/bitnami/ctlscript.sh restart apache

One thing I am confused about is how DocumentRoot should be set. We have another Bitnami server running Wordpress and DocumentRoot seems always to be set to /opt/bitnami/apache2/htdocs and not /opt/bitnami/apps/wordpress/htdocs as I would expect. The exception is /opt/bitnami/apps/wordpress/conf/httpd-vhosts.conf where it is set as /opt/bitnami/apps/wordpress/htdocs.

I have tried to compare the configuration of the two servers and they are very close. One thing that may help is that I had a failed certbot install that I finally got to work on demo.criticalinformatics.com.