Chromium gives "This page is not available" error

[AnotherUser]

Chromium browser (why is it called chromium in Linux and Chrome in Windows anyways) is very fast. However, when I use it, I quite often get the frustrating error This webpage is not available even though there are no internet problems on either my side or the server side. It doesn't matter what page this is (i.e. gmail, cnn, pclinuxos, etc) they all give this annoying message at about a 30% rate. I never get this error when I use Firefox or Konqueror.

Does anyone know why this is happening and better still, how to fix it?

[Just17]

why is it called chromium in Linux and Chrome in Windows anyways

Because they are two different releases.

Chromium is the open source release on which Chrome is based.

So you can have Chrome in Linux too!

[YouCanToo]

Try changing you DNS numbers and see if that helps out

Here are the DNS for OpenDNS

208.67.222.222
208.67.220.220

[AnotherUser]

Try changing you DNS numbers and see if that helps out

Here are the DNS for OpenDNS

208.67.222.222
208.67.220.220

Not sure I understand. My other browsers (konqueror or firefox) are not having any problems, so why would a DNS change on my network interface make any difference?

[YouCanToo]

Try changing you DNS numbers and see if that helps out

Here are the DNS for OpenDNS

208.67.222.222
208.67.220.220

Not sure I understand. My other browsers (konqueror or firefox) are not having any problems, so why would a DNS change on my network interface make any difference?

You would think it shouldn't make a difference, and I agree, but I have seen it happen. I changed the DNS and everything worked like it should, went back to the DNS provided by my ISP and the very same problem appeared again. Hey look at it this way if it doesn't do anything what have you lost by doing it. On the other hand if it does work what have you gained by making the change   Of course the choice to try or not is entirely yours, I just made a suggestion.

[johnmart]

I had a similar error bugging me, that was caused by the browser reading a cached pgge from an earlier page error. I cleared the browser cache & all was ok.