Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече
Open

failure to use container tabs for different AWS accounts

chris.allison

Hi, I was a heavy user of the multi-account containers extension. Since FF now has that functionality built in I disabled the extension recently (more than a week ago). My company keeps FF up to date - currently on 153.0.3 aarch64

All tests have been performed with other extensions (ublock origin and auto-reader view) disabled.

Since the last update (last wednesday I think, 5th. Aug.) I've been unable to access the AWS or Azure portals from a container tab, though it works correctly from the 'bare' browser.

I've cleared cookies and site data for the whole browser (made no difference)

I've cleared cookies and site data for the container tab - this now allows me to sign into Azure (which is a prerequisite to signing into AWS), but AWS is still blocked with a microsoft message "We cannot sign you in, try a different user name"

If I use the bare browser, no container, I can sign into the AWS SSO portal correctly.

What can I check to help diagnose this? MacOS Tahoe 26.6.1 Firefox 153.0.3

regards

Chris

Hi, I was a heavy user of the multi-account containers extension. Since FF now has that functionality built in I disabled the extension recently (more than a week ago). My company keeps FF up to date - currently on 153.0.3 aarch64 All tests have been performed with other extensions (ublock origin and auto-reader view) disabled. Since the last update (last wednesday I think, 5th. Aug.) I've been unable to access the AWS or Azure portals from a container tab, though it works correctly from the 'bare' browser. I've cleared cookies and site data for the whole browser (made no difference) I've cleared cookies and site data for the container tab - this now allows me to sign into Azure (which is a prerequisite to signing into AWS), but AWS is still blocked with a microsoft message "We cannot sign you in, try a different user name" If I use the bare browser, no container, I can sign into the AWS SSO portal correctly. What can I check to help diagnose this? MacOS Tahoe 26.6.1 Firefox 153.0.3 regards Chris

Променено на от chris.allison

Всички отговори (1)

Hi Chris

I recommend that you keep using the add-on for now. Containers in Firefox is still a preview, for more information I recommend that you have a read of https://blog.mozilla.org/en/firefox/firefox-containers-preview/

Задаване на въпрос

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