Thanks a lot man. I have tried many guides, created by many ppl. Yours the one was the most simplest, and yours the one I was able to run with no hassle. Good work man. Much obliged
Thanks for this video. The one thing which makes traefik so special and the best proxy for docker: The static config is simple and fits in a few lines. The dynamic part is truly dynamic. You can add, change and remove routings without restarting traefik. Even other docker stacks on the same machine need only a network and labels. Define web and websecure and you can add hostnames with certificates from different providers without restarting. Try this with any of the "webserver used as reversproxies" approaches. You should mention this in the intro or more often. Second thing: You should take a look at a docker-socket-proxy since you should not mount the socket inside your entry from the outside for security reasons. There is a simple proxy wich is used by some traefik powered projects.
Thanks for your input! :) And I'll take a look at the docker-socket-proxy. I am aware that it is not ideal, but I was not aware that there seems to be a neat solution to this :-)
Thanks for tuning in! I hope you enjoyed the Traefik tutorial. If you want to support me, demonstrating stuff in the clouds, you can try the digital ocean cloud with 200$ worth of credits if you use my link to sign up (for free of course!). link.techwithmarco.com/digitalOcean Thanks ------- 🔐If you want to improve your security stack even more, head over to my newest video about using a docker-socket-proxy instead of using it directly mounted from the host system! czcams.com/video/bOmnkJYv39M/video.html
Very good video ! Still I have a question, how does traefik know what port should it route the requests to. For instance, you never told it to especially route to port 8080 for the dashboard.
Hey @Saufolein, thanks for the comment! This works as this is a traefik specific feature or configuration which you have to follow according to the docs. Check it out here: doc.traefik.io/traefik/operations/dashboard/ In my example I activated '"--api.dashboard=true"' which means, traefik is exposing the dashboard. In order to view it via an url, you have to define a router attached to a specific service named 'api@internal' (this is how it just works according to the docs), and then you can map the router to a host rule, which in my case is 'traefik.example.com' We don't have to expose any port manually as traefik knows how to route the request to the api@internal service automatically. I hope this makes it a bit more clear to you :-)
Hi, thanks a lot for the tutorial. Iam thinking about switching from nginx proxy manager to traefik and your video helped me a lot to get it working. Is there a possibility to expose not only docker container but also other things on the network running on different devices using local ip and port of the service? NAS, Homeassistant, router...etc?
It is possible to export other services, have a look in the docs of traefik. doc.traefik.io/traefik/providers/overview/ You could use for example http, to expose another local network address
Very nice explaination, but there is one detail which is a bit annoying to hear: in the "Demo Time" Chapter when you type something in, it sounds on my headphones like you smack the microphone.
Thank you very much! and thanks for the hint, I was not aware of how this could be for people with headphones... I just thought its a bit like ASMR content smashing the keyboard :-D But I will more careful in the next videos :-)
Yes, you can for sure just play with it in your local network without exposing anything to the world. If you want to use let's say some subdomains like 'service.raspberrypi.local' you would need a local dns server to resolve those addresses in your network automatically. This can be done with PiHole for example. Then you could also benefit from using ssl certs on your local network. I haven't done it yet, but there are also some guides about that on the internet :)
@@techwithmarco If I have multiple services accessible from different ports on the same server, would pihole be able to handle this on its own or would I need Traefik to handle the addresses resolving to different ports?
You could use traefik for that, but you could also directly access the your services at their port. I am not completely sure about your setup, so my answers might not be accurate about your problem 😄
Sorry for the late response.. The subdomain already existed beforehand. You can see how I create them automatically with terraform and github actions. czcams.com/video/0BNwAEwYZlA/video.html There are also a bunch of other different ways to achieve the automatic creation. For example there is a docker container which works together with traefik which registers that traefik has a new subdomain configured and then creates the subdomain on your cloudflare account (github.com/tiredofit/docker-traefik-cloudflare-companion) Or you could also use some wildcard certificates, but for that you have to use dns-challenge.
Thanks a lot man. I have tried many guides, created by many ppl. Yours the one was the most simplest, and yours the one I was able to run with no hassle. Good work man. Much obliged
Glad to hear that :-)
fully agree!
Thanks for this video. The one thing which makes traefik so special and the best proxy for docker: The static config is simple and fits in a few lines. The dynamic part is truly dynamic. You can add, change and remove routings without restarting traefik. Even other docker stacks on the same machine need only a network and labels. Define web and websecure and you can add hostnames with certificates from different providers without restarting. Try this with any of the "webserver used as reversproxies" approaches. You should mention this in the intro or more often.
Second thing: You should take a look at a docker-socket-proxy since you should not mount the socket inside your entry from the outside for security reasons. There is a simple proxy wich is used by some traefik powered projects.
Thanks for your input! :)
And I'll take a look at the docker-socket-proxy. I am aware that it is not ideal, but I was not aware that there seems to be a neat solution to this :-)
Hey, I had a look at the docker-socket-proxy and made a short update video for that 🙂
czcams.com/video/bOmnkJYv39M/video.html
Create a playlist for Traefik please :D Good Job and Keep it up!
Thanks a lot! I definitely want to produce more Traefik content as I love it so much :-D
Just that you know, another Traefik video just went online 🙂
czcams.com/video/Z23BJrRMUM4/video.html
it's work! thank you from Indonesia
When presenting, enlarging type (your VS Code window) is not a bad thing. Lots of people consume media on a smaller screen nowadays.
Greate video . But i have problem how do i reserve proxy outside in docker
Can i also use traefik to expose not a container but instead a internal ip (a other vm) and put https externaly to it? :)
Great video. Thank you.
Thanks mate!
Thanks for tuning in! I hope you enjoyed the Traefik tutorial.
If you want to support me, demonstrating stuff in the clouds, you can try the digital ocean cloud with 200$ worth of credits if you use my link to sign up (for free of course!). link.techwithmarco.com/digitalOcean
Thanks
-------
🔐If you want to improve your security stack even more, head over to my newest video about using a docker-socket-proxy instead of using it directly mounted from the host system!
czcams.com/video/bOmnkJYv39M/video.html
Very good video ! Still I have a question, how does traefik know what port should it route the requests to. For instance, you never told it to especially route to port 8080 for the dashboard.
Hey @Saufolein, thanks for the comment!
This works as this is a traefik specific feature or configuration which you have to follow according to the docs. Check it out here: doc.traefik.io/traefik/operations/dashboard/
In my example I activated '"--api.dashboard=true"' which means, traefik is exposing the dashboard. In order to view it via an url, you have to define a router attached to a specific service named 'api@internal' (this is how it just works according to the docs), and then you can map the router to a host rule, which in my case is 'traefik.example.com'
We don't have to expose any port manually as traefik knows how to route the request to the api@internal service automatically.
I hope this makes it a bit more clear to you :-)
Hi, thanks a lot for the tutorial. Iam thinking about switching from nginx proxy manager to traefik and your video helped me a lot to get it working. Is there a possibility to expose not only docker container but also other things on the network running on different devices using local ip and port of the service? NAS, Homeassistant, router...etc?
It is possible to export other services, have a look in the docs of traefik. doc.traefik.io/traefik/providers/overview/
You could use for example http, to expose another local network address
Very nice explaination, but there is one detail which is a bit annoying to hear: in the "Demo Time" Chapter when you type something in, it sounds on my headphones like you smack the microphone.
Thank you very much!
and thanks for the hint, I was not aware of how this could be for people with headphones... I just thought its a bit like ASMR content smashing the keyboard :-D But I will more careful in the next videos :-)
@@techwithmarco Thank you 🙏
Is there a more simple approach if I only want the reverse proxy in my local network? I don't want to expose anything to the internet.
Yes, you can for sure just play with it in your local network without exposing anything to the world.
If you want to use let's say some subdomains like 'service.raspberrypi.local' you would need a local dns server to resolve those addresses in your network automatically. This can be done with PiHole for example. Then you could also benefit from using ssl certs on your local network.
I haven't done it yet, but there are also some guides about that on the internet :)
@@techwithmarco If I have multiple services accessible from different ports on the same server, would pihole be able to handle this on its own or would I need Traefik to handle the addresses resolving to different ports?
You could use traefik for that, but you could also directly access the your services at their port. I am not completely sure about your setup, so my answers might not be accurate about your problem 😄
Did the plausible subdomain already exist beforehand or is there something for treaefik to create it automatically ?
Sorry for the late response.. The subdomain already existed beforehand. You can see how I create them automatically with terraform and github actions. czcams.com/video/0BNwAEwYZlA/video.html
There are also a bunch of other different ways to achieve the automatic creation. For example there is a docker container which works together with traefik which registers that traefik has a new subdomain configured and then creates the subdomain on your cloudflare account (github.com/tiredofit/docker-traefik-cloudflare-companion)
Or you could also use some wildcard certificates, but for that you have to use dns-challenge.