This morning, I decided to move my blog from the old web hosting provider to a new one due to critical problem (lol =))). Since a week ago, a friend of mine wrote on my facebook wall that she got this message: Error establishing a database connection.
I didn’t get what she mean, but several days later while I was checking this blog, this annoying message come again.
Now, I understand that she pointed the error message to my blog. But, i think it would just be a temporary error, till i came up again to check my blog this morning. I always get this message whenever I open my blog and need to do CTRL+F5 (full refresh) to get rid of this error. I contact the customer support to fix this issue ASAP, and i asked him if another customer getting similar problem, but he confirmed nobody report the similar problem :-|. While he was troubleshooting about this issue, I prepared to backup my wordpress and ready to move it into a new web hosting.
Another reason why I decided to move is money. Yeah, money $-)
The old web host will cost me $5 USD quarterly (each 3 months) for 200Mb web space and 10Gb bandwidth monthly.
The new web host will cost me $5,85 USD quarterly (each 3 months) for 1.5Gb web space and 15Gb bandwidth monthly.
Well, it looks fair (lol =))) to kick me out of such service.
By the way, i’ve registered with the new webhost and i’ve another site hosted there already and I simply add new addon domain, point the name server of www.ryan-isra.net to the new webhost’s name server. By using VPN or proxy, i can access this blog on new webhost, else i need to wait the DNS server has fully updated.
This post also tells you that you’re accessing the new updated blog instead the old one.
what most people search here: www rayan vpn3 com, error establishing connection to, wordpress error establishing a database connection, how do you check for errors when establishing a connection to a database, rayan vpn3 com, www raian vpn3 com
Related posts:
pake selametan donk biar ‘selamet’ dirumah baru ;))
Emmm… selametan yah….
gimana yah… di sini aja masih resolve ke DNS yang lama terus…
mesti pake proxy biar bisa access 'rumah baru'… :))