☁️ The Most Secure and Easy Selfhosted Home Server. Take control of your data and privacy without sacrificing security and stability (Authentication, anti-DDOS, anti-bot)
I installed Docker-Mailserver, and as part of the installation a corresponding URL was created, proxying for http:/Docker-Mailserver:80. Attempting to access https://mymailserver.example.com resulted in 502 Bad Gateway.
What should have happened?
So I started troubleshooting why the url was not working, until I came to the conclusion that this particular server app should not have such a proxy url since it only talks mail related protocols. E.g. upstream compose file:
What happened?
I installed Docker-Mailserver, and as part of the installation a corresponding URL was created, proxying for
http:/Docker-Mailserver:80
. Attempting to accesshttps://mymailserver.example.com
resulted in 502 Bad Gateway.What should have happened?
So I started troubleshooting why the url was not working, until I came to the conclusion that this particular server app should not have such a proxy url since it only talks mail related protocols. E.g. upstream compose file:
and the cosmos servapp configuration also lists the exact same ports.
How to reproduce the bug?
Docker-Mailserver
Relevant log output
No response
Other details
Apparently Postfix Admin is a nice web frontend for dovecot, but probably cosmos should not add one until upstream does.
System details
Cosmos version 0.9.19