Is CI starting to die?

[Goat]

I've been having consistent trouble trying to make posts, and funpost recently. Notably getting the same error screens I get when I have to delete my cookies here. Are the servers starting to flicker?

edit: burp count since topic has been made: 2 many to count and CI was down for a few days

[Nano]

It was doing fine before you brought all your memes here...

Coincidence? I think not.

[Flame]

The memes end here, monster...!

I encountered a good few errors earlier, myself. Something's definitely up with the server, I think.

[Goat]

The memes end here, monster...!

Appropriate responses to wit aside, could it be that ever since the site revamp during a time when usercount was low. It wasn't meant to handle as many people visit it now?

[retrolinkx]

If you're referring to the errors that sometimes appear on the site. It's been a randomly occuring problem for users for a year or two now.

Mooncow/Fusion will sort it out one way or another.

[Goat]

So it's all more than likely going to persist for a while until it just goes away again?

[Midnite]

If it's the nginx error, I remember Pinka told me it had to do with the cookies or something causing that. If you delete the CI cookie (or history, whatever it was, I forget what exactly since it's been a while), it should hopefully go away.

[Goat]

Not quite, the cookie error is an error that occurs when look at certain topics.

This is a timed out error that occurs sporadically. If I wasn't allowed to see certain topics, I could as easily press the back button and look at a different topic. Then it's a clear diagnosis of the cookie error.

[Pentagrami]

i keep getting an nginx error only at certain hours of the day on /all pages/ even non forum, anything under the hippotank domain, mostly all morning

i thought this is what you meant but?? if there are these many identifiable and persistant different errors then that raises a red flag

[Goat]

The only consistent one would be the cookie error

[Jeffery Mewtamer]

There was an outage yesterday that lasted roughly the time it took me to go through my morning read of another forum I frequent, but the only error I get with any frequency worth noting is "the submitted form was invalid" when I take too long composing a message, and all that does is force me to press submit again.

Only error I get in regards to cookies is rarely being logged out despite being permanently logged-in, but that also happens on the other forum I frequent using this forum software and even forums using completely different forum software, and it doesn't happen often enough to bother me.

For the record, I'm using Firefox 45 on a Linux box, and have to question how many of the issues from people with more frequent issues are using a less compatible browser.

[Ivogoji]

I've been locked out CI for most of the past two days. Has this happened to anyone else?

[chaoadventures]

^Same, except it only was yesterday.

[Tsui]

Yeah, it errored for me too, from mid-yesterday to midday today. I wonder what's going on?

[Lamby]

i couldn't access yesterday

[Crazo3077]

I blame Brexit

[Rajikaru]

I blame Crazo

[KeatonLabs]

oh god is it back finally?

[Crazo3077]

At least for the moment

[KeatonLabs]

I HAVE HOPE

[Tsui]

please never do that again

[chaoadventures]

WHAT YEAR IS IT

[Goat]

[BlackLuigi7]

http://vocaroo.com/i/s0QD7yy9CdTQ

[Mooncow]

Sorry guys, touched on this in my recent announcement here so you guys are kept up to date.

In terms of the error - it's nothing to do with cookies. In understandable terms, what seems to be happening is the server starts to get "clogged" and then when it can't take it anymore it crashes. I'm working on the back-end and sorting out any bits of configuration that could be causing it. My current server setup is a lot better than the old one, as I have a whole server to myself and not sharing it with other websites, so it can definitely be fixed.

Sorry for the recent outage and thanks for your patience.

Edit: The reason cookies/cache was brought up before is because after the error was fixed (server was restarted) some people still had the error page. Clearing your browsers cache will ensure you will get the latest site page displayed.