0

I´m using Debian 9.
PROBLEM: I can only reach my subdomain by appending a specific port
Summary: I´m running two docker containers (laradock and mailcow). Both of them have their own instance of a web server (laradock: caddy, mailcow: nginx). Since I´m prioritizing my laradock container, it is the one blocking/using ports 80 and 443 (on localhost) for incoming http(s) traffic. My other container with nginx (mailcow) is listening to ports 8089 (http) and 8090 (https) on 0.0.0.0. I want to re-route all requests to webmail.mydomain.com, probably using caddy as a reverse-proxy in this case, to the ports utilized by mailcow. My attempts configuring a reverse-proxy with the not-so-well-known-caddy have failed with 502 gateway errors until now (and I can´t use nginx for my laradock container). Can anybody provide a solution to my problem? This doesn´t have to include port forwarding/reverse proxies.

Improve this question
2
  • In your config you have https://abc.example.com --> http://abc.example.com:8090 but then you say https://abc.example.com:8090 directly is one of those a typo.
    – Drifter104
    Jan 29, 2019 at 16:40
  • @Drifter104 sry typo
    – 3x071c
    Jan 29, 2019 at 17:00

1 Answer 1

Reset to default
-1

I solved the problem by using nginx on my main system as a reverse proxy for both caddy and mailcow.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .