I have this problem too on my iMac (BigSur 11.6.8). It seemed to start when I upgraded to Firefox 103.0.

I am able to connect to Stubhub home page https://stubhub.com by using Safari.

Also, I can login to stubhub with Firefox by browsing to subdomain https://my.stubhub.com, but any action in the stubhub website that causes a jump to top domain stubhub.com results in 'Access Denied' .... this is even true when one attempts to 'Sign Out' of the account after having successfully logged in via my.stubhub.com.

Someone posted a workaround on Reddit, which is to change your Language/Locale temporarily from en-US (U.S. English) to en-GB (British English). Not sure whether that affects your payment currency...

See: https://www.reddit.com/r/firefox/comments/wc0soe/on_win_10_ever_since_updating_to_firefox_1030_64/

David's problem is exactly mine, and it must be a function of the 103.0 upgrade.

Mozilla needs to fix this. It should be up to me to figure workarounds.

Or I can just use Chrome and forget Firefox.

The "Access Denied" message originates from Stubhub's perimeter security system, sometimes called a Web Application Firewall. Someone (or "AI") programmed it to treat a normal Firefox request requesting content for the "en-US" locale as suspicious and refuse entry. The reason I think it's a firewall programming error is that I only need to change my language list to "en" or "wtf people" to bypass the firewall and use the site. (See attachment.)

Hopefully Stubhub is aware of and working on fixing this. Until then, do what you need to do to buy or sell your tickets.

In case you're curious about experimenting with the setting in the attachment, here's how:

(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button accepting the risk.

More info on about:config: Configuration Editor for Firefox. The moderators would like us to remind you that changes made through this back door aren't fully supported and aren't guaranteed to continue working in the future.

(2) In the search box in the page, type or paste intl.accept_languages and pause while the list is filtered

(3) Double-click the intl.accept_languages preference to display an editing field, and change the value to en then press Enter or click the blue check mark button to save the change.

To restore the original value later, use the reset button (left-arching arrow) at the right end of the row.

Not only helpful. This slam dunks the problem on my end. Kudos jscher2000 !!! Is there a way to prominently designate your post as 'the solution'. at the top of this thread?

I have an old macbook (running High Sierra) that still uses Firefox 101.... but it has the same problem as Firefox 103: access denied from stubhub.com.

This pretty well puts the guilt on stubhub.

One would think Mozilla would have some influence with stubhub to encourage them to fix THEIR problem.

It looks that the Stubhub website has a problem with "en-US" in the accept header like posted above and with some language combinations gives the "You don't have permission to access..." error. What appears to work is adding a second "en-XX" language or other not English language or if you have "en" as second then add a third language (don't have to be "en-XX" as something like "fr" works).

• https://support.mozilla.org/en-US/kb/choose-display-languages-multilingual-web-pages

See also my reply in this thread:

• /questions/1384662 Access denied

Had the same exact problem with Stubhub. Fix was spot on. Thank you!

I reported this problem in the Stubhub community forum and got a personal message from an 'expert there saying that the problem had been reported to Stubhub IT folks. That was two days ago, but the problem persists as evidenced by the fact that when I upgraded my mac to Firefox 103.1 a half hour ago, I had to manually eliminate 'en-US, from the intl.accept_languages setting (see jscher2000's instructions for this above) and make sure it's value is 'en'.

As soon as I did that, 'Access denied' was no longer a problem on Stubhub. Stubhub surely has millions of users in the US who routinely use Firefox for browsing. It's hard to understand why they haven't fixed this issue as of the time I am posting this message.