Search results

Are enp5s0 and epn6so both connected? If they are both connected to a switch, and you have STP turned off, you could have a bridge loop.

Or it could just be that wifi doesn't work with bridging so when it fails over it stops working.

Are you sure that nothing else on your network is using 192.168.1.223? That would be in the default DHCP range of a lot of routers.

Most routers do DNS proxy/forwarding out of the box. They will typically forward to the one your ISP assigns via DHCP. That is likely why it works when you point PVE to your router for DNS. I don't know what the "helper scripts" do, I have never used them. They aren't officially sanctioned...

Try "ifup vmbr0".

He also seems to be lacking a bridge. The output of "cat /etc/network/interfaces" might be useful.

This is not correct. You apparently don't understand what the /24 does. It specifies the division between the network and host parts of the address. IP routing is based on prefixes, where the prefix represents the network and the rest represents the particular host on that network. The /24...

Why do you think backing up and restoring would not work? Did you try it? It isn't clear from your post what you have done.

Did you install "build-essential" or "dpkg-dev"?

Since you are using qcow2 I suppose you formatted the RAID as a file storage. If you used Ext4, by default it has a maximum file size of 16 TB. This is one reason to use lvm-thin instead of a filesystem.

A lot of ISP's, probably most of the big ones, block outgoing port 25. Instead you have to use 587 or 465 (mail submission) and supply appropriate credentials.

That is correct. They seem to not be used.

https://linuxconfig.org/introduction-to-lvm-thin-provisioning Here is a tutorial about lvm-thin. You can skip the part about creating the lvm-thin and just go to "creating thin volumes". You have to create the volume, format it, and then mount it. Substitute the name of your volume in the examples.

Ths simplest thing would be to create a volume on lvm-thin and mount it to /shared.

The SSH error is easily fixed by following the instructions in the error message. All it means is that the host key has changed, perhaps due to reinstalling PVE. ETA: Another thing that could cause that error, besides re-installing PVE, is an IP address conflict. That could also cause the issue...

Did you use https and port 8006? https://<your-pve-ip>:8006

It also allows people to endlessly opine on how Proxmox runs their business.

File servers tend to use all of the RAM as cache. Is there an actual problem or you just don't like all the memory being in use? ETA: Operating systems in general tend to use all of the RAM as cache. File servers just get there quicker.

Having two IP's from the same subnet on two different bridges won't do what most people think it does. What will happen is that the kernel will feel free to reply to incoming request on whichever bridge it thinks appropriate. It will _not_ load-balance. EDIT: There are circumstances where it...

I don't know about that but I am running a single node with key-only ssh logins and it is fine. I'm pretty sure the cluster SW uses keys as well, not passwords.