Lazy Daze Owners' Group

Lazy Daze Forums => Lazy Daze General Info & Discussions => Topic started by: Jon & Loni on December 11, 2017, 06:43:19 pm

Title: Forum Outage
Post by: Jon & Loni on December 11, 2017, 06:43:19 pm
I thought I would see some discussion here, but apparently no one had my problem yesterday?  All day yesterday and continuing until I went to bed I could not access the forum on either my iPad or my PC. I kept getting “can’t connect to server” messages. I was able to freely connect with any other website at all times. Today, all is fine. Curious as to whether it was just my equipment somehow? — Jon
Title: Re: Forum Outage
Post by: Joan on December 11, 2017, 07:08:29 pm
No, not just you, Jon. My laptop (Windows) connected, but the iPad and iPhone would not; same message as you received. I solved the problem by wandering off to try to do something useful, figuring that the 'stars' would realign and the gremlins would eventually be vanquished; they did and they were.  ;) 
Title: Re: Forum Outage
Post by: Steve C on December 11, 2017, 08:03:25 pm
Sorry about the glitch  :'(

I updated the site/server IPV6 support and in so doing certain ranges of IP address were not properly being identified.  This resulted in the server firewall sending you to a blank page or giving an EMPTY_RESPONSE error.   This occurred only if you connected with IPV6 and only within certain ranges.

The problem was addressed this AM so it should no longer occur.

Whats IPV4 or IPV6 (http://mashable.com/2011/02/03/ipv4-ipv6-guide/#inrBPe8ZmOqShttp://)

Title: Re: Forum Outage
Post by: Duro on December 11, 2017, 08:56:51 pm
Thanks Steve for getting it fixed!!!!
Title: Re: Forum Outage
Post by: squeakytiki on December 11, 2017, 08:57:45 pm
I had the same trouble in both firefox and chrome on a windows pc.
Title: Re: Forum Outage
Post by: Jerry on December 11, 2017, 10:41:02 pm
at first I thought it was my computer because later that day I was able to get in and read some posts, but then no more. I figured it was a server problem and saw no need to post about it then. Thanks for the explanation and the fix!