1 Answer
- Newest
- Most votes
- Most comments
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.
answered 5 years ago
Relevant content
- asked 8 months ago
- asked 2 years ago
- asked 4 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 2 years ago