Wellp.... We're back...



  • After nearly 24 hours of down time I finally got escalated to someone who knew what was going on and fixed the problem at digital ocean. That was awful, to say the least.

    Long story short, in order to address vulnerabilities in old Linux versions they force upgraded everyone with no regard for human life. We are back for now. I have a few other things I need to address.



  • @approxinfinity

    I was tired of seeing Error Milkshake! Error Milkshake!

    Thanks for restoring our life back!



  • Seriously, I did my actual work today. It was unsettling.



  • @Kcmatt7 Sounds awful



  • @Kcmatt7 My wife was wondering why our kitchen reno advanced so much in one day.

    @approxinfinity Thanks as always for keeping us in here. It was a great idea to put the twitter updates at the URL.



  • Thanks @approxinfinity ! I thought for a while it was just me - that i was banned for life because of my dislike of OAD’s. hehe



  • @nuleafjhawk There was probably a lot of that going around. I thought I was banned for being pessimistic about possible sanctions.



  • One day I went to work and my key fob wasn’t working anymore. Thought I was fired. I wasn’t. But this is exactly how that felt lol.



  • I was frantically contacting poor @approxinfinity on twitter dot com



  • Thanks for giving me a good laugh guys. I had a little storm cloud over my head the last day.



  • Btw I think the redirect to Twitter was a bad idea, as DNS propogation was spotty and probably left the site down for some longer than otherwise.

    We should come up with an emergency procedure before this happens again. I’ll see what I can do to get a plan in place.



  • @approxinfinity I just got on now.



  • Can’t get on with my computer again. I’m sure you’re working on it but just wanted to provide info



  • My iPad won’t work



  • Might be a local dns cache issue, here’s how youd flush it on iPad. http://osxdaily.com/2015/03/31/clear-dns-cache-ios/

    You can clear the local dns cache on whatever device, google " flush dns cache <devicename> "

    Or it could be the dns just hasn’t propagated yet. It should have, though.



  • I’m on my phone



  • Off and on here.



  • @Crimsonorblue22

    FWIW, the iPads are working fine and so are my Android phone and all the Windows computers.



  • alright. I tried to reset the dns settings and then add our ip back. let me know if that doesn’t resolve it today.

    Sorry guys!



  • So according to the guys who we have our domain name registered with (who I set up the twitter redirect with), everything is configured correctly and the reason we are seeing the twitter account still is because of local caches on our browser, the recommended solution being to google clearing dns cache for our respective browsers and/or not accessing the site for a while and allowing the cache to get stale and invalidated the next time you go to kubuckets on your browser.

    I think the moral of the story is, don’t redirect your site to twitter in a case like this? F!(#%. So this should clear up completely in several days, like a bad cold. Glad this was the off season.



  • iPad and iPhone are both working now, thx. Been toooo long!



  • @approxinfinity Thank you for your time and effort in this - I was thinking what the hell lol. – ROCK CHALK ALL DAY LONG BABY


Log in to reply
 

Looks like your connection to KU Buckets was lost, please wait while we try to reconnect.