charts
charts copied to clipboard
Protonmail-brigde fails to initialise : pass not initialized
App Name
protonmail-bridge
SCALE Version
22.02.0
App Version
1.8.10_5.0.1
Application Events
2022-03-25 19:06:20
Started container protonmail-bridge
2022-03-25 19:06:20
Created container protonmail-bridge
2022-03-25 19:06:15
Container image "tccr.io/truecharts/protonmail-bridge:v1.8.10-1@sha256:58a54002123cc9a83cfb3170deb0a1dbf4cedabdced09a9c6bcafc19ee4b5631" already present on machine
2022-03-25 19:06:14
Started container hostpatch
2022-03-25 19:06:13
Created container hostpatch
2022-03-25 19:06:09
Container image "ghcr.io/truecharts/alpine:v3.14.2@sha256:4095394abbae907e94b1f2fd2e2de6c4f201a5b9704573243ca8eb16db8cdb7c" already present on machine
2022-03-25 19:06:08
Started container autopermissions
2022-03-25 19:06:07
Created container autopermissions
2022-03-25 19:06:02
Container image "ghcr.io/truecharts/alpine:v3.14.2@sha256:4095394abbae907e94b1f2fd2e2de6c4f201a5b9704573243ca8eb16db8cdb7c" already present on machine
2022-03-25 19:06:02
Add eth0 [172.16.2.199/16] from ix-net
Successfully assigned ix-protonmail-bridge/protonmail-bridge-6f99779f8d-jvqq2 to ix-truenas
2022-03-25 19:05:56
Created pod: protonmail-bridge-6f99779f8d-jvqq2
2022-03-25 16:50:28
Scaled up replica set protonmail-bridge-6f99779f8d to 1
2022-03-25 19:05:49
Readiness probe failed: dial tcp 172.16.2.175:25: i/o timeout
2022-03-25 19:05:49
Liveness probe failed: dial tcp 172.16.2.175:25: i/o timeout
2022-03-25 19:05:31
Deleted pod: protonmail-bridge-6f99779f8d-h9khs
2022-03-25 19:05:32
Stopping container protonmail-bridge
2022-03-25 17:13:40
Scaled down replica set protonmail-bridge-6f99779f8d to 0
Application Logs
2022-03-25 18:06:20.493201+00:00+ [[ '' == init ]]
2022-03-25 18:06:20.494661+00:00+ socat TCP-LISTEN:25,fork TCP:127.0.0.1:1025
2022-03-25 18:06:20.495884+00:00+ rm -f faketty
2022-03-25 18:06:20.495904+00:00+ socat TCP-LISTEN:143,fork TCP:127.0.0.1:1143
2022-03-25 18:06:20.498608+00:00+ mkfifo faketty
2022-03-25 18:06:20.501253+00:00+ cat faketty
2022-03-25 18:06:20.501539+00:00+ protonmail-bridge --cli
2022-03-25 18:06:21.354322+00:00time="2022-03-25T18:06:21Z" level=warning msg="Failed to add test credentials to keychain" error="pass not initialized: exit status 1: Error: password store is empty. Try \"pass init\".\n" helper="*pass.Pass"
2022-03-25 18:06:21.377115+00:00[31mERRO[0m[Mar 25 18:06:21.377] Could not list credentials [31merror[0m="no keychain" [31mpkg[0m=credentials
2022-03-25 18:06:21.377194+00:00[31mERRO[0m[Mar 25 18:06:21.377] Could not load all users from credentials store [31merror[0m="no keychain" [31mpkg[0m=users
2022-03-25 18:06:21.381824+00:002022-03-25T18:06:21.381824001Z
2022-03-25 18:06:21.381864+00:00Welcome to ProtonMail Bridge interactive shell
2022-03-25 18:06:21.381881+00:00___....___
2022-03-25 18:06:21.381888+00:00^^ __..-:'':__:..:__:'':-..__
2022-03-25 18:06:21.381894+00:00_.-:__:.-:'': : : :'':-.:__:-._
2022-03-25 18:06:21.381900+00:00.':.-: : : : : : : : : :._:'.
2022-03-25 18:06:21.381911+00:00_ :.': : : : : : : : : : : :'.: _
2022-03-25 18:06:21.381921+00:00[ ]: : : : : : : : : : : : : :[ ]
2022-03-25 18:06:21.381927+00:00[ ]: : : : : : : : : : : : : :[ ]
2022-03-25 18:06:21.381933+00:00:::::::::[ ]:__:__:__:__:__:__:__:__:__:__:__:__:__:[ ]:::::::::::
2022-03-25 18:06:21.381944+00:00!!!!!!!!![ ]!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![ ]!!!!!!!!!!!
2022-03-25 18:06:21.381951+00:00^^^^^^^^^[ ]^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^[ ]^^^^^^^^^^^
2022-03-25 18:06:21.381957+00:00[ ] [ ]
2022-03-25 18:06:21.381963+00:00[ ] [ ]
2022-03-25 18:06:21.381973+00:00jgs [ ] [ ]
2022-03-25 18:06:21.381980+00:00~~^_~^~/ \~^-~^~ _~^-~_^~-^~_^~~-^~_~^~-~_~-^~_^/ \~^ ~~_ ^
2022-03-25 18:06:21.382716+00:00ProtonMail Bridge is not able to detect a supported password manager
2022-03-25 18:06:21.382757+00:00(pass, gnome-keyring). Please install and set up a supported password manager
2022-03-25 18:06:21.382766+00:00and restart the application.
Application Configuration
Describe the bug
The bridge doesn't come up. Logs show it fails to initialize.
When opening a shell in the container, and lauch the command "protonmail-bridge --cli" I get the following error : WARN[0000] Failed to add test credentials to keychain error="pass not initialized: exit status 1: Error: password store is empty. Try "pass init".\n" helper="*pass.Pass"
After using the command "pass init protonmail" to initialize de password manager, I get the following error : WARN[0000] Failed to add test credentials to keychain error="exit status 1: gpg: protonmail: skipped: No public key\ngpg: [stdin]: encryption failed: No public key\nPassword encryption aborted.\n" helper="*pass.Pass"
After initializing a gpg key (without password and all default settings), following this issue, I was able to make it work.
To Reproduce
- Install protonmail-bridge
- bug occur
Expected Behavior
Protonmail bridge should be up and accepting connexion.
Screenshots
Additional Context
None
I've read and agree with the following
- [X] I've checked all open and closed issues and my issue is not there.
btw, looks like you can only have one instance of the cli opened atm. So once the application is started, there is no way to login, etc.
I also have the same end log:
2022-05-06 19:33:45.489661+00:00ProtonMail Bridge is not able to detect a supported password manager
2022-05-06 19:33:45.489695+00:00(pass, gnome-keyring). Please install and set up a supported password manager
2022-05-06 19:33:45.489703+00:00and restart the application.
Still the same as of current version (1.8.10_6.0.3). Is there an official maintainer or should I take the matter into my own hands ?
Still the same as of current version (1.8.10_6.0.3). Is there an official maintainer or should I take the matter into my own hands ?
Of course it's the same, If it had been fixed, this issue would be also closed.
Even when there is a maintainer, PR's are welcomed, so you can work on this yea
btw, looks like you can only have one instance of the cli opened atm. So once the application is started, there is no way to login, etc.
Here is a temporary workaround until this is fixed.
- Open a shell into the pod
- Find the running bridge
-
ps -aux
- take note of the PID the command should look like "/usr/lib/protonmail/bridge/proton-bridge --cli --launcher /usr/lib/protonmail/bridge/proton-bridge-launcher"
-
- Kill it
-
kill -9 #
- replace # above with your PID
-
- Launch the CLI and login
-
protonmail-bridge --cli
-
login
-
- Stop and start the app
Still no fix ?
Still no fix ?
https://truecharts.org/docs/charts/stable/protonmail-bridge/installation_notes
We dont work for you guys, we are a community of volunteers.
this one specifically requires protonmail. Which almost none of the staff have.
+1’ing the issue is not helping your case. Either stfu and wait or fix it yourself.
This issue had been resolved due to a new pr that i made a week ago.
The installation notes explains exactly what commands to use to be able to login into proton the right way.
Just follow the guide and run the 2 commands exactly.
https://truecharts.org/docs/charts/stable/protonmail-bridge/installation_notes