Error 521 and site won't come back up, despite restarting. Suggestions?

0

Please help with suggestions of what I can do to get my site back online.

Encountered an Error 521 -- which in the past has meant just a quick stop and start of the server to get back online. Not today.

I've stopped and restarted my Lightsail instance multiple times with no effect. I've rebooted as well, with no effect. I had noticed the ** Restart Required ** that last time I connected via SSH, just before stopping the server. Could the restart be required for some type of update, which has locked me up?

UPDATE: I am also unable to connect to the phpMyAdmin though my SSH connection does "work". The normal method (I use this a lot) to connect is to SSH in, hit the http://localhost:8888/phpmyadmin/index.php url and then edit. Says: "This site can’t be reached The connection was reset" -- stopped and restarted the SSH connection (successfully), but still no joy.

Help, please. Anyone, any suggestions on what to try now?
Cenay
Site: https://www.cenaynailor.com

Edited by: Cenay on Jun 26, 2019 11:15 AM - removed incorrect formatting on link

Edited by: Cenay on Jun 26, 2019 11:32 AM
Added new information about the phpMyAdmin issue now present

Edited by: Cenay on Jun 26, 2019 11:40 AM

Cenay
asked 5 years ago367 views
1 Answer
1

Solved my own issue... sharing it just in case anyone else encountered something like this.

So, about a month ago, I had added a small change to the htaccess.conf file in /opt/bitnami/apps/wordpress/conf to prevent a type of exploit I was seeing. The code I added is shown below:

# Added to prevent exploits
<Directory "/opt/bitnami/apps/wordpress/htdocs">
	# Block WordPress xmlrpc.php requests
	<Files xmlrpc.php>
		order deny,allow
		deny from all
		allow from 67.61.95.121
	</Files>
</Direcory
>```

As you can see from the content above, the closing </Directory> tag was misspelled, causing Apache to not start.   
  
The reason it took a month to manifest, is because I didn't restart Apache or the server after making this change (stupid, I know)  
  
So, my advice. If you make a change, force your site to stop and restart and check it immediately. Don't wait a month until a random reboot introduces the error, as you won't know where it came from.   
  
Just my .02 worth.
Cenay
answered 5 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions