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

Walgreens prescription disabled

  • 6 ŋuɖoɖowo
  • 0 masɔmasɔ sia le wosi
  • 25 views
  • Nuɖoɖo mlɔetɔ TrainClaude

more options

I have been using the Walgreens web site to manage my many prescriptions without problems. Now, most of the Walgreens web site still works but the two menu options that need to display my personal prescription details fail with the display "Sorry, an unexpected error occurred. Please try again later." I initially thought that a Walgreens update might be in progress so just waited. Walgreens support gave me the same answer that there was probably web site maintenance in progress. After 4 days of the same problem and answer, I ported enough information to login in to Walgreens with the Microsoft Edge browser and access to my prescription information worked without a problem. I believe this problem with Firefox started around the time I updated to 117.0.1 but I might not have this perfectly correct. I was just notified to update to 118.0 and did so. Firefox access still fails and Edge access still works. Thanks for any help you can provide. Windows 10

I have been using the Walgreens web site to manage my many prescriptions without problems. Now, most of the Walgreens web site still works but the two menu options that need to display my personal prescription details fail with the display "Sorry, an unexpected error occurred. Please try again later." I initially thought that a Walgreens update might be in progress so just waited. Walgreens support gave me the same answer that there was probably web site maintenance in progress. After 4 days of the same problem and answer, I ported enough information to login in to Walgreens with the Microsoft Edge browser and access to my prescription information worked without a problem. I believe this problem with Firefox started around the time I updated to 117.0.1 but I might not have this perfectly correct. I was just notified to update to 118.0 and did so. Firefox access still fails and Edge access still works. Thanks for any help you can provide. Windows 10

Ŋuɖoɖo si wotia

Does it still happen in a new profile? An easy way to test a new profile is to install Developer Edition and see if it happens there or refresh your existing profile.

Xle ŋuɖoɖo sia le goya me 👍 0

All Replies (6)

more options

Does it still happen in Troubleshoot Mode?

Helpful?

more options

Yes, it still happens in Troubleshooting mode. Also 118.0.1 just loaded. No change, same error.

Helpful?

more options

Ɖɔɖɔɖo si wotia

Does it still happen in a new profile? An easy way to test a new profile is to install Developer Edition and see if it happens there or refresh your existing profile.

Helpful?

more options

You can check for issues with Total Cookie Protection.

You can try these steps in case of issues with webpages:

You can reload webpage(s) and bypass the cache to refresh possibly outdated or corrupted files.

  • hold down the Shift key and left-click the Reload button
  • press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
  • press "Command + Shift + R" (Mac)

Clear the Cache and remove the Cookies for websites that cause problems via the "3-bar" Firefox menu button (Settings).

"Remove the Cookies" for websites that cause problems:

  • Settings -> Privacy & Security
    Cookies and Site Data: "Manage Data"

"Clear the Cache":

  • Settings -> Privacy & Security
    Cookies and Site Data -> Clear Data -> [X] Cached Web Content -> Clear

Start Firefox in Troubleshoot Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration or if userChrome.css/userContent.css is causing the problem.

  • switch to the Default System theme: "3-bar" menu button or Tools -> Add-ons -> Themes
  • do NOT click the "Refresh Firefox" button on the Troubleshoot Mode start window

If clearing cookies doesn't help, it is possible that the cookies.sqlite file in the Firefox profile folder that stores the cookies got corrupted.

Helpful?

more options

To ZeroKnight

Now that I have another helper, I am going to finish the path with Zeroknight so I am only working one solution at a time.

Yes, there was no error from the Walgreens site when I downloaded and used Developers Edition. Nothing seems to have been transferred from v118 of FF to the Developers Edition so I manually found the web site and entered my login manually. When I select either option that should display my prescription, they do display prescriptions without error.

So what is my next step and how do I perform it?

Thanks.

Helpful?

more options

Starting with zeroknight suggestion to download the developers edition, it was clear something in the profile must be the problem. I refreshed my usual version 118 but that did not solve the problem. I then looked for items NOT changed by refresh and decided to try cookies first. In v118, I deleted the "cookies and site data" for the Walgreens web site only and that solved the problem. The same error message appears once per session but even that does not disable my prescription data which now appears whenever it should. I am always concerned about what I might lose from deleting cookies but it appears that I only lost "My Walgreens" which was easily selected again. I also have used the vaccination portion of Walgreens' site and I have not tested that but I seldom use that function unlike prescriptions which I use frequently. I expect vaccinations to work but might have lost some easy-to-replace data. BTW, I don't know what was in all those cookies. Before deleting, there were over 100 for walgreens.com. After deleting and reloading the web site, there were only a little over 70 recreated. Well, I'll never know but it is great that it works. Thank you zeroknight and thank you cor-el. Claude

Helpful?

Bia biabia

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.