Once in a while your blog may break down. At that moment you may need your hosting support help.
One thing I’ve learned, knowing how to clear cache the right way could lead a better communication with my hosting tech experts and solve my broken blog.
Read also: How to Find a Great Hosting for Your Blog
I was experiencing glitches on my site. The layout sometimes got messy suddenly. I didn’t know why.
Often time if there were a problem, restoring your backup back to a certain point could fix it.
My hosting tech expert suggested this method. I agreed and decided to restore it. But it didn’t help.
Now, here’s where it becomes interesting. On my tech expert’s end, he saw my site had backed to normal, but on my end, I didn’t.
Let me give you an important advice, after every fix attempt, both ends must see that it is fixed. If not, then something is off.
The difference could be caused by uncleared cache.
A cache is simply a place to store something. In the context of a web page and browser, it is a place to store pages elements. Thus, if a user asks for the same page, the browser just take it from its cache. It’s a faster process.
The problem is if your tech support expert fixes your blog, you won’t be able to see the new version of your page until your cache is empty. That’s why you need to clear your browser cache, every time you want to test.
Speaking about cache clearing, there are 5 caches you should pay attention:
- Browser cache.
Here are the links of how to clear cache of the two most popular browsers: Firefox Browser and Chrome.
- Plugin cache.
If you use a WordPress caching plugin, such as: W3TC or SuperCache, deactivate it.
- Server cache.
You need to ask your support to do it. Even though usually, they may have done it.
- Turn off your Content Delivery Network (CDN)
This way you won’t be served from CDN’s server and you’ll be served from your own server.
- Google Page Speed Module Cache
If your hosting server applies Google Page Speed Module and you have turned it on, then turn it off (from your .htaccess).
In this case number 5 was the reason why me and my hosting tech expert saw different results. We haven’t turned it off. He was served by the Google Page Speed Module cache, while it seems I got served by the cache, but sometimes I didn’t. That is why I saw glitches.
After I turned it off, all we both saw, was a broken site. Then the support guy realized something was wrong. My site should be ok with or without Google Page Speed Module.
From that point, he and his friends investigated the problem and fixed it. They rebuilt the NginX vhost for my domain (I don’t understand what that means), and cleared all caching on the server for it.
All I know my site is fixed. Hooray!
The case above was actually involving 4 different tech experts and it last for two days of continuous communication. I deliberately make the story short and bring up only the important points.
In this stage some other hosting support may wish you to vanish with your problem and stop giving them a headache, but my hosting support sticks.
Even though the problem was coming from their side, that’s okay, no hosting company is perfect. There will be problem once and a while. As long it’s not often. What matter next is how the support handles it.
In order to help your hosting support experts, help you, what you can do is to provide them with information as detail as possible, such as:
- If you have more than one domain, which domain is having a trouble. Don’t get mixed, or else a miscommunication could happen. Remember, they can’t read your mind.
- Tell them what you did, before the problem occurs (if you did do something). This way the guy assigned to help, can pinpoint the problem and provide a solution faster.
- Tell them the symptoms you see. Provide them with images if possible. You can use screen captor to capture images on desktop screen.
- Give them your hypothesis. Sometimes it can shed some light.
Do you have any interesting experience with your hosting support, you can share it in the comment below, I would like to hear it.