Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.
How to fix Access Denied to http://support.microsoft.com
After the January update Mozilla Firefox reloads to many Microsoft websites delayed Access Denied.
https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet Access Denied You don't have permission to access "http://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet" on this server.
https://support.microsoft.com/en-us/...-update-errors Access Denied You don't have permission to access "http://support.microsoft.com/en-us/help/10164/fix-windows-update-errors" on this server.
https://support.microsoft.com/en-us/...update-history Access Denied You don't have permission to access "http://support.microsoft.com/en-us/help/4529964/windows-10-update-history" on this server.
https://support.microsoft.com/en-us/...cle-fact-sheet Access Denied You don't have permission to access "http://support.microsoft.com/en-gb/help/20443/windows-10-battery-saving-tips" on this server.
https://support.microsoft.com/en-us/...l-numbers-when Access Denied You don't have permission to access "http://support.microsoft.com/en-us/help/937251/disk-drive-numbers-may-not-correspond-to-the-sata-channel-numbers-when" on this server.
There are several hundred browser websites that are opened after reboot with Mozilla Firefox reload.
How did this happen with a reload?
Is this a cache or cookie problem?
What was changed in the January Mozilla Firefox update?
Ccleaner requires that the browser is closed to clear cache and cookies.
If this were done the several hundred webpages would no longer reopen.
How can the Mozilla Firefox browser be modified so that it no longer displays Access Denied without losing the reload option for the hundreds of websites that are currently open?
(The browser typically has the default settings)
The Google Chrome and Internet Explorer browsers can open these websites without problems. Other end users opening the same websites with Mozilla Firefox did not see Access Denied.
For this problem please indicate:
What specifically happened with the January update that may have caused this problem? If it was not the January update what else could have caused this problem? How can the problem be fixed so that the webpages that are currently open can easily be reopened after a reboot with reload? What could have been done to prevent this Access denied problem?
All Replies (7)
I do not have this problem on the same version of FF on Windows 10. I think it is most likely a cookie issue. Do the sites in work in private mode?
If so, just click on the lock in the address bar when you are on the site and "clear cookies and site data". You can clear this for all sites in settings instead if you prefer.
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.
For this access denied troubleshooting I'd like to be able to reboot and reopen several hundred Firefox webpages.
Was the problem related to the January update? Was there corruption or some other problem that caused only the support.microsoft.com websites to display access denied?
Typically I rarely use the Firefox menu options so please indicate whether any steps could cause the inability to reopen the webpages.
Please be as specific as possible with the instructions, including any side effects or pitfalls.
Only when all of the many webpages are closed is Ccleaner used to clean cookies and cache.
There were four images added after clicking on the lock.
You may clear cookies and site data using the Remove cookies and site data button in the last image (first image works too).
There are essentially no pitfalls or side effects. You will just be logged out of your Microsoft support account. If you decide to clear cookies and site data for all pages (by going into settings) you will be logged out of all accounts on all sites.
That is it though. You can just log back in afterwards.
What was this part about CCleaner? You don't need to use that to clear your cookies and cache. Your can clear for all web sites in Firefox settings.
Maybe you'd like to take a look at this :
And just to show that you're not the only one with this problem on "support.microsoft.com":
These were the steps that fixed the access denied problem:
1) Click the lock on the Access denied webpage 2) Click security tab 3) Click Clear Cookies and Site Data
A reboot was not required.
The cause remains unknown?
Somehow a cookie got corrupted?
Thank you all for your help!
Access Denied You don't have permission to access "http://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet" on this server. Reference #18.2d15e8ac.1580920353.2dd4db75
Hi ineedhelpwithfirefox, the message you got is characteristic of a web application firewall used to deflect denial of service attacks and other unwanted traffic. If you were sending a high volume of requests, that could have been the issue? Usually it clears up after a couple hours.
Microsoft's support article on this indicates it is related to their use of the Akamai Content Distribution Network: https://support.microsoft.com/en-us/help/4492050/access-denied-when-visiting-a-microsoft-website-hosted-on-akamai
These were the steps that fixed the access denied problem: 1) Click the lock on the Access denied webpage 2) Click security tab 3) Click Clear Cookies and Site Data A reboot was not required. The cause remains unknown? Somehow a cookie got corrupted? Thank you all for your help!
The block typically is IP address based, not cookie based. Perhaps Firefox had cached the messages and wasn't trying to get the real pages again? Glad to hear you got it cleared up.