Hello,
First things first, thank you for your work on Otter browser. I believe this can grow into a excellent browser and a lot of people will be relieved they can finally have some of Opera's goodies back.
I'm watching the development closely and will eventually make the switch.
Some minor issue arose however when trying to access the page "otter-browser.org". It seems to be blocked for me.
I'm from Colombia, South America and after consulting my ISP (said they do not block anything) I came to the conclusion that there must be something as bogon blocking going on on your side.
Browsing your page works just fine from a free proxy (kproxy for example) but a direct connection can not be made.
I can ping the server and it responds. But my browser said "the connection timed out".
Could you please take a look at it? My ip address should be listed here, if needed I can send it in a private message.
Cheers.
Hello Emdek,
trying to clear up the issue, I wrote an email to Leaseweb.nl as they seem to host the page "otter-browser.org".
Actually I'm unable to access any page on that server, so it's definitely something at their side.
Sadly, they can't investigate the issue because I'm not a customer.
This is the response I got:
Thank you for your email.
As you are not our direct customer, we cannot assist you.
What I can advise you is to contact the owner of this server (or
particular website) and let him contact us, we will than be able to
investigate this issue further.
Kind regards,
LeaseWeb - Customer Support
Please try and contact your hosting company Leaseweb, a simple email would do I guess.
Cheers.
@Escorpiom, I'm not using their services directly but through reseller.
Please send me your IP using private message and I'll ask admin if something could be done.
As a moderator I believe you should be able to see the IP in the bottom right of the post?
@Frenzie, nope, it is shown only for my own posts.
Hm, ok. Well, I sent it to you.
@Frenzie, thanks.
Awesome, thank you guys for reporting the issue. Hopefully I can soon browse the otter page without using a proxy.
Otter browser should be accessible from anywhere, you have users also in Latin America.
By the way, I can do some translating to Spanish or Dutch if you like.
Cheers
@Escorpiom, as long as it is not blocked at Leaseweb level then it should be only matter of time. ;-)
If you would like to try then here is How To:
https://github.com/Emdek/otter/wiki/Translations-How-To
I'm afraid it's not going to happen guys. Leaseweb is blocking traffic from this continent.
The days that Internet was worldwide are over.
In my opinion, you have a great project going on.
Otter browser need more exposure, but is now limited to some parts of the world.
You are doing yourself a disservice by allowing your provider to block users in, for example, Latin America.
Cheers.
I am in Latin America and I have no problem accessing Otter web pages.
It's only guessing which ranges have been blocked by Leaseweb.
They may be IP-ranges or country blocks.
Leaseweb has had a lot of DOS attacks lately and took the easy way out by blocking the whole lot.
Anyway I checked other sites hosted on that server and I can't access any of them.
Your ASN may or may not be blocked, I'm not familiar with Leaseweb's blocking policy.
I'm on Claro Colombia (part of America Movil) and it's the biggest ISP in South America.
Cheers.
Anyway I checked other sites hosted on that server and I can't access any of them.
¿Nobody else in Colombia can?
¿Nobody else in Colombia can?
That's what I'm afraid of.
Anyway, after asking around a bit, there are at least two operators that are blocked:
- Claro Colombia
- Virgin Mobile Colombia
I'll update this list as info comes in. It seems like Leaseweb used a so called "country block".
Cheers.
@Escorpiom, please check it now.
If it won't work now then it is blocked by Leaseweb...
Sweet!
Working flawlessly, thank you so much. Now we can start to recommend otter-browser here too.
Consider this as closed.
Cheers.
@Escorpiom, thanks for confirmation. :-)
Somebody from Philippines said otter-browser.org is inaccessible :(
@ersi, I'll check what could be done.