One thing that should never be overlooked is making sure to have backups, and even backups of your backup. While I may look silly for taking so long to fix such an error, everyone overlooks some things. Luckily, I had a backup of the website, and was able to undo some of the changes I have made to it when I was attempting to resolve the issue. It was not until much later that I was given access to a higher level account, and all it took was a few minutes for me to find the solution to the problem. In the end, I have easily spent four hours trying to fix the problem, but to no avail. The worst part about this was I didn't even have full access to the Plesk powered Windows server. This can range from not having a file set properly, lack of a default website, to something as simple as wrong permissions. The reason for this is because it is a generic error given, and can have so many meanings. In my opinion, this is by far the most annoying error when it comes to building a webpage. Recently, I had one of the worst possible experiences a web programmer could have - the dreaded "Server Error 500".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |