Host a webserver on your router using CONTAINERS!

Рет қаралды 26,939

Жыл бұрын

Like most MikroTik devices, L009 is more than just a router. Containers enable a variety of new usecases. You can even host a simple webpage on your router. Here's how!

Пікірлер: 68

@IamKhoramdin 7 ай бұрын

You have no idea that how much you changed my IT life with container in Mikrotik. Thank you very much

@zadekeys8304 4 ай бұрын

Agreed. I Have an AC2, AC3 and recently I got a AX3. Going to setup Uptime Kuma , Pi.Alert & AdGuard on it. Uptime Kuma has a nice simple interface, while Pi.Alert gives more info than most will need or know what to do with. I have some older RB951 and 952 units around that I'm repurposing as WiFi Pineapple's.

@freddyalvarez485 Жыл бұрын

Awesome, please second part with the domain part and securing, thanks guys great video!

@rsatopwebdesouza5215 Жыл бұрын

Thanks so much for explaining more about this new container feature :)

@chadtaylor1148 Жыл бұрын

I think going thru the process of securing a domain name and setting up CF with a ZeroTrust tunnel would be a great video even if you dont have a little website running on the router. The added benefit of this would be CF taking the brunt of a DDoS attack. At minimum you could just show that using CF with Proxy on would help tremendously then you can set the port forward to only allow traffic from CF and they will proxy the connection to your router.

@chadtaylor1148 Жыл бұрын

Also keep in mind that CF is the least expensive domain registrar out there they have a zero markup stance on domain names. Plus its automatically setup for use with their DNS.

@qsergii 9 ай бұрын

As always - great job! Nice instruction and it works! Thank you! Don't stop in future!

@mikrotik 9 ай бұрын

Glad it helped!

@louislectric Жыл бұрын

Since the first three videos of the container subject I was wondering when you would come up with additional container applications. Good work

@rogeriodesouza8066 Жыл бұрын

Congratulations on the excellent tips about containers! I would like tips on how to install a DLNA or miniDlna server container. Thanks!

@drumaddict89 Жыл бұрын

yes please go into more detail in setting this up with cloudflare! 🤞💪

@randomxspots Жыл бұрын

Very useful. Moving my local Web server from raspberry pi to CCR. thank you mikrotik.

@jameshoggtech Жыл бұрын

Cool, yes please do a video about cloudflare tunnels!

@JocPlus Жыл бұрын

nice, please second part :)

@DmMukhin Жыл бұрын

Nice. Please second part!!!

@Kredo800 Жыл бұрын

Very expected episode. Eager to get at least one. Not available at local shops in Ukraine... Very useful will be to have tls easy install without cloudflare, this will be killing feature for the market. I think pre-maid container capable of tls would be great, pre-made container able to work with letsencrypt certificate update would be brilliant. Too many clients just need simple one page landing with primitive php scripting for feedback form & I believe many have static ip for cams.

@gabrielporto.mikrotik Жыл бұрын

As a MTCRE guy and Cloudfare user, I think you should definitely buy a domain to make another videos.

@stephanszarafinski9001 Жыл бұрын

To solve the https issue, you could make a container with nginx and letsencrypt inside it.

@kyleheppler2860 Жыл бұрын

Do the domain! Fun tips!

@maizfeIiz Жыл бұрын

please do a tutorial for docker in docker in mikrotik, for example to configure a outline server inside mikrotik, that would be the deffinitive vpn server, almost all vpn protocols...

@mikrotikmali Жыл бұрын

Thanks 😊

@alexisassi Жыл бұрын

Nice 👍

@andrii.dergilev Жыл бұрын

Please do that video on how to secure the Cloudflare tunnel with MicroTik.

@ABUNDANCEandBEYONDATHLETE Жыл бұрын

I'll purchase one and maybe record a video using Cloudflare connection to our container website.

@nikolashuminosky6987 8 ай бұрын

also , how can i use nginx, if i want to run two website, do i need to instal separate container?

@GustavoGustik 2 ай бұрын

Yeah I want to setup a website through Cloudflare. I am also interested in video how to install certificate directly on router and make https working natively in container.

@MiniArts159 Жыл бұрын

Another Interesting topic could be using the built-in automatic Let's Encrypt features built into RouterOS to secure containers.

@dimitris470 11 ай бұрын

You can run Caddy or nginxproxymanager as a reverse proxy in front of your containers

@D9ID9I Жыл бұрын

how about docker-compose support?

@trexx_media Жыл бұрын

Awwwwwwesome 🎉🎉🎉🎉

@hordynaelmf 5 ай бұрын

Can I do more with a Router OS installed on a X86 PC, with lots of resorces? I'm thinking in use my PC to install RouterOS and from IT run NextCloud and a NVR System.

@mikrotik 5 ай бұрын

For sure, with x86 you can run way more demanding docker setups. Sounds like a fun project.

@jpsemnetworkers 2 ай бұрын

Yes

@mahyudimdyusof1865 Жыл бұрын

yes

@DiscotequeVIP Жыл бұрын

I followed your tutorial, and at end got "403 Forbidden nginx/1.25.1" when try to load some file. I placed index.html file into html folder, but same error occured. Any help how to fix this?

@user-wy2ys7eo8j Жыл бұрын

多更新视频，对我帮助很大

Жыл бұрын

If self hosting is important I'd avoid Cloudflare and use a VPS with a webserver acting as a reverse proxy (apache or nginx + certbot for letsencrypt) and connect to the container via a VPN connection between the VPS and the router, that way no public IP is needed. If everything has to happen in the router, I'd use a container that has certbot + a webserver to handle TLS, for dynamic IPs I'd add CNAME record to the dynamic DNS provided by Mikrotik's cloud function.

@tvojejbabkydedko Жыл бұрын

at that point you can just host it already on a VPS because you are making additional single points of failure

Жыл бұрын

@@tvojejbabkydedko sure, I would do that too, but if the customers at the local premises are the ones that need to view the menu having the site in the router will make the site available even if local internet connection is not available

@D9ID9I Жыл бұрын

Containers add versatility. But they require hardware with enough ram, compute power and storage. And L009 does not really fit.

@nikolashuminosky6987 10 ай бұрын

need episode 2

@genesishep Жыл бұрын

I'm another vote for setting up Let's Encrypt no need to pay for SSL when you can get it for free.

@ivancristianledezmasoria3461 Жыл бұрын

winbox dark mode!!!

@kubicajakub Жыл бұрын

Sony phone?

@nikolashuminosky6987 Жыл бұрын

nokia 3310

@cldpt Жыл бұрын

amazin video! Quick English tip: do not pronounce allow as "ah! Low", it is pronounced more like "a-Lou(d)". The (d) is not pronounced, just putting it there to say the sound is similar to the word "loud"

@Anavllama Жыл бұрын

No kidding Chad, that is why I keep recommending to MT that they include ZeroTrust cloudflare tunnel as either an options package on ALL devices or part of RoS like Wireguard. The ability to create safer servers for all users is a NO BRAINER!! Not sure why MT is brain-dead on this topic??

@homayounshokri5041 Жыл бұрын

Router os security sucks Instead of adding new features work on the security and stability for it

@PopovGP 11 ай бұрын

Ставлю ALT Linux: /container add remote-image=alt:latest root-dir=my_ram_disk1/alt interface=veth01 cmd="tail -f /dev/null" всё ок: start 0 0 name="8c54660f-466c-4860-9357-128db24177fe" tag="library/alt:latest" os="linux" arch="arm64" interface=veth01 cmd="tail -f /dev/null" root-dir=my_ram_disk1/alt mounts="" dns="" status=running shell 0 не запускается: execve: No such file or directory done RouterOS: 7.10.2 Stable, Microtik hAP ax² Это ошибка в образе или команда shell вызывает что-то определенное, работающее не для всех образов?

@Antoxic90 Жыл бұрын

I wish you could fix the docker feature as it is still not working with docker registry. The docker feature just breaks down in every new release. It would be nice if you talk about new features when they are stable.

@louislectric Жыл бұрын

Perhaps investigate the existence of the main route! Docker has been working flawlessly for me. Also, are you using stable or dev releases?

@Antoxic90 Жыл бұрын

@@louislectric it’s not the routing. It’s a problem of mikrotik pulling the image from docker registry. There is a post on the forum about this issue. This happens on the latest stable release.

@louislectric Жыл бұрын

@@Antoxic90 Spreading false news that an entire feature is broken just because the Adguard (advertising blocking) application didnt work out for you is unsolicitely going to make you famous. Consider rephrasing your initial comment.

@miankamran802 Жыл бұрын

Hey, MikroTik Hope, you will be fine. It is for your information. Your video for Hosting the webserver on Mikrotik Container is useless to me. And I think it is also useless for everyone who is trying to host a web server by getting a guideline from this video. At least you should keep in mind while you making a video you are doing it for branding your product or teaching your users for the deployment. I'm now in my office and spent 4 hours on this configuration but unfortunately no result. I waste my 4 hours. "no nginx shows in files etc many problems". I request to you make this video again even beginners can able to understand your way of teaching. And they no more need to go for another platform. May you should need to configure it with GUI, not in the terminal. Please do needful as soon as possible. I will be waiting for a positive response from you. Thanks

@RB01-lite Жыл бұрын

When adding a container set the logging=yes parameter to know exactly why your container fails. If you are beginner it is better you follow the older videos to learn the basics.

@miankamran802 Жыл бұрын

@@RB01-lite it not enough and no answer of my question. and for your information, I'm a Mikrotik user since 2013.

@KonstantinovAG Жыл бұрын

Sorry .... but .. what? port 80 to port 80? really?

@blu4able360 Жыл бұрын

It's a local network test, when you use certbot it will automatically make it use port 443.

@vioreld5203 Жыл бұрын

yeah, port 80 from "localhost" to port 80 in the container

@cldpt Жыл бұрын

means you're mapping requests made to the router on port 80 to be forwarded to port 80 on the container. Since the container is essentially another "OS/Computer" running inside the host Router (which is also a computer), one needs to instruct the host system's physical requests made by other computers on the network to use the container "computer" instead. You could also not use this port or even the same ports.

@KonstantinovAG Жыл бұрын

@@vioreld5203 it's no reason, when you doing dstnat - you change addrewss from address of router to address of container. and change in this rule - port 80 to port 80. Why? It's no need if port not changed

@gabrielporto.mikrotik Жыл бұрын

@@KonstantinovAG You ain’t right my friend. There is source and destination. Both should have ports. Even if it’s the same. Otherwise, how would the router know what port to forward to the destination IP?