Caddy based setup vs Traefikl
# install
c
Caddy based setup vs Traefikl
What's the difference between the traefik setup and caddy based setup? Are there some improvements worth the trouble of switching or should I stick with caddy?
j
Traefik will proxy MQ. This means 8883 no longer has to be exposed directly. Traefik also removes the port "80" requirement, so really, all you need is port 443, which is good for security.
Some corporate environments restrict reachable destination ports with their firewall, and will not let the clients reach 8883/tcp on a remote server
However, if you're not deploying for a corporate use case and dont care about minimizing ports, you can just stick with Caddy
c
Would it be possible to do that with Caddy as well? I have already set everything to be caddy based
b
only if someone writes a caddy module to proxy mqtt traffic. Such a caddy module does not exist as far as I am aware.
a
https://caddyserver.com/download select mholt/caddy-l4 should be possible but the standard config of caddy isn't working anymore
c
Ok, thanks. The security issues are not huge problems for me.
a
51821 and above is fine? Just a noob question 😅
j
yeah, because it's UDP, which is usually OK, but MQTT needs to be TCP, which is typically more restricted
a
and get a connection to mqtt with uft isn't possible?
*udp
b
No, mqtt is tcp
a
ok thanks for the explanation
2 Views