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.

getting blocked from commercial web sites

  • 4 antwoorde
  • 0 hierdie probleem
  • 1 view
  • Laaste antwoord deur cor-el

more options

I tried to get on Lowes.com and keep getting a message that I cannot access this server from my account. Is Firefox blocking this?

I tried to get on Lowes.com and keep getting a message that I cannot access this server from my account. Is Firefox blocking this?

All Replies (4)

more options

It works for me. see screenshot Can you show us the issue?

more options

You can remove all data stored in Firefox for a specific domain via "Forget About This Site" in the right-click context menu of an history entry ("History -> Show All History" or "View -> Sidebar -> History").

Using "Forget About This Site" will remove all data stored in Firefox for this domain like history and cookies and passwords and exceptions and cache, so be cautious. If you have a password or other data for that domain that you do not want to lose then make sure to backup this data or make a note.

You can't recover from this 'forget' unless you have a backup of involved files.

If you revisit a 'forgotten' website then data for that website will be saved once again.

more options

This did not solve my problem. It got me to the site- Lowes.com, and I was able to see it, but when I tried to use it I got the same message. See attached image.

more options

"You don't have permission to access..." errors are characteristic of a firewall that protects the server against misuse and this firewall thinks something is suspicious about the HTTP request. If you use a proxy or VPN then try to use a direct connection. You can try to clear the Cache and remove the Cookies for websites that cause problems via the "3-bar" Firefox menu button (Options/Preferences) to see if that fixes it. I've also seen cases where having "Resist Fingerprinting" enabled caused this issue to occur.