This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

500 Error When Signing Into Site On User Profile

  • 2 antwoorde
  • 0 hierdie probleem
  • 1 view
  • Laaste antwoord deur WiebuschDD

more options

Hello,

I am new to the community here so thank you all for your posts. I am having an issue authenticating into a site on my user profile. When I log into the site on a private window in Firefox or another browser such as Chrome or Edge I do not get the 500 error. Are there specific settings I need to change on my profile that are blocking me from accessing the site? I have cleared cache and cookies and the browser is updated. I have attached an image of the error I get when logging in. If anyone can offer guidance it would be greatly appreciated.

Thank You!

Hello, I am new to the community here so thank you all for your posts. I am having an issue authenticating into a site on my user profile. When I log into the site on a private window in Firefox or another browser such as Chrome or Edge I do not get the 500 error. Are there specific settings I need to change on my profile that are blocking me from accessing the site? I have cleared cache and cookies and the browser is updated. I have attached an image of the error I get when logging in. If anyone can offer guidance it would be greatly appreciated. Thank You!
Aangehegde skermkiekies

All Replies (2)

more options

Try to enter about:config in the address bar and set network.http.http3.enable = false, then restart.

more options

@TyDraniu Hey Ty, thanks for the response. Unfortunately that did not correct the issue.