Search results

That is what I have now. Rebooted but still can't get to the host. vmbr0 is showing both the .91 and .74 IP address

Just to sum up where I am now. With the default /etc/network/interface I still have intermittent access to the Proxmox host but all VMs and CTs are working fine. It's been pointed out that, with that setup, enp3s0 and vmbr0 are being assigned the same IP address. To test this I tried taking...

/etc/network/interfaces: auto lo iface lo inet loopback iface enp3s0 inet manual auto vmbr0 iface vmbr0 inet static address 192.168.1.74/24 gateway 192.168.1.1 bridge-ports enp3s0 bridge-stp off bridge-fd 0 I tried changing iface enp3s0 inet dhcp and...

I understand I just don't know how to accomplish that. I changed the IP for vmbr0 in /etc/network/interfaces. Now I see 2 IPs for vmbr0 in ip a. Is there somewhere else I should change it?

Changed the IP of vmbr0 to 192.168.74 auto lo iface lo inet loopback iface enp3s0 inet manual auto vmbr0 iface vmbr0 inet static address 192.168.1.74/24 gateway 192.168.1.1 bridge-ports enp3s0 bridge-stp off bridge-fd 0 Rebooted. Still no connection...

Any idea what might cause that? My /etc/network/interfaces file is configured as per the documentation I'm seeing. It has not been changed and worked fine for months. Now I suddenly lose connection and get it back randomly. root@pharpe:~# cat /etc/network/interfaces auto lo iface lo inet...

Anyone have any ideas? Is the lack of response due to me not providing the right information or is it just an issue no one knows how to solve?

My connectivity to Proxmox started working again. After no connectivity for 20+ hours it magically starts working. I just ping it intermittently to check. I've done nothing to it since yesterday. Anything I can diagnose now that connectivity is back? No telling how long it will stay online...

Back to no connectivity to the host. Starting and stopping the pihole container doesn't have any effect now. If anyone could help with this I'd really appreciate it.

The last thing I did before this issue was create a pihole container. I didn't think it was related because I do not even have that container started and I'm not using it for DNS right now. I tried starting the pihole CT via cli. When it came up suddenly the host got network connectivity back...

Output of systemctl list-units --failed Output of systemctl status sshd.service Out put of ip addr There were a number of errors in the journal

I've been running Proxmox for about a year and have had no issues. Today I had to shutdown to move some wiring and when I rebooted I can no longer access the web GUI or ssh into the host. The containers and VMs are coming up and working. When I get on the terminal I cannot access and local or...

I'm having trouble figuring out how to set permissions to edit and delete files created by an LXC container. On my host I have a user named tom. I want to allow that user to delete and edit files created by user 101000. Here is an example file -rw-rw-r-- 1 101000 101000 473054718 Nov 9...

Thanks for the help.

I think I narrowed it down to a docker issue. I tried installing openvpn directly in the LXC rather in the Docker container and it's working.

Container wont start with that line in /etc/pve/lxc/102.conf Here is the whole file: #lxc.mount.entry%3A /dev/net/tun dev/net/tun none bind,create=dir #lxc.mount.entry%3A /dev/net dev/net none bind,create=dir arch: amd64 cores: 1 hostname: openvpn memory: 1024 net0...

Thanks for the quick reply. When I use that line the container starts fine but it doesn't resolve the "Cannot open TUN/TAP dev /dev/net/tun: error." This is what I'm getting when I try to start OpenVPN in the docker container. This in a Ubuntu 18.04.4 LXC and CentOS 7 LXC identically. Using...

I"m having this same issue trying to get OpenVPN to work on Ubunbu and CentOS LXC containers. I ran the following on the host mkdir -p /devcontainer/net mknod /devcontainer/net/tun c 10 200 chown 100000:100000 /devcontainer/net/tun Then updated /etc/pve/lxc/102.conf with lxc.mount.entry =...