This is before the error was fixed. Microsoft edge throwing an error that says it can't find the web address "tech.com".
0
0
Did you know that the very website that you are looking at right now just went through a big fix? It was just troubleshooted after a huge problem arose. And this problem might be of interest to you…
It all started one day when I went to add a new post. Well, for some reason, I couldn’t access the site. The URL re-routed to tech.com. I was puzzled. I tried the wp-admin. The same junk, except this time it was rerouted to tech.com/wp-login. This was very puzzling. I tried several times, but I couldn’t get it to work.
After a day I had tried so many times that I was sure that something was seriously wrong. Since I couldn’t get access to the site, I couldn’t change anything that might’ve gone wrong.
On MobaXterm the troubleshooting process started. Tests were ran on the LINODE server that this site is placed on, and the error was found to be a problem with the site URL in the WordPress database. Sure enough, when the site was pinged, and the Windows System32 hack was done, the site was able to be accessed again. The site URL on the WordPress URL configuration settings in the database had been changed to tech.com. This too was very puzzling, and perhaps I may never find out how it got to that state.
After this error was found, the URL was reset back to the usual techstation.bjrowan.com, and everything was back to normal. And if you’ve tried to visit that site between now and a month ago, then you wouldn’t’ve been able to do it. Now you can.
Whew! A fix well done. I haven’t seen this site in a while, but luckily nothing has gone wrong while I was away…just a few updates that needed to be done.
There is nothing like a good feeling of satisfaction after you fix a problem that is been a problem for quite some time. After digging into multiple terminals and running updates and hacking into the system and checking servers, the secret was finally uncovered–it could be distilled down to a simple problem with the site URL.
Wow! I didn’t know that this site went through a troubleshooting process that involved a wrong web address! I don’t know how in the world that could happen.