Search results

Now i cant login to GUI :( My first container dont work pct list dont work: ipcc_send_rec[1] failed: Connection refused ipcc_send_rec[2] failed: Connection refused ipcc_send_rec[3] failed: Connection refused Unable to load access control list: Connection refused Login dont work may 27...

Hi all. I'm on 7.4.3 When i try to make a backup in snapshot mode (or suspend) vzdump never ends with no error. root@server:/backups# vzdump --mode suspend --all 1 --tmpdir /backups/tmp/ --dumpdir /backups --compress zstd --prune-backups 'keep-daily=2 First i try without tmpdir and dumpdir...

Finally solved. rm -rf /etc/pve Check /etc/hostname and /etc/hosts reboot

UPDATE: I delete /etc/pve and then reboot. Now I can login GUI :) But my LXC containers are down Next step!

If helps... My /etc/pve is empty (right now not, after https://pve.proxmox.com/wiki/Proxmox_SSL_Error_Fixing guide). But I have only manual certs into it :( Working Proxmox: --- I checked my disk and I have free space into it Broken proxmox:

Hi all. After electric failure my server rebooted. Then I can access any of my lxc containers, and proxmox GUI is off. I located an error about /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/ Then I change my /etc/hosts , deleted 121.0.0.1...

Solved. My actual config: lxc.cgroup2.devices.allow: c 108:0 rwm lxc.mount.entry: /dev/net dev/net none bind,create=dir lxc.mount.entry: /dev/ppp dev/ppp none bind,create=file Then lxc-device -n MyContainer add /dev/ppp After this, I need to restart my docker container and finally I can...

I can access to VPN into my Mac using docker. But when I use it over proxmox, I can't access to /dev/ppp interface :( , I think it's the only thing I need to make it work

After restart all seems equal. VPN can't connect. root@rosita:~# ls -l /lib/modules/5.15.53-1-pve/kernel/drivers/net/ppp total 180 -rw-r--r-- 1 root root 16824 ago 26 16:53 bsd_comp.ko -rw-r--r-- 1 root root 24944 ago 26 16:53 ppp_async.ko -rw-r--r-- 1 root root 14664 ago 26 16:53...

Hi all. I'm on Proxmox 7.2 Then I install a LXC container from here: https://github.com/tteck/Proxmox (Docker LXC script). arch: amd64 cores: 14 features: fuse=1,nesting=1 hostname: docker memory: 122880 net0...

I'm gone change max usage to 16 GB https://linuxhint.com/configure-zfs-cache-high-speed-io/ Thanks

Yes, I'm on ZFS file system :(

I have a fresh install (proxmox 7) with 128 GB RAM Then I create 2 x CT to use MariaDB, 4 RAM each other. 1 x CT to use docker inside. If I go to each CT, I can see MariaDB are using 1 x GB each other (2 in total) and docker CT are using 1 more = 3 GB RAM But when I go to Server in proxmox...

I try to change my first ip from other one. Then works (again, only eth0) with the new ip. This confirms tha OVH can router the ip to proxmox and the error is in Proxmox or Container (Centos 7). I check /etc/sysconfig/network-scripts/ifcfg-eth0 vs /etc/sysconfig/network-scripts/ifcfg-eth1 and...

Sorry, I mix the result form cpanel XD The fact is, I have a promo with 2 CT The first ip from each other, responds to ping Next ip's, doesn't They are configured in the same way: Ip failover (OVH), Mac, Gateway, No firewall. I have other server with the same configuration and works as expect.

Hi all. My first ip works as expect. But next ups dont, I can't do ping If I set "ip -a" I can see all of the as "up I want to use them as name servers into cpanel, but I can't use them :( pveversion pve-manager/6.4-13/9f411e79 (running kernel: 5.4.166-1-pve) 1: lo: <LOOPBACK,UP,LOWER_UP>...

Hi all. The Scale servers from OVH cannot use bridge mode. we need to use router mode instead. Using this guide https://pve.proxmox.com/wiki/Network_Configuration#_routed_configuration we can configure and access our server: auto lo iface lo inet loopback iface enp193s0f0np0 inet manual...

In scale servers, we cannot use bridge as network type, after talk with OVH

I need to make it work with proxmox and each vm with it's ip's. My ubuntu 20.04 Netplan config is empty. Then: nano /etc/netplan/01-netcfg.yaml network: version: 2 renderer: networkd ethernets: eth0: dhcp4: no dhcp6: no...

Something estrange: root@shared1:~# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128...