Search results

If your /etc/pve folder is empty, you have issues. Regarding your network issue, when you switch it back to the original configuration, does it work? Also R700s are really old.

Because they are a different products with that feature. Proxmox does not have every feature every other hypervisor has and other hypervisors do not have every feature Proxmox has.

As mentioned before, you cannot just suspend your VMs. You would have to create a snapshot.

You can limit users from being able to add/remove network interfaces to the physical servers and VMs, but you cannot limit what interface is available after it is added to the physical server.

As far as I know, this is not a feature supported by Proxmox. I would also like to note that if you manually suspend your VMs before shutting down, it will not resume normally. The only work-around I can think of is to create a script to snapshot, shutdown, reboot, restore.

Side note, I had this same issue about a month ago. I believe I installed a non-pve version of a package and it caused similar issues.

Authentication is not affected. SSL certification works just like any other website.

Thanks all for the input. It was helpful to hear the pros and cons of running Proxmox on a USB. I should have clarified this is for a home environment. With that being said, I am going to continue running Proxmox on a USB. If it dies, it dies. If it Proxmox runs a tad slower, meh, I am not on...

The general consensus seems to be that reading and writing onto a USB often would wear down the flash drive quickly. However, I believe ESXi loads the hypervisor into memory on boot. What is stopping Proxmox from implementing a similar setup?

If you reboot from the container's terminal, then statistics will not show. However if you use pct stop and pct start, then the statistics will remain. AFAIK, you must reboot to get the statistics working again.

If you reboot from the container's terminal, then statistics will not show. However if you use pct stop and pct start, then the statistics will remain.

Try this. Do not forget to restart the container after editing the profile. lxc.aa_profile=unconfined

https://pve.proxmox.com/wiki/Network_Model https://pve.proxmox.com/wiki/Vlans

You going to have to allocate more space to root which is difficult. I would instead install docker on a VM or use LXC instead.

Before trying to mount it at boot, check if you can see the mount and attempt to mount it manually using: showmount -e 10.10.10.10 mount 10.10.10.10:/path/to/folder /mnt/nfs Personally, I have not been able to get NFS working without adding "lxc.aa_profile: unconfined" to the container...

I have not tested accessing Proxmox through a reverse proxy subdirectory. Though, a subdomain should also work if that is acceptable for you. Code: server { listen 443 ssl; server_name subdomain.example.com; location / { proxy_pass https://10.10.10.5:8006...

I suggest storing your media on a different storage device than your Plex server. In regards to backing up your data, see https://pve.proxmox.com/wiki/Backup_and_Restore. In your case, backing up your media files then rebuilding your Plex server from scratch. However, troubleshooting why your...

This still sounds like a port forwarding issue to me. Can you SSH in? As LnxBil stated, it is best to use SSH tunneling anyway. Here are generic example rules: External Port Ext. IP Address Internal Port Internal IP Address TCP/UDP: 8006 Any TCP/UDP: 8006...

Can you ping your server using its external address? Is it the correct IP address? What is the browser error?

Make sure you are attempting to access using HTTPS, not plain HTTP. You may have to manually enter: https://example.com:8006 Otherwise, you will get an ERR_EMPTY_RESPONSE.