You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The README file say to run docker run -d --name=protonmail-bridge -v protonmail:/root -p 1025:25/tcp -p 1143:143/tcp --restart=unless-stopped shenxn/protonmail-bridge
but this causes the wrong port to be exposed for the contain. Since 1025 and 1143 are mapped to 25 and 143 with socat so the README commands should be
docker run -d --name=protonmail-bridge -v protonmail:/root -p 25:25/tcp -p 143:143/tcp --restart=unless-stopped shenxn/protonmail-bridge
The text was updated successfully, but these errors were encountered:
I would note that there is a difference here on port selection. If I map to port 25 on the container (instead of the configured 1025), I am able to connect. Not so if I map 1025:1025. I'm guessing socat is fooling protonmail-bridge into accepting the connection from an "outside" machine.
The README file say to run docker run -d --name=protonmail-bridge -v protonmail:/root -p 1025:25/tcp -p 1143:143/tcp --restart=unless-stopped shenxn/protonmail-bridge
but this causes the wrong port to be exposed for the contain. Since 1025 and 1143 are mapped to 25 and 143 with socat so the README commands should be
docker run -d --name=protonmail-bridge -v protonmail:/root -p 25:25/tcp -p 143:143/tcp --restart=unless-stopped shenxn/protonmail-bridge
The text was updated successfully, but these errors were encountered: