Does anyone have a guide to Traefik for an absolute idiot (myself)?
I was able to get a freshrss server running using dockercompose and was able to connect to it on my local network, but all the guides I read said I NEED to have a reverse proxy before I access it remotely.
This is probably my sign I need to actually learn how to use docker instead of being lazy as hell and copy/pasting code, but I thought I’d ask.
Or you could consider using Caddy instead: https://caddyserver.com/docs/quick-starts/reverse-proxy
+1 for caddy. I had some issues with traefik and switched to caddy and it’s so easy!
Just need to learn the more advanced stuff for the Caddyfile like error redirects and what not.
@fraydabson @krdo been curious about caddy before but I have no reason to switch from nginx-proxy-manager. Has anyone got any experience with both of these ? How do they compare?
Im new with reverse proxies. My understanding is that npm is way easier to do stuff with the UI and you use it to setup the certs and all that.
With caddy it has auto https. So you just need one Caddyfile listing your reverse proxies and that’s it. It just works. No config or anything.
Now if you want to do more advanced stuff like what you would do with nginx conf files, caddy is very expansive with its directives. Setting up redirects or error pages and what not. It’s super simple in the Caddyfile. I’m still learning how to do more complex stuff like if else statements and what not.
@fraydabson Thanks for the explainer. I was recently tempted to try it out but my certs end everything is managed by NPM and didn’t really have the time to redo my whole setup but it looms interesting
@krdo I have found Caddy much easier to use than Traefik
Consider Caddy … just uninstalled Traefik in favor of Caddy
Caddy is the only reverse proxy I managed to setup. I failed miserably multiple times with Traefik and Nginx.
Techno Tim did a good video on traefik
Here is an alternative Piped link(s): https://piped.video/watch?v=liV3c9m_OX8
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source, check me out at GitHub.
As stated before you don’t need a reverse proxy. Since you are exposing port 8080 ( if you stuck the config on the docker hub page; “-p 8080:80”) it is reachable from everywhere, where you have access to that machine.
A reverse proxy can expose many different services running either on the same machine or from a remote. As long as the reverse proxy is in the same docker network (usually “default”) it can access your services without their ports exposed.
You can configure the reverse proxy to decide which backend service to call by path, dns name or other patterns.
A reverse proxy can also do TLS termination and get certificates from let’s encrypt, so the backend services don’t have to deal with it.
So if you run more than one service on the same machine and want to use TLS you normally want to use a reverse proxy.
I personally use traefik because I used to but I also used nginx and caddy. Whatever works for you. But I agree that caddy is easier to get going without a lot of boilerplate config.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters DNS Domain Name Service/System HTTP Hypertext Transfer Protocol, the Web IP Internet Protocol SSL Secure Sockets Layer, for transparent encryption TLS Transport Layer Security, supersedes SSL VPN Virtual Private Network nginx Popular HTTP server
5 acronyms in this thread; the most compressed thread commented on today has 4 acronyms.
[Thread #43 for this sub, first seen 14th Aug 2023, 17:05] [FAQ] [Full list] [Contact] [Source code]
