I had some problems accessing the site, too. From home and work. A while even DNS failed. So it does not seem to be your setup.
I had this now and then for the last half year. I once IMed Mojomonk about it but it seems he did not have those issues at the same time - maybe it's a europe-only problem . . .
I had this problem too. jmonkeyengine.com would resolve to the wrong IP or no IP at all. What I did was use a proxy in the US, find the IP used for the site, and then manually add a DNS entry in the HOST file.
I had this problem too. jmonkeyengine.com would resolve to the wrong IP or no IP at all. What I did was use a proxy in the US, find the IP used for the site, and then manually add a DNS entry in the HOST file.
eek, how can that happen? - resolving to a wrong IP even :?
i got no ip a few days ago, either. sometimes i have this problem with us sites and i always put the blame on my provider t-online. you are never wrong with blaming t-online.
it's not a problem from my home computer : I'm currently using it with my neighbour internet connexion and all is fine
it's a problem neither from my wifi nor from my router : i've directly plugged my comp on the modem and nothing was fine
there's nothing to see abound the "forever" login option… I was thinking it was maybe because I was logged forever at work. But now that I'm not logged anymore nowhere, there's still the problem.
Well, well, well… The only things I can see now is :
what mojo was talking about : IP locked due to any spammer (but this has been checked by him and it's not the case)
my Provider and the JMonkeyEngine's host may be in open war for any reason
I'm sad…
Mojo : can you check if any blocked IP is looking nearly like mine?.. (not the one wrote in this post, because it's my neighbour's one but the one i gave you earlier)
The reason you get that image is because the HTML file refers to the image location by the DNS name. This proves that the problem is the DNS not the connection to JME. Modifying the host file should work. You can also change your DNS server or run your own but the HOST file should be simpler.
I misunderstood what you were talking about llama and I did something else instead of what is described in your page… However, I didn't try this page : I was about to but I just see that I can reach the forum (woooohoooo!).
I've no answer from my ISP but I bet they did something (I hope). Else, if the "bug" comes back I'll do your HOST trick…