Search results

Does the LXC itself have access to the Internet? Or. try the masquerade. OR PreUp = iptables -I FORWARD -i wg0 -s 192.168.2.12/32 -d 0.0.0.0/0 -j ACCEPT PostDown = iptables -D FORWARD -i wg0 -s 192.168.2.12/32 -d 0.0.0.0/0 -j ACCEPT

When I had Proxmox 7.x, I also used Wireguard in LXC. I always set it accordingly. In the summer of 2023, I switched to Proxmox 8.x and forgot to do this setting, and Wireguard still works in LXC. Is it necessary to do this setting only for OpenVPN, or also for Wireguard? Someone answered on...

Thanks, it's fine. I imported the pool successfully. Some info on oracle as well

I understand, it means that I should always export zpool before reinstallation and it won't complain when importing. So I can use the command without any worries zpool import datapool -f -d /dev/disk/by-id

Until now I was running on Proxmox 7.3-4 and today I installed a clean Proxmox 8.0.3. Everything works great, VM and LXC are running. There are 2 data SSDs in the system on which ZFS Mirror was installed. zpool import pool: datapool id: 5891050705304534901 state: ONLINE status: The...

I don't like upgrading proxmox. A clean installation is better.

Well thank you. I thought so. However, I have to wait another week. Alternatively, can I do a dist-upgrade without rebooting PVE? I plan to install Proxmox 8 soon

run_buffer: 321 Script exited with status 25 lxc_init: 847 Failed to run lxc.hook.pre-start for container "114" __lxc_start: 2008 Failed to initialize container "114" d 0 hostid 100000 range 65536 INFO lsm - ../src/lxc/lsm/lsm.c:lsm_init_static:38 - Initialized LSM security driver AppArmor...

I tried, but same problem apt update && apt dist-upgrade -y run_buffer: 321 Script exited with status 25 lxc_init: 847 Failed to run lxc.hook.pre-start for container "114" __lxc_start: 2008 Failed to initialize container "114" TASK ERROR: startup for container '114' failed However, I don't want...

I apologize, after installation rebooted without problems. A problem occurs even after the update apt update && apt upgrade -y run_buffer: 321 Script exited with status 25 lxc_init: 847 Failed to run lxc.hook.pre-start for container "114" __lxc_start: 2008 Failed to initialize container "114"...

proxmox-ve: 7.3-1 (running kernel: 5.15.83-1-pve) pve-manager: 7.3-4 (running version: 7.3-4/d69b70d4) pve-kernel-5.15: 7.3-1 pve-kernel-helper: 7.3-1 pve-kernel-5.15.83-1-pve: 5.15.83-1 pve-kernel-5.15.74-1-pve: 5.15.74-1 ceph-fuse: 15.2.17-pve1 corosync: 3.1.7-pve1 criu: 3.15-1+pve-1...

It's a home server and it's idle a lot of the time. CPU is Intel Core i5-10400, MainBoard If you know of any settings to reduce consumption, I will be grateful

I recently saw this procedure as a way to reduce electricity consumption. I set it up the way the guy describes it echo "powersave" | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor It is set from 7:00, see graph. The CPU increased from 2% to 4%, but the total consumption decreased by...

If I use RAIDZ, I assume that all disks must be spinning all the time. Or am I wrong ?

Proxmox 7.4-3 HW everything new MB: asus rog strix x570-e gaming wifi ii bios CPU: AMD Ryzen 7 5700X Ram: 2x Kingston FURY 32 GB KIT DDR4 3200 MHz CL16 Beast Black Power supply: Seasonic Focus Plus 550 Platinum Cooler: Scythe Ninja 5 (SCNJ-5000) System disk raid0: 2x WD Red SN700 1TB M.2 2280...

In Proxmox I created from 4x 18TB HDD Raidz (52TB). Then I created a 12 TB zvol and assigned it to VM (Debian). In my debian, I formatted the disc to ext4 and everything works well. I have some data on the 12 TB section. Now I would like to increase the section to 16TB. Is it possible without...

I use MC Midnight Commander

I have only one node that is not connected to the cluster. I followed the instructions I set a new name in nano /etc/hosts nano /etc/hostname nano /etc/postfix/main.cf reboot Next, through the MC, I entered the /etc/pve/nodes/ but copy (F5) didn't work. In the proxmox web interface, I saw...

Yes, the problem is solved. The problem was not proxmox, but the DHCP server. Proxmox had a MAC address of vmbr0 18:c0:4d:0a:03:2c and an IP address 192.168.1.3 DHCP had a different MAC address 6c:60:eb:90:bc:c4 assigned to the IP address 192.168.1.3

Probably no one would come up with that. I always use the static IP 192.168.1.3 for proxmox. I use pfsense firewall and in DHCP I have bind MAC with IP addresses. For the IP address 192.168.1.3, I had the MAC address from the previous Proxmox.