WARN[0000] Failed to add test credentials to keychain error="failed to open dbus connection: exec: \"dbus-launch\": executable file not found in $PATH" helper="*keychain.SecretServiceDBusHelper"

[collateral127]

trying to connect to the console and pull any information at all gives me this error

the bridge still seems to work just fine in terms of sending emails, but i'm a little concerned i can no longer access the config

[Redryan243]

I am getting this error as well, this is my first time setting up protonmail-bridge and am unable to proceed last this point. Have you found any workaround?

[collateral127]

No clue sorry :(

I'm at the "it works so I'm not touching the pyramid of cards" stage

[ifrido]

@collateral127 I

trying to connect to the console and pull any information at all gives me this error

the bridge still seems to work just fine in terms of sending emails, but i'm a little concerned i can no longer access the config

@Redryan243 I had the same problem.. The problem seems to be that you can't launch the console when the bridge is running in the background.

In my case I was able to solve this by stopping the protonmail bridge, then use the console to do the needed configuration and start the bridge afterwards.

[collateral127]

thanks @ifrido

i'll give that a crack and report back

[MrToast72]

@collateral127 I

trying to connect to the console and pull any information at all gives me this error the bridge still seems to work just fine in terms of sending emails, but i'm a little concerned i can no longer access the config

@Redryan243 I had the same problem.. The problem seems to be that you can't launch the console when the bridge is running in the background.

In my case I was able to solve this by stopping the protonmail bridge, then use the console to do the needed configuration and start the bridge afterwards.

How did you manage to stop just the bridge and complete the configuration?

[RichardJActon]

I've been having the same issue. I found the protonmail-bridge process with top and killed it then I was able to start the interactive mode with protonmail-bridge --cli and login.

[Philip-Mooney]

I've been having the same issue. I found the protonmail-bridge process with top and killed it then I was able to start the interactive mode with protonmail-bridge --cli and login.

This worked for me, but it required killing protonmail-bridge and proton-bridge

[AviationAce]

I am also stuck here. Has anyone found a solution to this yet?

[aarek-eng]

Same here, stuck in the same way. protonmail-bridge doesn't even appear among the top apps.

[MrHash]

you may be able to view config by running something like this docker run --rm -it -v protonmail-data:/root --entrypoint="" shenxn/protonmail-bridge:3.8.1-build /protonmail/proton-bridge --cli