Recent content by CyberKiller_MDS
-
C
VM/Container stuck at 0% on apt-get
I disabled it, still not working- CyberKiller_MDS
- Post #7
- Forum: Proxmox VE: Installation and configuration
-
C
VM/Container stuck at 0% on apt-get
Just install proxmox on computer, no problem with apt, on vmbox > proxmox i have, same configuration on both... Yes i can ping, i try apt-get clean, same... still have a problem... Can't run dig, can't run wget... I think something with DNS is problem...- CyberKiller_MDS
- Post #5
- Forum: Proxmox VE: Installation and configuration
-
C
VM/Container stuck at 0% on apt-get
root@test:~# ping google.com PING google.com (172.217.169.206) 56(84) bytes of data. 64 bytes from sof02s34-in-f14.1e100.net (172.217.169.206): icmp_seq=1 ttl=120 time=7.72 ms 64 bytes from sof02s34-in-f14.1e100.net (172.217.169.206): icmp_seq=2 ttl=120 time=9.57 ms --- google.com ping...- CyberKiller_MDS
- Post #3
- Forum: Proxmox VE: Installation and configuration
-
C
VM/Container stuck at 0% on apt-get
I have a problem on this configuration: Router (192.168.0.1) VirtualBox (192.168.0.100) > Proxmox (192.168.0.110) > Ubuntu/Debian (192.168.0.115), in proxmox all is ok, but in VM/Container (Debian or Ubuntu) i can ping, but can't do apt-get update, it stuck on 0%. I use bridged mode on...- CyberKiller_MDS
- Thread
- Replies: 7
- Forum: Proxmox VE: Installation and configuration
-
C
apt-get update results in waiting for headers and does not update
I have a similar problem on this configuration: Router (192.168.0.1) VirtualBox (192.168.0.100) > Proxmox (192.168.0.110) > Ubuntu/Debian (192.168.0.115), in proxmox all is ok, but in VM/Container (Debian or Ubuntu) i can ping, but can't do apt-get update, it stuck on 0% like in this case. I use...- CyberKiller_MDS
- Post #18
- Forum: Proxmox VE: Installation and configuration