Search results

thanks, will try that

Hi, I am having problems with backing up lxc containers which were accidently created with the "unprivileged" flag. I want to test if using them in "privileged" state solves the backup problem. But how can I change that? In pct on the command line there is no option to change the unprivileged...

sorry folks, this was my fault, the lxc ran with unpriviledged = no, now all ist fine with #database server # #db1.toko.loc #IP 192.168.4.16 #Gateway 10.10.10.16 arch: amd64 cores: 2 hostname: db1 memory: 1024 nameserver: 10.10.10.1 net0...

It seems like this problem ist till not solved on 6.0.9: root@db1:~# systemctl status mariadb.service * mariadb.service - MariaDB 10.4.8 database server Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/mariadb.service.d...

Die Lösung von Adrian funktioniert :) PVE /etc/network/interface: # eth0 primary ipv4 auto enp0s31f6 iface enp0s31f6 inet manual address x.x.x.x netmask 255.255.255.192 gateway y.y.y.y # vbridge for public network auto vmbr0 iface vmbr0 inet static address...

Hi all, I have a problem with the routing of additional IPs on vmbr0 which are from a different subnet. My installation is a proxmox PVE community 6.x on a hetzner root server. The networking setup is routed and my primary network segment is 138.201.52.x/26 with 138.201.52.41 as the main...

ok, as I said before: it depends on the use case behind If you need so many IPs, its possible that NAT is the best strategy.

Both strategies (routed/bridged or NAT) have their pros and cons and may be adequate, depending on the detailed use cases. In my case, I used a NATted setup on a previous hetzner server in combination with headless virtualbox VMs, now I switched to a routed setup on a new server and for...

additional ips

Example network/interfaces for the proxmox server (check your own settings as provided in the hetzner robot): auto enp0s31f6 iface enp0s31f6 inet static address [public ip of hetzner root server] netmask 255.255.255.192 gateway [hetzner gateway] pointopoint...

I am now using a routed setup instead and all works fine. The original problem is solved and the thread can be closed. PS. yes, I know, the macs for bridged setup have to be requested and set in the hetzner robot

ok, the problem was the bridged setup, the routed setup works fine: auto lo iface lo inet loopback iface lo inet6 loopback auto enp0s31f6 iface enp0s31f6 inet static address [REDACTED] netmask 255.255.255.192 gateway [REDACTED] pointopoint [REDACTED]...

no, this is my first proxmox server, migration will be done manually from another virtualbox server

Hm, I used the documentation at https://community.hetzner.com/tutorials/install-and-configure-proxmox_ve/de?title=Proxmox_VE But maybe I mixed something up here ... I could also switched to a routed setup if this has advantages. Which one is better, seen from the PVE point of view?

auto lo iface lo inet loopback iface lo inet6 loopback auto enp0s31f6 iface enp0s31f6 inet static address [REDACTED] netmask 255.255.255.192 gateway [REDACTED] up route add -net [REDACTED] netmask 255.255.255.192 gw [REDACTED] dev enp0s31f6 # route...

I have separate MACs for both VMs and added these MACs in the MAC Address field in "Edit: Network device" on the VM level. Just re-checked if I have the correct MACs and all seems to be fine ... Are there any additional checks I can make on the cli level?

Hi all, I am a newbie to proxmox, so please apologize if my questions are a bit "basic" I have a running proxmox 6.05 on a Hetzner EX42 server with debian 10, bridged setup and two bridged VMs (ubuntu 18 lts). Setup was done following the documentation at the proxmox wiki for Debian Buster...