Search results

I did all those things and it still didn't work. I had to do these additional steps... apt update apt install rsyslog After installing, start the service: systemctl start rsyslog Enable the service to start on boot: systemctl enable rsyslog Verify the Service Status: systemctl status...

I'm facing a similar issue. Except, If I reboot the VM the raid is still there. If I reboot the host, it's gone. I have to recreate it everytime. Still no answer to the problem. I've tried... qm set <vmid> -virtio0 /dev/disk/by-id/<my_disk> qm set <vmid> -sata0 /dev/disk/by-id/<my_disk> Neither...

Maybe instead of attaching a HD like this qm set 3000 -sata0 /dev/disk/by-id/wwn-0x50014ee262bb97b7 I should do it like this qm set 3000 -virtio0 /dev/disk/by-id/wwn-0x50014ee262bb97b7 ?

I'm running Proxmox 8.1.4 and have an Ubuntu server 22.04.4 LTS VM that was a hardware server and I virtualized it. I successfully configured 3 hard drives from the Proxmox host to the Ubuntu VM. Those three drives were setup as a RAID 5 with mdadm before I virtualized it. I successfully...

I'm running Proxmox 8.1.4 and have an Ubuntu server 22.04.4 LTS VM that was a hardware server and I virtualized it. I successfully configured 3 hard drives from the Proxmox host to the Ubuntu VM. Those three drives were setup as a RAID 5 with mdadm before I virtualized it. I successfully...

Same here I have a Dell Poweredge R520. It was running Proxmox 6.4.14 just fine. I decided to upgrade to 7 and it blew up on me. The server boots and I can still connect via ssh. But the GUI is dead. I followed the instructions from here...

I found the problem. It was with the router. I had MAC address filtering turned on. Typically all I did when adding a new device to my network, I would go into the mobile app, find the device and allow it to connect. For some reason, my router would not add the device. I only found it when I was...

Ok. It’s not a Windows firewall issue. What I’ve discover is when I connect my laptop to a dock with a wired connection, I can access the container. When I pull it off the dock and it goes wireless, it cannot. That holds true with two different laptops and my iPhone. Thus it has something to do...

I cannot connect to Webmin, WebDAV, Web shell, SMB and ssh.

I've done that. On the working system then only entry is 192.168.0.68. No other hops. The none working system comes back empty handed.

That's what I was thinking as well. The question is where do I look for that?

My DHCP is fine. All the VMs I have running on proxmox are accessible to all the computers on my network. It's just the container that has the problem. Yes I figured it was a config or firewall issue. The questions are what config issue? What firewall issue? I've turned it off on the container.

I have proxmox setup on a Dell Poweredge R520 with an IP address of 192.168.0.11. I created a container from the TurnKey fileserver container. Currently I have the IP address of the container set to DHCP and it obtained the IP address of 192.168.0.68. My Windows 10 Desktop computer has a router...