rvice - Socat Bridge ProtonMail/Discourse.d -d will print the fatal, error, warning, and notice messages you may not want that much detail loggedĪnd automatically get it to start on boot:ĭone! Now, configure Discourse app.yml and rebuild: DISCOURSE_SMTP_ADDRESS: 172.17.0.1Īfter the initial sysctl commands systemctl status rvice We configured Socat to listen to all IPs 172.17.0.0/24, port 1026, and redirect the traffic to 127.0.0.1:1025, where Protonmail Bridge is listening

… and put the following content in it: ĭescription=Socat Bridge ProtonMail/DiscourseĪfter=rvice,rviceĮxecStart=socat -d -d -lm TCP4-LISTEN:1026,fork,reuseaddr,so-bindtodevice=docker0,range=172.17.0.0/24 TCP4:127.0.0.1:1025 Solution: We configure it to send to 172.17.0.1 (the Docker’s bridge IP on the host machine), and then redirect to 127.0.0.1, on which the Protonmail Bridge is listening. Problem: a) Protonmail Bridge cannot listen to IP other than 127.0.0.1, and b) Discourse in a Docker container cannot send SMTP requests to 127.0.0.1 of the host machine.

Bridge protonmail