Redirect loops on Firefox

[Sennalen]

I normally use Firefox, and it from time to time, the Wikipediocracy forum doesn't load but instead appears to be stuck in a redirect loop. It will be like that for 30-60 minutes and then fine again for awhile. I tried Edge and it hasn't exhibited the same problem

[rnu]

I normally use Firefox, and it from time to time, the Wikipediocracy forum doesn't load but instead appears to be stuck in a redirect loop. It will be like that for 30-60 minutes and then fine again for awhile. I tried Edge and it hasn't exhibited the same problem

I use Firefox too and have not experienced this. Have you tried private mode? Depending on your settings that will disable most of your add-ons.

[Giraffe Stapler]

I normally use Firefox, and it from time to time, the Wikipediocracy forum doesn't load but instead appears to be stuck in a redirect loop. It will be like that for 30-60 minutes and then fine again for awhile. I tried Edge and it hasn't exhibited the same problem

Can confirm. It's happened to me a few times today. I have also seen the occasional SQL error this week.

[Vigilant]

I normally use Firefox, and it from time to time, the Wikipediocracy forum doesn't load but instead appears to be stuck in a redirect loop. It will be like that for 30-60 minutes and then fine again for awhile. I tried Edge and it hasn't exhibited the same problem

Can confirm. It's happened to me a few times today. I have also seen the occasional SQL error this week.

I get the SQL error about 10 times a day.
F5 is my friend.

[Lurking]

SQL error is somewhat frequent here as well, and less commonly "misloads" where it does load the page, sort of, but the style elements are all over the place and it clearly failed to load some of them.

Don't think I've had a redirect loop of the type Sennalen described, though.

[rnu]

I've had the SQL error multiple times. But reloading once, sometimes twice has so far always worked.

[Elinruby]

I've pointed SQL errors out to Zoloft a few times. I have seen those and General error quite a bit lately but there has been a series of storms in my area with some intermittent Internet and power outages so I haven't reported those. I don't think this would cause a SQL error that talks about too many connections, but the General error stuff could be about the timeouts I also get on Wikipedia, so I don't want to waste his time unless I am sure it isn't on my end. Usually though my ISP is bulletproof fibre with constant uptime regardless of active wildfires or atmospheric rivers, both a feature of living here. No problem at all all for the previous four years

[greyed.out.fields]

...

...

I get the SQL error about 10 times a day.
F5 is my friend.

Vigilant, is your F5 friend electric?

Mods: please feel to delete this post. I'm just having a bit of fun here.

[Midsize Jake]

We're overdue for some upgrades, and that's my fault because I'm the one who's supposed to do them. However, there's a problem: The shared Bluehost servers we're on are all set up with MySQL 5.6, and the most current versions of both Wordpress and phpBB are well past that in terms of what's "optimal" for them, version-wise.

However, that's not the cause of the SQL errors; it may be exacerbating the problem, but the cause is almost certainly another Bluehost customer on the same shared DB server who's just eating up all the available bandwidth and/or CPU cycles. (They're not going to tell us who it is, though.)

And FWIW, I've been getting the General SQL errors too (starting about a month or so ago), about once or twice a day on average. And I don't think it's a coincidence that this started around the same time as a major marketing push by Bluehost, including a Super Bowl ad.

As for ways to improve the situation, the problem there is that we're already on the $15/month "Pro" plan, and once you move past that, the costs go up quite a bit — a Virtual Private Server (which I'd have to maintain myself) is more than twice as expensive, and a "Dedicated" server plan (which they would maintain) is 6 times as expensive. I could afford that for a year or two, but the fact is, both of those higher-level plans are Total Overkill for the amount of bandwidth and storage we actually need. What we're experiencing now is just not supposed to happen, basically.

So the most sensible solution (in terms of just minimizing/eliminating the errors) is to move to a new provider, which is a fairly big deal logistically. I've done it once already though, when WR moved from HostGator to Dreamhost, or was it vice-versa, I forget which now... Some of the old-timers here might remember that we were only offline for a few hours, and I might be able to do it even more quickly now because of my new fancy-ass fiber-optic connection. But a lot of things can go wrong, too, so I'm still viewing that as a last-resort sort of option until the timeouts (and other errors?) just get to be completely intolerable.

[Elinruby]

We're overdue for some upgrades, and that's my fault because I'm the one who's supposed to do them. However, there's a problem: The shared Bluehost servers we're on are all set up with MySQL 5.6, and the most current versions of both Wordpress and phpBB are well past that in terms of what's "optimal" for them, version-wise.

However, that's not the cause of the SQL errors; it may be exacerbating the problem, but the cause is almost certainly another Bluehost customer on the same shared DB server who's just eating up all the available bandwidth and/or CPU cycles. (They're not going to tell us who it is, though.)

And FWIW, I've been getting the General SQL errors too (starting about a month or so ago), about once or twice a day on average. And I don't think it's a coincidence that this started around the same time as a major marketing push by Bluehost, including a Super Bowl ad.

As for ways to improve the situation, the problem there is that we're already on the $15/month "Pro" plan, and once you move past that, the costs go up quite a bit — a Virtual Private Server (which I'd have to maintain myself) is more than twice as expensive, and a "Dedicated" server plan (which they would maintain) is 6 times as expensive. I could afford that for a year or two, but the fact is, both of those higher-level plans are Total Overkill for the amount of bandwidth and storage we actually need. What we're experiencing now is just not supposed to happen, basically.

So the most sensible solution (in terms of just minimizing/eliminating the errors) is to move to a new provider, which is a fairly big deal logistically. I've done it once already though, when WR moved from HostGator to Dreamhost, or was it vice-versa, I forget which now... Some of the old-timers here might remember that we were only offline for a few hours, and I might be able to do it even more quickly now because of my new fancy-ass fiber-optic connection. But a lot of things can go wrong, too, so I'm still viewing that as a last-resort sort of option until the timeouts (and other errors?) just get to be completely intolerable.

Nod, are there any failover.options? Or maybe the same host moving us to a less-trafficky server? or maybe just working on the SQL throttling?

Just brain storming

As I told Zoloft the problem is always short-lived and I can live without WO for seconds at a time

I have screenshots.of recent errors; PM me if that helps you at all

[Zoloft]

Jake, if you need my brains or some money PM me and I can help.
I have been considering paying the domains for a ten-year period and then adding a codicil to my will.

[iii]

Just so y'all are aware, I experienced this 30-minute redirect loop about five times yesterday. It resolved itself most of the time and turned into a Bad Gateway error one time.

[Elinruby]

No redirects over here on Android but a different gateway error than usual, repeatedly for about two minutes. In case that tells anyone anything

Screenshot_20240312-223451.png

[Carcharoth]

In case it helps, I got this issue as well yesterday, for a sustained period of time (rather than just a few minutes). From my Android phone. Good luck with getting it all sorted, and please do have backups of all the content if moving provider. (And good luck as well with the longer-term legacy planning - several forums I know and frequent probably don't have that sort of planning and I wish they did, or that it was easier to sustain forums over several generations [and archive and wind them up properly at the end of their natural life-spans].)