What Happened?

[Peter Parker]

Yesterday I received error messages when I tried to log in or view a thread. I know I was not alone but the time stamps indicated that others were able to post.

What happened? Can I suggest that when things like this occur the front page contain a warning? will anyone pay attention to that suggestion?

 

[John Nv]

Yesterday I received error messages when I tried to log in or view a thread. I know I was not alone but the time stamps indicated that others were able to post.

What happened? Can I suggest that when things like this occur the front page contain a warning? will anyone pay attention to that suggestion?

Same here.

 

[TheKrell]

Yesterday I received error messages when I tried to log in or view a thread.

I got the Securi timeout message yesterday. But I waited a few minutes and then it worked. Is that the error message you got?

 

[Scott Greczkowski]

We were traveling yesterday so I didn’t know it was happening. And it was only happening in some browsers.

We can’t post an announcement about it if we don’t know about it.


Sent from my iPhone using SatelliteGuys

 

[Peter Parker]

OK. So what happened. I tried Firefox, Chrome and the new Edge and they al failed. Just trying to understand what happened. Everyone knows I am nosy.

 

[KE4EST]

OK. So what happened.

Big cookie or header error

Today I've been getting a 400 error when using my usual browser (Firefox) about "Request header or cookie too large". The offending cookie doesn't appear to be one from www.satelliteguys.us or satelliteguys.us as if I clear all of those, the problem remains. Does anyone have any insight as...

www.satelliteguys.us

 

[Peter Parker]

Ironically I cannot open that link. Perhaps I am not supposed to know. Are you guys planning a surprise party for me?

 

[KE4EST]

Ironically I cannot open that link. Perhaps I am not supposed to know. Are you guys planning a surprise party for me?

Well that is strange. I copied the answer below:

The fix was to add the following to our Nginx config file (Nginx is our Webserver software)

"large_client_header_buffers 4 16k;"

And that solved it.

 

[TRG]

I got the Securi timeout message yesterday.

I saw that message a few times a while back with the old software. I never saw it again after the XenForo upgrade. [Knocking on wood]