UPDATE: TUES. 9/17/2024 - SERVER REPAIRS ARE & HAVE BEEN IN PROGRESS!!

[jmpeal]

OMG. I can actually see this site again. Either take the time to fix it correctly or just pull the plug. Quit letting this page die slowly.

[SWalt]

Maybe President Harris can have her people fix Calguns.

Rumor is she did fix it before the election.

[Usual_Suspect]

A number of us have been kvetching/complaining/commenting on .org that we haven't been able to get to the site for 36 hrs. or more. It's working, sort of, for the moment; but, I just had another 504 Gateway Error while posting, only to open another window and find the thread posted.

So...

Hopefully, this all gets fixed by the first of the year and we can get on with things.

I had the same issue yesterday, 504, tried to post again, and it was a duplicate of the post with the 503. I get 503 constantly, it's so bad, most of the time I can't access the site at all, sometimes for days on end.

[CessnaDriver]

I had the same issue yesterday, 504, tried to post again, and it was a duplicate of the post with the 503. I get 503 constantly, it's so bad, most of the time I can't access the site at all, sometimes for days on end.

Same. It's showing no signs of improving after months.

[GetMeCoffee]

It is running extremely fast for me this morning!

[jarhead714]

It is running extremely fast for me this morning!

Mornings are strong, after 3pm Pacific Time there’s a 50/50 chance.

[antilamr]

Mornings are strong, after 3pm Pacific Time there’s a 50/50 chance.

My mornings are 50-50. Either it's fast or 504. I usually get online 1 out of every 12 times I try. I'm trying to go online all times of the day/night also. I've been going to "that other site" more and more these past 9 months and they're always so fast it's almost instantaneous!

[Usual_Suspect]

Mornings are strong, after 3pm Pacific Time there’s a 50/50 chance.

I have to agree, early morning I can access with little to no issues. Later in the afternoon, it's inaccessible for me as well.

[DougJ]

The first time I’ve been able to get on in at least week, again. It goes like this:
Nothing
Nothing
504
Nothing
504
504
504
Nothing

Rinse and repeat. I normally try when I’m having a cup of coffee in the morning, and have failed every time. Typically I move on and don’t think about it again. Currently it’s about 1645 and I got right on.

I assume Kes has verified that’s it’s not a prolonged DOS attack, so it’s still just hardware and software issues? For phucks sake. The habit of getting on is broken for sure, just stubbornness keeping me coming back now.

[DougJ]

IMG_0669.png s IMG_0666.png IMG_0668.png IMG_0667.png This is my normal, still. 😡

[TrappedinCalifornia]

There is no consistent 'time of day' where I can get access or access which allows for long enough functionality to read and/or post more than a couple of times.

I try at various times and when I can even get access to the site, I can't always get on and when I can get on, I can't always post and when I can post, I typically can't post for long.

Such is consistent with it being a 'resource' issue or, as DrJonesUSA stated, once traffic reaches a certain point, the system crumbles.

I sincerely hope it's being worked on and one day (soon) it'll be back to a level of functionality where we can readily access the site and post. "Personal niceties" (where you can adjust things to meet your personal taste/style) and functional searches are likely to take longer.

[LA Rondo]

Yes, it's a travesty. Still, I will try and post some handguns for sale in the market place.

[zatoh]

I'm posting while I can. Hopefully it stays up!

[MountainLion]

I can’t remember when CGN has worked so well, but then again I can’t remember what I had for dinner last night.

Who is this Alzheimer guy everyone keeps talking about?

Hopefully it stays up!

You know they have pills for that now? Just sayin'

[GiveMeMo2A]

once traffic reaches a certain point, the system crumbles.

So, this type of behavior is common in a system that services oldest request first. The second you hit capacity, every request takes infinite time and absolutely no request is ever satisfied. Don't know if that is the issue here, but the fix is trivial, you merely service only the last request, first, to completion, and if there is any room, the request before it and so on. But this sort of fix would be at the inner working of the underlying software. Easy to see by putting the db on a really slow drive and then seeing how many completions per second there are, 0 or n. With access to adequate logs, would be trivial to spot in logs as well.