[BUG] Proton Passkey 'error 'module not initiated'.' #201

Flatly4 commented 2025年11月16日 11:46:50 +01:00

Confirmation Checklist

• I confirm that this issue occurs on the latest release of Phoenix. You can check what the latest version is on the Releases page.
• I confirm that this issue has NOT already been reported on the Codeberg issue tracker, the GitLab issue tracker, and/or the GitHub issue tracker.

What web browser(s) are you using with Phoenix?

Firefox

Other

No response

What operating system(s) are you experiencing this issue on?

Other

Other

Pop_OS 24.04 LTS

What version of Firefox/Gecko and Phoenix are you using?

145.0 (Phoenix: 2025年11月07日.1)

If you remember, what version of Firefox/Gecko and Phoenix did you first notice the issue on?

No response

Does the issue occur on a new browser profile?

• Yes
• No

Please share your browser's distribution ID.

default

Please share your browser's update channel.

release

Please share a list of your currently installed browser add-ons/extensions, as well as the versions you have installed.

Proton Pass v1.32.11

Please explain the issue you are experiencing.

When I have been trying to set-up a passkey using Proton Pass, I would receive this pop-up over the Proton Passkey pop-up error 'module not initiated'.. This was for all sites I attempted to create a passkey for; discourse forums, codeberg, google, mastodon, github.

This would also occur when trying to log in using passkeys for sites like https://forum.f-droid.org

After a search through the bugs, I saw this similar bug and after trialling that solution, I was able to create and log in using passkeys.

Please provide detailed steps to reproduce the issue.

Install Proton Pass
Visit https://forum.f-droid.org, go into settings and create passkey

### Confirmation Checklist - [x] I confirm that this issue occurs on the **latest release** of Phoenix. You can check what the latest version is on [the `Releases` page](https://codeberg.org/celenity/Phoenix/releases). - [x] I confirm that this issue has **NOT** already been reported on [the Codeberg issue tracker](https://codeberg.org/celenity/Phoenix/issues), [the GitLab issue tracker](https://gitlab.com/celenityy/Phoenix/-/issues), **and/or** [the GitHub issue tracker](https://github.com/celenityy/Phoenix/issues). ### What web browser(s) are you using with Phoenix? Firefox ### Other _No response_ ### What operating system(s) are you experiencing this issue on? Other ### Other Pop_OS 24.04 LTS ### What version of Firefox/Gecko and Phoenix are you using? 145.0 (Phoenix: 2025年11月07日.1) ### If you remember, what version of Firefox/Gecko and Phoenix did you first notice the issue on? _No response_ ### Does the issue occur on a new browser profile? - [ ] Yes - [ ] No ### Please share your browser's distribution ID. default ### Please share your browser's update channel. release ### Please share a list of your currently installed browser add-ons/extensions, as well as the versions you have installed. Proton Pass v1.32.11 ### Please explain the issue you are experiencing. When I have been trying to set-up a passkey using Proton Pass, I would receive this pop-up over the Proton Passkey pop-up `error 'module not initiated'.`. This was for all sites I attempted to create a passkey for; discourse forums, codeberg, google, mastodon, github. This would also occur when trying to log in using passkeys for sites like https://forum.f-droid.org After a search through the bugs, I saw this [similar bug](https://codeberg.org/celenity/Phoenix/issues/133#issuecomment-4989933) and after trialling that solution, I was able to create and log in using passkeys. ### Please provide detailed steps to reproduce the issue. Install [Proton Pass](https://addons.mozilla.org/en-US/firefox/addon/proton-pass/) Visit https://forum.f-droid.org, go into settings and create passkey

jahtnamas commented 2025年12月03日 04:37:17 +01:00

i'm not familiar with how proton pass works but the module error makes me think it uses native messaging host features. i'm having a similar issue with the plasma browser integration addon being unavailable along with keepassxc-browser being unable to connect to the desktop app, both of which use native messaging host features.

i'm not familiar with how proton pass works but the module error makes me think it uses native messaging host features. i'm having a similar issue with the plasma browser integration addon being unavailable along with keepassxc-browser being unable to connect to the desktop app, both of which use native messaging host features.

celenity commented 2026年06月01日 21:58:28 +02:00

Apologies for the very late/overdue response here...

@Flatly4

After a search through the bugs, I saw this similar bug and after trialling that solution, I was able to create and log in using passkeys.

So, to confirm, the issue resolved once you changed the value of extensions.webextensions.base-content-security-policy.v3 to script-src 'self' 'wasm-unsafe-eval'; upgrade-insecure-requests;?

If so, I would consider this expected - but it may be worth revising the default pref for this, since it’s caused other issues as well.

—-

@jahtnamas

At the cost of privacy and security, you can re-enable Native Messaging by setting webextensions.native-messaging.max-input-message-bytes to 1048576 and webextensions.native-messaging.max-output-message-bytes to 2147483647 (For reference, this is documented on the Web Compatibility page as well).

Apologies for the very late/overdue response here... @Flatly4 > After a search through the bugs, I saw this [similar bug](https://codeberg.org/celenity/Phoenix/issues/133#issuecomment-4989933) and after trialling that solution, I was able to create and log in using passkeys. So, to confirm, the issue resolved once you changed the value of `extensions.webextensions.base-content-security-policy.v3` to `script-src 'self' 'wasm-unsafe-eval'; upgrade-insecure-requests;`? If so, I would consider this expected - but it may be worth revising the default pref for this, since it’s caused other issues as well. —- @jahtnamas At the cost of privacy and security, you can re-enable Native Messaging by setting `webextensions.native-messaging.max-input-message-bytes` to `1048576` and `webextensions.native-messaging.max-output-message-bytes` to `2147483647` *(For reference, this is documented on [the Web Compatibility page](https://codeberg.org/celenity/Phoenix/wiki/Web-Compat#website-compatibility) as well)*.