02/16/2022
Today I am going to write about arguably the most important topic to date. Resilience.
I felt particularly compelled to write this blog because it means so much more than fixing a bug. The entire experience describes the reason why I decided to and have stuck with (to be frank) web development. Simply put, my desire to solve problems.
Now let me set the picture. Here I am minding my own business one day when I decided to add an rss feed to my affiliate coffee website, Brewing Alpha. I thought, man what a great way to add some outbound links for SEO. If you are not familiar with RSS feeds they are a really fun and interesting tool for developers.
Well. That's where we encountered the issue. I noticed that trying save some of my settings was causing a bit of a mess. And then eventually after a few minutes I started to receive an “Error 500” message from WordPress. This meant that any changes I was making were not being saved. I was simultaneously working on an article and coincidentally the changes I was making to the blog were saving (but the ones I was making to the homepage were not).
I of course started by looking up what the hell an “Error 500” message even meant. Now in the element of full disclosure I hate these types of problems. The moment I have to Google search what something even means, is when I begin to feel the existential dread of actually having to program. The results of my search is that an Error 500 is typically reserved for server side functions. Bro wut?
A little bit more digging led me to a step by step guide on whittling your Error code options down. One of these suggestions was to isolate the problem by disabling all the plugins and enabling them one at a time in order to see where the issue was. Well. When you mix explicit directions like that with my destructive personality you end up with a pretty big mess on your hands. Boy did I deliver!
I actually ended up disabling my ssl certificate plugin cloudflare and completely disabling my HTTPS encryption. This now made it so that any time I tried to make a change on my website the page would reload and suggest I don't visit because it did not have a secure connection. JFC. Talk about snowball effect. You can read more about getting your website a free ssl certificate via cloudflare and updating your GoDaddy DNS settings here.
Ok. So understanding that my issue was on the server side I decided to log in to my GoDaddy Cpanel and see if I could figure out where we were getting jammed up. After waiting hours to chat with a tech I was finally able to explain my issue. They “checked their servers” and saw no issues. Except for my ssl certificate. Which the tech kindly gave me a link with instructions on how to upload your ssl certificate directly to go daddy from your cloudflare account. NOPE!
Soon as I did it all hell broke loose with the ssl certificate. Heads up, if its working don't mess with it, or as I’ve stated in other posts just get yourself a host that provides this service for free.
In the end after reinstalling my ssl certificate and changing my DNS settings the tech said it would be 1-48 hours before the changes take affect. Well, that did not happen and it turned out to be a tremendous waste of time.
My next move should’ve been my first all along. When lost on the internet, consult the internet. So I joined Reddit r/WordPress and got some great advice. I started by logging into my cPanel once again on the server side (meaning GoDaddy). On the cpanel menu when you scroll down you should see errors. Clicking on this icon will take you to a page that displays the error logs for the website in question.
I had two error logs. In order to make sure they were for the same issue I had to crosscheck by attempting to make a change on my homepage and saving it. When I checked back to the error code log there was a new entry. Bingo! From here I summoned a GoDaddy tech again. I explained that the errors were logged and I asked them to pull any additional php error codes in case I wasn’t seeing them. Next thing I knew the tech popped back into our convo and asked me to try and save my work again. Boom. Problem fixed!
When I asked what was done in order to correct the issue the techs response was, “Awesome we just added few files to hosting, like User.ini file.”
So while I actually had very little to do in terms of coding, I still had to diagnose the problem and find it and point a specialist to it. I think I got lucky this time, but this is exactly why it is important to keep these occurrences logged so we can always come back and have a reference point.
And while the original (and second ssl certificate) problem had been solved, we encountered a new issue. When we posted the error codes on Reddit one user pointed out a bit of code that should never exist on WordPress. You can read the full breakdown on that issue after the jumpoff…