randommouse

randommouse · Oct 15, 2022

Finally got it, at least the TLSA issue. I followed this guide > Getting Started

My journey to make my own email server. . Contribute to chucklessducks/VPS-Wireguard-Nginx-Mailcow development by creating an account on GitHub.

but modified it with my own IPtables rules (posted

here

GitHub

Better IPtables · Issue #4 · chucklessducks/VPS-Wireguard-Nginx-Mailcow

When using mailcow on my local server I could not get it working 100% (TLSA, damn you!) with the iptables rules described in the instructions. The sudo iptables -P FORWARD DROP rule specifically wa...

) and moved the client endpoint to my OPNSense router.

randommouse · Oct 11, 2022

aaronsmith Those are the EXACT same instructions that I used when setting this up. The only difference being that my nginx reverse proxy was in its own docker container. The reverse proxy was working for the most part, there was just the inconsistent issue trying to log in at mail.domain.tld/SOGo. Upon submitting the username and password the green part of the UI turns orange and text “unhandled error” apears where it would normally say “Welcome Firstname Lastname”

randommouse · Oct 11, 2022

I’ve already tried this. I would not be posting here if i had not, I’m looking for community support as I cannot find the information the usual way (google). What i really don’t understand is why NPM will pull the letsencrypt certs with the only difference being the docker container.

randommouse · Oct 11, 2022

Still no luck. I think it might have something to do with routing through the wireguard tunnel and NAT not working as expected. It’s strange that everything else seems to be working as far as the web UI and emails are sending and receiving. I’m going to try changing the VPN client endpoint to my router (OPNSense) to see if I have any luck that way. Will come back to update if successful.

randommouse · Oct 10, 2022

Coniass I just abandoned using the reverse proxy. The error was inconsistent. I could change the proxy port and restart the containers and it would work for a while but then would stop working a few minutes after I logged in.

I should note that I’m using the non-production-ready builds because I want that sweet dark mode. Not sure if the issue exists in production ready builds.

randommouse · Oct 10, 2022

Had a similar issue. SOGO wouldn’t log in when behind reverse proxy and gave “unhandled error” on login page.

randommouse · Oct 10, 2022

After years of wanting to move my mail server to my local network I finally got the job done. By using a VPS and a wireguard tunnel to a VM running on my own network I was able to successfully forward all the required ports and now I’m able to send and receive emails from a server on my own network! My only issue is with SSL and TLSA. Mailcow won’t aquire certs from letsencrypt and won’t generate a TSLA key (1 1 1 connection refused). I set up Nginx Proxy Manager on the local host and was able to pull SSL certs with it and transfer them to mailcow. The persistent issue is the lack of TLSA. Anyone else have this issue and was able to solve it?