Cryout - please add a warning to the docs

I don’t use hassio so I don’t know how the add-ons are configured. I manage my own Traefik on another server separate from my home assistant host. It’s actually in a completely different state. Lol.

I rely on IIS so Nginx is out of the question no? But I am guessing I could do the same with IIS right? I can’t get rid of IIS because I have a windows environment with Active Directory and I am pretty sure that core functionality of this relies on IIS. Has anyone tried it with IIS by any means?

Active Directory doesn’t rely on IIS at all.

Srry you are right, I use server essentials which does rely on IIS if I want to use it’s features like anywhere access. But I am guessing I could do the same with IIS as with Nginx?

I checked out both Caddy and Traefik and then looked at benchmarks, and it looks like Nginx is way ahead of them in performance. That combined with the fact that I’m familiar with nginx and SSL is trivial with certbot --nginx command, I decided to just stick with nginx.

@flamingm0e So I slept on it and now have another question. You said that it’s better to give VMs their own IPs within network. But in my case I am going to use this same PC for file storage. So I don’t think it’s logical to send all traffig through 1Gbit connection to the router, it will cripple performance not only within this machine but also of the whole LAN.

Is there any way to get the best of both worlds? Have LAN IPs for each VM but also allowing direct access to data share?

Your traffic should never go to the router running VM to VM. This has nothing to do with getting it’s own IP address.

There is absolutely a way to do this. It’s a little more advanced setup, but not hard. It’s simple to configure the host. Create a new vmbr (it’s essentially a virtual switch) and don’t connect the vmbr to physical adapters. Boom, you have a VM-only LAN.

And for that I need to create a new vmbr, right? Cool, thanks. If my physical LAN uses subnet 255.255.255.0 and IPs of 192.168.1.X - what should\could I use for this new vmbr?

I should read more about how it works of course

Yes, create a new vmbr with NO physical NIC attached.

You don’t give the vmbr ANY IP address or subnet. Just IP the VMs in the vmbr with whatever subnet you want to use that’s different from your normal subnet. It doesn’t have to be routable.

Like this? https://i.imgur.com/pAA0pfi.png

I assume the IP address there is the one that can be used by VMs to connect to the host if needed? Or not?

No, don’t give the VMBR an address at all. The VMBR doesn’t need an IP. The settings on the VMBR have no bearing on the VMs attached to it. Remove the IP address.

Think of the VMBR as a dumb switch. That’s it. It doesn’t get an IP address and doesn’t need to be accessible from your LAN.

Removed, but it still does not allow me to give any IP outside the 192.168.X.X range.

No, you aren’t understanding.

DO NOT GIVE ANY IP ADDRESS TO THE VMBR AT ALL.

DO NOT PUT ANYTHING IN THE IP SETTINGS.

No need to shout on me, I did not put anything in VMBR:

The screenshot above is not VMBR’s settings, it’s VM’s settings:

If I dont need to put anything in VM’s network settings, where do I set it’s IP?

So that worked, do I set the IP inside the VM’s system then?

That is a CONTAINER, not a VM.

I know, does it make a difference in this case? I still need both CTs and VMs to have this kind of network configuration

It does make a difference.

You usually configure the container from the GUI.

You configure a VM from inside the VM.

You can also configure the container from within the container. That will be a manual config inside.

I see. So in case with the container then, how do I give it IP address on vmbr1?

EDIT:

Ah, 10.10.0.1/24 worked. Forgot CIDR.

should be able to edit /etc/network/interfaces inside the container (assuming it’s a debian/ubuntu base)

Why can’t I give container IP address like this?