One of our site participants is getting a 406 error that is blocking access. Any suggestions?

I get the same error - only at work. Assumed it was a firewall issue at work.

I get it consistently on my iPhone. It is Error 406 on Safari. I don't have issues on any other device.

Just change to open using Microsoft Edge

406 is generally a server level error where access is blocked by Mod Security (assuming an Unix server).

Depending on the web host, this could be automatically configured based on several things including IP range/location, browser, device type, etc.

The best thing to do for this would be for Yosef (or somebody) to take a look at your IP address and see if it's blocked so they can whitelist it.

I have had it happened using Safari and Firefox. Now using Microsoft Edge for the last week.

Same here. Went on vacation Sunday and blocked my cell when i got around 50 miles from myrtle beach. Must think I'm a beach chicken fan.

I was having the same issue using Safari. Went into Safari under Settings and did the Clear History and Website Data. That cleared up the issue.

Interestingly, mine is error is on Google Chrome. I can open the cabin on Microsoft Edge and Safari just fine. I'm in Asheville for what it's worth and laptop.

Fine on PC but get the same error on cell for last week or so

I began having the same problem with the 406 error. I went incognito on both my laptop and cell and now have no issues.

WASU 93 wrote: ↑

Mon Sep 20, 2021 4:51 pm

I get it consistently on my iPhone. It is Error 406 on Safari. I don't have issues on any other device.

Same for me

Apps03 wrote: ↑

Tue Sep 21, 2021 9:34 am

Fine on PC but get the same error on cell for last week or so

Same issue started 3 days ago. PC fine, cell phone, no dice.

Everyone having differing experiences is pointing to a recent update from the web host for their mod_security toolkit.

Having issues on both my laptops. I use chrome, but when I browse in incognito mode the website does just fine.

Glad it's not just me lol, I've had it for several months now but using incognito mode on Chrome fixed it.