Would you like to use LXD clustering? (yes/no) [default=no]:
Do you want to configure a new storage pool? (yes/no) [default=yes]: no
Would you like to connect to a MAAS server? (yes/no) [default=no]:
Would you like to create a new local network bridge? (yes/no) [default=yes]: no
Would you like to configure LXD to use an existing bridge or host interface? (yes/no) [default=no]: yes
Name of the existing bridge or host interface: lxdbr0
Would you like the LXD server to be available over the network? (yes/no) [default=no]:
Would you like stale cached images to be updated automatically? (yes/no) [default=yes]:
Would you like a YAML "lxd init" preseed to be printed? (yes/no) [default=no]:
Error: Failed to update profile "default": Device validation failed for "eth0": Cannot use "nictype" property in conjunction with "network" property
I tried lxc network create lxdbr0 Error: The network already exists
lxc list still shows all of my containers are still there but my main site will no-longer load ERR_SSL_PROTOCOL_ERROR just because csf destroyed lxd_nic_lxdbr0
I’m guessing lxc init with the default networking suggestions should have made some iptables rules with /* generated for LXD network lxdbr0 */ based on what I’ve seen in other peoples questions.
my iptables:
iptables -L -n -v
Chain INPUT (policy ACCEPT 1664K packets, 141M bytes)
pkts bytes target prot opt in out source destination
Chain FORWARD (policy ACCEPT 19677 packets, 5501K bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 1612K packets, 214M bytes)
pkts bytes target prot opt in out source destination
(^ looks blank?)
It there a way to trigger it to reload the default rules for LXD?
systemctl restart snap.lxd.daemon and snap restart lxd makes no change