error 404 help

**Silent Raven** · 4th June 11, 12:15 PM

anyone else have tissues signing on to xmarks today. Keep getting error 404 from my computer, I'm posting this from my cell phone. if so how did people fix the problem??

**Jock Scot** · 4th June 11, 12:31 PM

It solved itself after an hour or so.Ted had the problem as well.

**DRipper** · 4th June 11, 12:42 PM

Been having that problem on and off for two hours, some server glitch,

**Steve Ashton** · 4th June 11, 12:48 PM

The pool of unallocated IP addresses that are distributed by the Internet Assigned Numbers Authority (IANA) has been depleted. In laymens terms, they have run out of IP addresses. APNIC, one of the five regional internet registries, exhausted its available pool of IP addresses on April 15. The four remaining regional registries are expected to exhaust their supply of IP addresses soon.

Because of the shortage of available IP addresses, SoftLayer, our upstream provider of IP addresses, has started rationing and limiting IP address allocations. At this point they will only issue dedicated IP addresses for websites that require ssl certificates. They have also asked us to return any IP addresses that are not being used to host websites that require SSL certificates.

At 12:00 a.m. On Saturday, June 4, we will begin renumbering websites that currently use dedicated IP addresses but don't use an SSL certificate. Your new IP address will be 208.43.100.35. Websites that currently use SSL certificates will not be affected.

The renumbering is not expected to cause any downtime. If you experience problems viewing your website after the IP address has been changed try clearing your browser's disk cache and/or clearing your computer's dns cache. If neither one of those options work, try rebooting your computer or your router/modem.

The problem some of you experienced this morning is that some Internet Service Providers took a long time to re-propogate sending your computer to the new IP.

I was down using Shaw until about an hour ago. It seems I'm now back online.

If anyone knows or is contacted by a member still experiencing problems please have them contact me directly at:
steve@xmarksthescot.com

**Silent Raven** · 4th June 11, 01:29 PM

Originally Posted by Steve Ashton

The renumbering is not expected to cause any downtime. If you experience problems viewing your website after the IP address has been changed try clearing your browser's disk cache and/or clearing your computer's dns cache. If neither one of those options work, try rebooting your computer or your router/modem.

The problem some of you experienced this morning is that some Internet Service Providers took a long time to re-propogate sending your computer to the new IP.

I was down using Shaw until about an hour ago. It seems I'm now back online.

If anyone knows or is contacted by a member still experiencing problems please have them contact me directly at:
steve@xmarksthescot.com

thanks Steve!
i had already cleared both caches, but just now restarted my modem and computer, and am back on the site now. thanks for the info!

**Steve Ashton** · 4th June 11, 03:49 PM

Just remember the magic words.

Òpen the door please HAL.``

**Silent Raven** · 4th June 11, 04:17 PM

still having some strange issues, it seems the site works but not if the 'www' is in the address bar. hoping it will go away in time, as it make navigating the site a bit difficult.

**Santa Wally** · 4th June 11, 06:33 PM

I had the same problem ALL DAY, it started when I simply tied to click to the the next page of the thread that was on my screen from last night. I kept trying to log in at different times throughout the day. Didn't have a problem with any other site.

I finally copied and pasted the error message to an email and sent it to the "adminisrator". Ten minutes later I got a reply from Christine at vervehosting: Try clearing your browser's cache, clearing your dns cache, rebooting your computer or rebooting your dsl router. I don't understand all the computer terminology, so I closed out programs, shut down and restarted my computer. Problem resolved. Sure glad to be back.