Things to do after website DOWN

An active site should be better maintained, especially if you have a lot of visitors, so that you don’t disappoint visitors with a site that is free of bugs. When it comes to an error, there are actually many types, there are those from functioning systems that lead to fatal errors and can still be repaired, and then there are errors on the server. If the website that is currently owned is renting hosting, it might be quiet because the one who fixes it is the hosting provider and errors occur with many users, not just one. However, this becomes very difficult if the error is on your own server and the error is made yourself, of course you have to fix it yourself and reinstall it at most if the problem is not fixed.
Websites that are inactive can actually be seen by tracker sites such as website status sites which provide received HTTP header information. Not all of the pages that went down are actually down, so I can once again conclude that this can be seen from the website’s response header form as it could be a website that is taking a long time to open and this causes Time out occurs because a script it contains blocks or malfunctions causing the process to rotate continuously (ribbon) and to see if the site is down or not, you can use multiple website trackers to check the headers I shared in the article to see if the site is down or not.
No matter how big the website is, if the connection is very weak it will definitely time out and it is believed to be the case Low. But sometimes a Cache or Cookies which is still attached causes the last data for visiting the website to be saved together with your page. This usually happens a lot on websites that are idle and displaying the page maintenance or go to another page like Standard website. Just like a site that has never been created goes to this page and the page’s caching process is usually still saved when the user tries to refresh or run the page Update The page stays down unless the DNS is cleared or the device is restarted.
Clearing DNS is also very easy, but some people still don’t know because to do it you have to use CMD when on Windows but when If you want to clear the cache, you can do so directly from the browser and it’s very easy. The feeling of an admin will definitely get annoyed if the website they have has a bug or goes down and can go limp immediately if the website that has been under maintenance for a long time suddenly has unexpected problems even though it was fine before. But it’s best not to worry if a website that is down is temporary and it would be better to send a contact to the server provider. But if they say the site was back up or should be restored and the browser the user is currently using is still inactive, then below is how to make sure of that.
- Review by website tracker – Users can confirm that the site is down or not by visiting a website tracker that shows a full HTTP header. A reliable site is status.ws and in addition to relying on one site, you should use 2 website trackers at the same time to be sure.
- Clear DNS, cache and browser cookies Just like creating a new domain, it definitely takes a long time unless the user tries to clear the DNS. To do this on each device, you can simply restart the device or if Windows can do a DNS flush via CMD. In the meantime, you can clear the cache and cookies by going through the browser settings.
- Visiting websites through WebProxy – A web proxy is required here if the cache or cookies are still attached in the browser, so that users can easily visit their website via a web proxy such as Hideme, Kproxy or others and with this help can definitely see the current state of the website, regardless of that whether it is open or still inactive.
- Use VPN – Even if using a web proxy is enough, who knows that the website server is blocking a certain country, which results in users not being able to open the website properly. So with the help of this VPN you can change the current user as if they were online from another country.
- Use a different browser – This is the last resort, users shouldn’t just save the Chrome type browser as I think it has similarities with the cache and try to access websites owned by Mozilla browser and Internet Explorer.
It is only possible with the above method know the state of the website currently owned and don’t have to worry, let alone witness the same incident, as the server outage usually doesn’t last long. I experienced this myself and thought that my page was offline for a day, but it turned out that it was my own fault not to clear the cache and cookies in the browser. Use one of the methods above, preferably starting with the top method. If you have any questions about any of the above, please comment.
Hopefully useful and good luck