7/5/2018 - Planned outage - Noon to 6pm

[FJRoss]

For some reason, I can login from my phone but still get the down for maintenance message on my desktop. Both Chrome and IE.

Try clearing the browsing data (flush the cache). Also, type the address in the address bar instead of using a saved shortcut.

Sent from the Tapatalk app...

Tried clearing board cookies. Got maintenance message. Tried rebooting computer and typing in address. Also tried logout and login.
Might have to completely clear computer cache/cookies. Pain in the butt because it forgets passwords etc.

[wheatonFJR]

I have no problem posting...so obviously something went horribly wrong.

Ross, hope it works for you soon.

[FJRoss]

Tried everything including clearing cookies and browsing history in Chrome. No idea what's going on.

[gixxerjasen]

Was this the big move?
Looks like, new IP address.

[wheatonFJR]

Was this the big move?

Nah, I think we're still on that machine plugged into the hallway outlet. DON'T trip on the cord!

I obviously have no idea, but I think Wayne is still in the Detroit metro area.

I hope.

[extrememarine]

PM me if you need further assistance, we'll do what we can to sort out the issue on your device(s).

Tried everything including clearing cookies and browsing history in Chrome. No idea what's going on.

[extrememarine]

The site has been fully migrated to new host and hosting plan - so, yes, the "big move" is complete for FJRiders.com & Attacktheroad.com (which houses the storefront for event registration and the EOM website.

Was this the big move?
Looks like, new IP address.

[Uncle Hud]

Aw. So what am I supposed to do all afternoon?

Same thing I did. Hit the website URL two dozen times and get told "NO!"

[DesignFlaw06]

I want to say thank you to all of you for being patient during this process and recognizing that this is not a full time gig for Wayne or me.

This change should be for the best. The new host offers much better speeds and finally all the domains and hosting plans are under one account (it was 4 separate accounts and 3 different companies before). The install of the software is much cleaner and everything should be easier to manage from the behind the scenes perspective. There probably won't be many major changes until the fall when riding season starts to wind down. This move was a big item to get off my plate.

[bungie4]

We currently are in the midst of the worst outage since I started working here 7 or so years ago. 3hrs and counting.

I'm blaming Wayne.

[Steel_Gin]

Thanks guys for all the time you put in behind the curtain!!

[NTXFJR]

Thanks guys for all the time you put in behind the curtain!!

+1

[wheatonFJR]

I think Wayne threw the ban hammer and missed. Cav texted awhile back and said he's been trying to get on Riders for 12 hours.
<insert Cav Face here>

It might be him or it might be Wayne.

Where are you putting your money???

[Cav47]

It was a cookies and browser history issue on my phone. Wayne talked/texted me through it.

Echo the sentiments of those that have expressed their gratitude for all the work here.

I now can prob get going on a ride report from the little clockwise circle I rode awhile back.

[gixxerjasen]

<insert Cav Face here>

Let's not.

[extrememarine]

I think the next opportunity for fund raising is forum access tech support billed by minute...

Gees Bungie, maybe they need to hire the fjriders tech support team, we were only doen 5 hrs and 55 minutes...

Sent from the Tapatalk app...

[FJRoss]

Interesting... I tried everything to get back to the site on my work computer last Friday. Including multiple computer reboots, clearing browser cache and trying two different web browsers. I even tried accessing the site using mail links to notifications and by typing in the address (as opposed to bookmarked link). I had no issues with access from my phone or from home. Wasn't being deliberately blocked by work IT department but the FJRiders maintenance page may have been cached on the server. There were no issues with any other websites. Today, all is restored. Presumably the page cache "expired" as there was no deliberate action to restore it.

[extrememarine]

Maybe some of the resident corporate I.T. professionals here can shed some light on how a company I.T. department manages network traffic, and how that might have contributed to you not being able to get on the site from a corporate network.

When we made the DNS change, Tim and I monitored while we waiting for the site to load from the new location. Funny thing was that I saw the new logo first, and it took another half hour or so before Tim saw it from his connection.

Interesting... I tried everything to get back to the site on my work computer last Friday. Including multiple computer reboots, clearing browser cache and trying two different web browsers. I even tried accessing the site using mail links to notifications and by typing in the address (as opposed to bookmarked link). I had no issues with access from my phone or from home. Wasn't being deliberately blocked by work IT department but the FJRiders maintenance page may have been cached on the server. There were no issues with any other websites. Today, all is restored. Presumably the page cache "expired" as there was no deliberate action to restore it.

[bungie4]

Maybe some of the resident corporate I.T. professionals here can shed some light on how a company I.T. department manages network traffic, and how that might have contributed to you not being able to get on the site from a corporate network.

When we made the DNS change, Tim and I monitored while we waiting for the site to load from the new location. Funny thing was that I saw the new logo first, and it took another half hour or so before Tim saw it from his connection.

Interesting... I tried everything to get back to the site on my work computer last Friday. Including multiple computer reboots, clearing browser cache and trying two different web browsers. I even tried accessing the site using mail links to notifications and by typing in the address (as opposed to bookmarked link). I had no issues with access from my phone or from home. Wasn't being deliberately blocked by work IT department but the FJRiders maintenance page may have been cached on the server. There were no issues with any other websites. Today, all is restored. Presumably the page cache "expired" as there was no deliberate action to restore it.

Not funny at all. When you make a DNS change, in your case, you re-mapped your IP's, it takes a while for it to propagate to all the routers on the Interwebs. Think like when you move homes and you tell the phone company your new address. You had to wait a year before all the phone books were next delivered. Same thing, but usually happens within 24 hours.

[gixxerjasen]

Also, it depends on when you change your TTL (Time To Live). Time To Live is how long it takes for your DNS provider to refresh the DNS. If you are doing an DNS change then to shorten the downtime you shorten the TTL. However, you must change it x hours before you intend to do the change where x is the CURRENT TTL. I notice you shortened it down to 15 minutes but don't know when exactly that was done but it'd explain possibly why you saw the discrepancy.

There's a chance some DNS providers are ignoring the TTL and not refreshing often and it got stuck and they didn't get the update till much later.

Side note: Why set the TTL back up to a large number? Well, if you aren't going to be changing the DNS anytime soon there's no reason for a short TTL. A short TTL can cause a lot of network traffic too depending. However, the biggest reason, and I've been bitten by this one, is if your DNS host has an outage. Say your TTL is set to 4 hours. That means most will only check every four hours. If your DNS host has a 1 hour outage, there's going to be some trying to refresh during that time but largely your visitors won't see an issue and can continue surfing. However, if your TTL is set to 15 minutes and they have a 1 hour outage, you will have a minimum of 45 minute outage of your site.