Unable to login with Firefox 131+

Installation Issues
1

Hello,

Since updating Firefox to version 131, I can’t connect to Passbolt (the extension works fine).
I had Firefox dev edition in v131 and Firefox standard in v130, I could not connect on the dev edition but could on the standard. Now Firefox standard is also in v131.
It’s the same problem as Login Redirected to Login Page · Issue #203 · passbolt/passbolt_api · GitHub, I tried adding an exception but it didn’t work.
In about:preferences#privacy I have the standard setting.
Thanks

1 Like
2

Hi there,

I couldn’t reproduce the issue with Firefox 131 on my end, but let’s try a few troubleshooting steps to narrow down the cause.

  1. Browser extensions conflict: Sometimes, other browser extensions can conflict with Passbolt. Could you try disabling all other extensions and restart Firefox? Then, attempt logging in again to see if this resolves the issue.

  2. Checking extension logs:

  • Navigate to about:debugging#/runtime/this-firefox in Firefox.
  • Find the Passbolt extension and click on the Inspect button.
  • Go to the Console tab and try login to passbolt again to see if any errors appear. You can share the logs here, and we’ll help analyze them.

Let me know how it goes or if you need more guidance on gathering this information.

3

Hi,

  1. It didn’t work, same problem.
  2. Here are the logs
TabService::exec(id: 13, url: https://…/auth/login?redirect=%2F): Navigation detected. index.min.js:2:587940
TabService::exec(id: 13): No content script application acknowledged presence on worker runtime memory port. Error: Attempt to postMessage on disconnected port
    emit moz-extension://ec016543-bc33-48f1-8e71-b16a813f9e37/index.min.js:2
    request moz-extension://ec016543-bc33-48f1-8e71-b16a813f9e37/index.min.js:2
    request moz-extension://ec016543-bc33-48f1-8e71-b16a813f9e37/index.min.js:2
    exec moz-extension://ec016543-bc33-48f1-8e71-b16a813f9e37/index.min.js:2
index.min.js:2:588594
The pagemod "Recover" should implement canBeAttachedTo. Default false. index.min.js:2:17002
The pagemod "Setup" should implement canBeAttachedTo. Default false. index.min.js:2:17002
The pagemod "Auth" should implement canBeAttachedTo. Default false. index.min.js:2:17002
The pagemod "App" should implement canBeAttachedTo. Default false. index.min.js:2:17002
The pagemod "QuickAccess" should implement canBeAttachedTo. Default false. index.min.js:2:17002
The pagemod "InFormCallToAction" should implement canBeAttachedTo. Default false. index.min.js:2:17002
The pagemod "InFormMenu" should implement canBeAttachedTo. Default false. index.min.js:2:17002
The pagemod "AccountRecovery" should implement canBeAttachedTo. Default false. index.min.js:2:17002
TabService::exec(id: 13): Trigger pagemods identification process. index.min.js:2:589149
TabService::exec(id: 13, url: https://…/auth/login?redirect=%2F&locale=fr-FR): Navigation detected. index.min.js:2:587940
TabService::exec(id: 13): Content script application acknowledged presence on worker runtime memory port. index.min.js:2:588459

Thanks

4

I have the same issue.

5

Same problem here. My extension logs are similar :+1:

6

Hello,

We’re not able to reproduce this yet, can you tell us more:

  • Have you tried restarting firefox? The OS?
  • What is your operating system, which version?
  • Do you have any custom cookie configuration? Under: about:preferences#privacy
  • Have you tried deleting the cookies for the passbolt domain?
  • Do you use https:// to access the service? Or http://? Is it a normal domain.tld or something custom?
  • If you deactivate the passbolt extension, do you see the passbolt landing page correctly?

If you have time this afternoon, and can join on a call to help us reproduce, you can send us an email at support@passbolt.com mentionning this thread. Thank you for your patience.

7

Hi,

  • I’ve restarted Firefox and my computer
  • I’m on macOS Sequoia 15.0.1 but the issue was present with Sonoma too
  • No, standard configuration for cookies
  • Yes I have deleted the cookies for the Passbolt domain and looked in local storage too
  • I use https with a certificate from Certbot on a domain .ovh
  • If I deactivate the extension I see the page with the input asking for my email address
8
  • Restarted my computer and Firefox too
  • On my work machine I have Windows (Version 22631.4169)
  • I use Firefox in strict privacy mode, I turned it off and on, but no difference
  • I deleted all cookies and checked also the local storage
  • we use HTTPS with an Let’s Encrypt certificate on an .de domain, the server is only available in our local windows domain via VPN
  • if I also deactivate the extension, I see also the page with the input asking for my email address

For about an hour now, I have been getting an error message when I try to log in:

grafik

9

Mozilla just released a 131.0.2, do you experience the issue with this new version?

They mention fixing a security issue: Security Vulnerability fixed in Firefox 131.0.2, Firefox ESR 128.3.1, Firefox ESR 115.16.1 — Mozilla

10

Unfortunately, the new version has not fixed it.

I updated Passbolt to the newest version just in case that the cause of this problem is related to the installation itself, but that does not seem to be the origin of the issue.

11

Update:

I got it working again by deleting the cache directly in the Firefox settings under “Cookies and website data”. Deleting the data via the console is apparently not enough.

1 Like
12

Thank you for the update! I’m glad to hear that clearing the cache and cookies did the trick

13

Hi,
I confirm it worked for me too.
I had to select “all” for the interval.

14

I don’t want to lose all my cookies :frowning:
Any other way to fix this?

15

From here maybe: about:preferences#privacy
Click on “Manage data” and filter on your passbolt instance domain.

Note: prior to manipulating the memory, always ensure you have a copy of your recovery kit.

16

I had already considered that, but our Passbolt instance runs on password.company.tld, and Firefox unfortunately only allows to delete all cookies of the whole company.tld domain. I had already tried to delete only the cookies below password.company.tld with F12 → Storage → Cookies, but that didn’t resolve the problem.

I then installed Cookie Quick Manager – Get this Extension for 🦊 Firefox (en-US) which allows the deletion of cookies per subdomain and deleted password.company.tld, but that also didn’t resolve the problem. What worked in the end was to use Cookie Quick Manger to export the cookies of the subdomains that I cared about, then delete all cookies of company.tld in the Firefox settings, and then restore the exported cookies that I cared about. No idea why deleting the cookies of password.company.tld wouldn’t work :X

17

Hello,

I have exactly the same problem here with FireFox unlike the extension which continue to work as expected.
Windows 10 FireFox 131.0.2.
No problem with Edge.

Regards,