• Dear all,

    Thank you for taking the time to help me with my issue.
    I have to admit, Im not a web developer. But very interested in learning. So, Im not really sure if im running Nginx or Apache or both.
    I selected all the plugins that needed an update and updated all. I know, what was I thinking, while not having a backup.
    The issue is, I started getting Error 525 for a while. And now Im getting
    Index of/
    index.nginx-debian.html
    Apache/2.4.18 (Ubuntu) Server at http://www.hadyprints.ml Port 80

    Any idea how I can get my site up and running again??

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi @hadyashraf

    Did you try to deactivate the plugins?

    Are you able to access your wp-admin area?

    If not, you can still deactivate plugins using FTP: https://kinsta.com/knowledgebase/disable-wordpress-plugins/#how-to-disable-wordpress-plugins-via-ftp

    Try again after deactivating all plugins. 🙂

    Thread Starter hadyashraf

    (@hadyashraf)

    Hi @bizanimesh

    I renamed the “plugins” folder via FTP. Now, I get 525 Error SSL handshake failed, when I load my domain name through HTTPS. When I load the public IP address over HTTP, I get the same “Index of/ index.nginx-debian.html”

    I did, however, edit the default file, located in /etc/nginx/sites-available. As some other forum suggested that. Please find the edited file now.

    ##
    # 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.
    # http://wiki.nginx.org/Pitfalls
    # http://wiki.nginx.org/QuickStart
    # http://wiki.nginx.org/Configuration
    #
    # Generally, you will want to move this file somewhere, and start with a clean
    # file but keep this around for reference. Or just disable in sites-enabled.
    #
    # 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 /opt/bitnami/apps/wordpress/htdocs;
    
    	# Add index.php to the list if you are using PHP
    	index.php;
    
    	server_name www.hadyprints.ml;
    
    	location / {
    		# First attempt to serve request as file, then
    		# as directory, then fall back to displaying a 404.
    		try_files $uri $uri/ =404;
    	}
    
    	# pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
    	#
    	#location ~ \.php$ {
    	#	include snippets/fastcgi-php.conf;
    	#
    	#	# With php7.0-cgi alone:
    	#	fastcgi_pass 127.0.0.1:9000;
    	#	# With php7.0-fpm:
    	#	fastcgi_pass unix:/run/php/php7.0-fpm.sock;
    	#}
    
    	# 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;
    #	}
    #}
    

    Hi @hadyashraf

    I request you to contact your hosting provider and describe all things to them, also include the thread of the other forum from where you have applied those things.

    They would better help you. 🙂

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Site Broke after plugins update’ is closed to new replies.