Question

After restoring my droplet backup, in place of my fully functional wordpress website, it is showing "Welcome to nginx!" page (Emergency)

Posted June 12, 2020 469 views
NginxWordPressBackups

My Wordpress website: http://advisorate.in was functional and on LEMP but after I restored my droplet backup yesterday in place of Wordpress website it is showing “Welcome to nginx!” page.
I am not well versed with exact console command but can execute it in putty if you provide it. Please help me with its solution along with the command. I am really scared that I will lose my website.

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.

×
1 answer

Hello, @rahuljaiswalrj1989

Could you please double check the Nginx configuration file for your domain name and make sure it’s pointing to the correct directory?

My assumption is that somehow the restore changed the content of the nginx config file or had overwritten it completely. If you can shed more light on what exactly happen during the restore and what files have been restored this can help us to find the culprit of the issue.

You can check the nginx configuration file using a text editor like nano, vi or vim:

sudo nano /etc/nginx/sites-available/yourdomain.com

You can also copy the content of the file here so we can check it and see if something is wrong with the current setup.

Hope this helps!

Regards,
Alex

  • Hi Alex,

    I restored my complete droplet backup over my existing droplet. I the first place I used easyengine (https://www.youtube.com/watch?v=9zX5-i9oJHU) to setup my Wordpress and everything was working great and advisorate.in was coming beautifully. But yesterday I restored the droplet backup and after that in place of my wordpress website it was showing “welcome to Nginx”
    I can access all my files with FileZilla and putty.

    Inside /etc/nginx/sites-available i have “default” name file with below content

    ##
    # You should look at the following URL's in order to grasp a solid understanding
    # of Nginx configuration files in order to fully unleash the power of Nginx.
    # https://www.nginx.com/resources/wiki/start/
    # https://www.nginx.com/resources/wiki/start/topics/tutorials/config_pitfalls/
    # https://wiki.debian.org/Nginx/DirectoryStructure
    #
    # In most cases, administrators will remove this file from sites-enabled/ and
    # leave it as reference inside of sites-available where it will continue to be
    # updated by the nginx packaging team.
    #
    # This file will automatically load configuration files provided by other
    # applications, such as Drupal or Wordpress. These applications will be made
    # available underneath a path with that package name, such as /drupal8.
    #
    # Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.
    ##
    
    # Default server configuration
    #
    server {
        listen 80 default_server;
        listen [::]:80 default_server;
    
        # SSL configuration
        #
        # listen 443 ssl default_server;
        # listen [::]:443 ssl default_server;
        #
        # Note: You should disable gzip for SSL traffic.
        # See: https://bugs.debian.org/773332
        #
        # Read up on ssl_ciphers to ensure a secure configuration.
        # See: https://bugs.debian.org/765782
        #
        # Self signed certs generated by the ssl-cert package
        # Don't use them in a production server!
        #
        # include snippets/snakeoil.conf;
    
        root /var/www/html;
    
        # Add index.php to the list if you are using PHP
        index index.html index.htm index.nginx-debian.html;
    
        server_name _;
    
        location / {
            # First attempt to serve request as file, then
            # as directory, then fall back to displaying a 404.
            try_files $uri $uri/ =404;
        }
    
        # pass PHP scripts to FastCGI server
        #
        #location ~ \.php$ {
        #   include snippets/fastcgi-php.conf;
        #
        #   # With php-fpm (or other unix sockets):
        #   fastcgi_pass unix:/var/run/php/php7.0-fpm.sock;
        #   # With php-cgi (or other tcp sockets):
        #   fastcgi_pass 127.0.0.1:9000;
        #}
    
        # deny access to .htaccess files, if Apache's document root
        # concurs with nginx's one
        #
        #location ~ /\.ht {
        #   deny all;
        #}
    }
    
    
    # Virtual Host configuration for example.com
    #
    # You can move that to a different file under sites-available/ and symlink that
    # to sites-enabled/ to enable it.
    #
    #server {
    #   listen 80;
    #   listen [::]:80;
    #
    #   server_name example.com;
    #
    #   root /var/www/example.com;
    #   index index.html;
    #
    #   location / {
    #       try_files $uri $uri/ =404;
    #   }
    #}
    
    
    • Hello, @rahuljaiswalrj1989

      At the moment the domain/site is loading okay tested from my end. Can you please confirm if you’ve sorted the issue?

      As mentioned on Ubuntu the Nginx config files should be stored in: /etc/nginx/sites-available/example.com

      Looking at the easyengine docs: https://easyengine.io/wordpress-nginx/tutorials/conventions/

      Nginx

      Configuration Files:

      /etc/nginx/ – all nginx related configuration will be in this folder

      /etc/nginx/nginx.conf – THE (main) nginx configuration file

      /etc/nginx/sites-available/ – nginx configuration for different sites will be available here

      /etc/nginx/sites-enables/ – symlinks to nginx configuration files which are “active”

      Log Files:

      /var/log/nginx/ – default log directory for nginx. We will use this for logs of all sites we will create.

      /var/log/nginx/example.com.access.log – access log file for example.com

      /var/log/nginx/example.com.error.log – error log file for example.com

      /etc/logrotate.d/nginx – this file control log-rotation policy for nginx related log files

      they follow the same structure as the default one. You might want to check if there are config files stored in /etc/nginx/sites-available and check your domain name’s config.

      Hope this helps!

      Regards,
      Alex

Submit an Answer