HTTP 500 Internal Server Error

[Chokra Broodslayer]

All of a sudden, the site is working again. No errors.

[watkins-legal]

Wonder of wonders, I'm back up, as mysteriously as it went, it's back.

No rhyme or reason but certainly thankful for it's return. Hope the same is true for the rest of you.

I want to thank everyone for their information and help.

[Clams]

Originally Posted by stevenjw

I can get there using the unblockanything.com proxy so it looks like something is blocking traffic to their site.

Now might be a good time to apologize to FurryGuy.

-W

[denirogator]

Something has definitely been going on and I'm sure it's been happening to a lot more people than some realize, because they can't get on the site to tell you!

I was only able to post because my wife had a computer that the site came up on. We were both using firefox and on the same internet connection.

And every other website on my computer came up perfectly fine, except slysoft. And I've never had a problem before.

Last night, I found that when I googled the internal 500 problem and slysoft, I was able to make it to the forum and this thread on my computer. Yet if I tried going to slysoft.com, I'd get the error.

I'm at work now and the site came up fine. I'll see when I get home if it's coming up fine now on my computer.

[Frank]

We do not know exactly what caused this and we apologize for any inconveniences caused. It would appear that by now all IP areas are on-line again.

[FurryGuy]

Originally Posted by Frank

We do not know exactly what caused this and we apologize for any inconveniences caused. It would appear that by now all IP areas are on-line again.

Thank you very much for the update on the situation Frank.

[denirogator]

Yep, I can confirm that everything is back to normal now on my end. I'm at home and the site is up on my computer for the first time in days.

[nbias]

I believe that the problem may be related which server was being chosen based on the DNS reply. See attached screenshot. Setting slysoft.com in my hosts file to 91.121.16.109 when things weren't working fixed the issue for me.