Trouble signing in.

[tazire]

I keep getting login incorrect. Im just curious does this version have trouble with special characters? ive double checked the pw and that with the bridge on my main rig etc and it works fine. Just FYI im running this in unraid. cheers

Just to add to this my protonmail authentication logs shows no login failed.

[shenxn]

Which version are you using? Special characters should be fine.

[tazire]

I dont know if you have ever used unraid but there is a version on the community applications. I believe it is taken directly from your docker hub post.

Just having a thought about this.. should i create port forwarding rules for this? since i dont actually get a failed authentication log on my protonmail account it kind of seems like the bridge login might not even be connecting to the authentication servers???

[shenxn]

Try the check internet command inside the protonmail bridge cli. If there is a connection problem, #3 might be helpful.

[tazire]

Yea that definitely seems to be the problem. This is where I am a little limited as using unraid is very different to standard cli. check internet just came back with a not found. I get the same result with other containers also. I can however ping out of other containers and it works fine. Not so with this container. And your suggestion of using the --dns operation when starting up. Im not sure where to include this. Again if you are not familiar with Unraid its kind of hard to explain. I tried to use it in the extra parameters and post arguments... which seem to be used for adding launch parameters... what is the full command to include --dns. I will bring my issue to the unraid forums to try get this working.

[tazire]

Just FYI as a total beginner I was being stupid and assuming that opening the container console was bringing me into the cli.... ofc i needed to use the command "protonmail-bridge --cli" before trying to login. As I had missed this I wasnt being prompted for the 2FA code and was getting a login failed every time. Completely my own lack of knowledge with this. but if this helps anyone else its worth having here. Thanks for the help.

[hecmen]

I'm stuck in the same screen using unraid with the protonmail-bridge from the community applications. I tried the "protonmail-bridge --cli" in the console of the container, but nothing happens. In the "console shell command," are you using bash or shell?

Also the community applications says to use bash with this command "bash docker exec -it protonmail-bridge /bin/bashchmod +x entrypoint.sh/entrypoint.sh init"; however, it tells me "no such file or directory". Any thoughts?

[tazire]

@hekitoo this is a bit finicky on unraid but here's what I did to get it up and running. First of all this all has to be done on the first install of the docker. I only ever seem to be able to access the cli one time and then I never get access again. So delete the app data and container and start from scratch.
When I first install and put in "protonmail-bridge - - cli" i always got the output that the bridge wasn't running. I had to enter the following commands to get the bridge up and running..

gpg --generate-key --batch /protonmail/gpgparams

pass init pass-key

That got the bridge running. Then protonmail-bridge - - cli will work. However this will only work this one time. So I had to login and set the bridge up in seperate inbox mode and copy the settings to a txt file incase I ever need them later. Once I exit cli mode I have never been able to access it again. But the docker has been running as it should and I can connect to it no problem using the detail. Hope this helps. There may be means to get back into the cli but I haven't found it. After this first launch the cli command will only inform me that the bridge is running but will not actually give me access to input cli commands. I have no means to make any changes to any settings other than a fresh install. This hasn't been an issue for me however ymmv

Credit to @ragregory42 for this addition. This has solved my issue of being able to access the cli after the initial install. Unfortunately beyond this I dont really know what else to try.

I have the same issue as above. "Protonmail-bridge --cli" results in no further output in the terminal once run in an unraid docker container.

--SOLVED--

I ran a 'top' and killed the duplicate "proton-bridge" process which was PID 26 for me. Then re-ran "protonmail-bridge --cli" and was able to continue with login.

[hecmen]

Hey @tazire, thanks for the detailed instructions. Unfortunately, nothing happens after I use the "protonmail-bridge --cli". I also tried your commands, which worked fine, but it will not open the cli for protonmail.

I've probably spent way too much time on this already. It's a shame that protonmail won't officially support docker for it.

Once again, thanks for the help!

[ragregory42]

I have the same issue as above. "Protonmail-bridge --cli" results in no further output in the terminal once run in an unraid docker container.

--SOLVED--

I ran a 'top' and killed the duplicate "proton-bridge" process which was PID 26 for me. Then re-ran "protonmail-bridge --cli" and was able to continue with login.

[TrevorSLong]

--SOLVED--

I ran a 'top' and killed the duplicate "proton-bridge" process which was PID 26 for me. Then re-ran "protonmail-bridge --cli" and was able to continue with login.

This worked for me, thank you!

[ghzgod]

I have the same issue as above. "Protonmail-bridge --cli" results in no further output in the terminal once run in an unraid docker container.

--SOLVED--

I ran a 'top' and killed the duplicate "proton-bridge" process which was PID 26 for me. Then re-ran "protonmail-bridge --cli" and was able to continue with login.

Thank you! I hope you have a great day and I hope you have a beautiful family some day (if not already).

[nandonov]

I have the same issue as above. "Protonmail-bridge --cli" results in no further output in the terminal once run in an unraid docker container.

--SOLVED--

I ran a 'top' and killed the duplicate "proton-bridge" process which was PID 26 for me. Then re-ran "protonmail-bridge --cli" and was able to continue with login.

That worked also for me, thanks!

[BrandonMcInroy]

I've been trying to get this running on my unraid server using the various solutions here, but no matter what I do, it just won't work at all. When I use the top command, there are no proton process running at all so I can't try to kill the duplicate process. Any ideas?

[christycenturion]

at the risk of sounding incredibly ignorant here, the login that is required, is this the protonmail account you are creating the bridge for OR a user on the server hosting the bridge? (for instance i'm setting up on an unraid server and login command prompts '-servername- login'

---

it's the smtp credentials* I was seeing the wrong login screen because I hadn't ran the top command to kill the proton-bridge process: this worked for me>> https://www.hagensieker.com/wordpress/2021/11/18/protonmail-bridge-on-unraid/