Welcome to nginx! after droplet backup restore (emergency)

My client has paid ads and visitors coming to their site and they’re going crazy, so I’m a little frustrated here.

After restoring a droplet from when the site worked, I’m getting “Welcome to nginx!”

Following the instructions in this discussion:

I’m getting a 403 error

Nothing in: /var/log/nginx/error.log.1 /var/log/nginx/error.log

Inside /etc/nginx/sites-available/default (comments removed):

server {
        listen 80 default_server;
        listen [::]:80 default_server ipv6only=on;

        root /var/www/;
        index index.html index.htm;

        server_name localhost;

        location / {
                try_files $uri $uri/ =404;

 location ~ /.well-known {
                allow all;

— update as I’m troubleshooting —

I used this tutorial to set up my droplet with wordpress:

I didn’t install nginx, I installed Apache. I’m not sure why it was running.

I’ve stoped nginx and restarted apache but I’m getting an error: /etc/init.d/apache2 restart

  • Restarting web server apache2 [fail]
  • The apache2 configtest failed. Output of config test was: AH00526: Syntax error on line 33 of /etc/apache2/sites-enabled/default-ssl.conf: SSLCertificateFile: file ‘/etc/letsencrypt/live/’ does not exist or is empty Action ‘configtest’ failed. The Apache error log may have more information.

/etc/letsencrypt/live/ is not empty, there is a certificate inside I’ve just verified

Apache error logs (/var/log/apache2/error.log) only have logs from Yesterday, nothing from today

Show comments

Submit an answer

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!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

I’ve restored the droplet once again to start over, this time I immediately stopped nginx and restarted apache as sudo. I wasn’t restarting apache as sudo which seems to have caused the permission error.