Search results

Check the time on the client machine you are using.

Like I said, it depends on the context. It isn't clear to me whether the OP is using a web form or the API or the command line or what.

It isn't clear to me, but you seem to be running PVE inside of another virtualization. Is that correct? In that case you need to pay special attention to how the network is set up on the host side. For example, Virtualbox defaults to NAT, which means the host can't access the VM directly but the...

Likewise, he also asked for the IP of the workstation you are trying to browse from. You said "ipconfig /all" did not work. What operating system do you use? ETA: It appears from what you posted that the PVE web server is running and serving the main page and the Ethernet port is up. That means...

It said "could not resolve host LAN_IP". The only way to get that response is to have put, literally, LAN_IP, as the target of the curl command because IP addresses don't need resolving and so can't give that error. You should instead substitute your machine's real IP (e.g 192.168.1.3).

Depending on the context where you're using the password it may need to be in single quotes ('xxxx$$xxxx') or be escaped (xxx\$\$xxx).

Seriously? He wrote "LAN_IP" to indicate you should substitute the real IP of your server. Do that.

One could always install Debian to the emmc and then put PVE on top. You will need to configure the desired "saving logs elsewhere" part on your own but the basic procedure is in the manual: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_install_proxmox_ve_on_debian

This is normal. It puts the current setup in a temp file for editing. But really, on Debian-based systems, the easiest way to run something once per hour/day/week/month is to put a normal bash script into /etc/cron.{hourly, weekly, monthly}. That is how the log rotation and a number of other...

The different file thing is because crontab -e copies the current settings into a temporary file for editing. It is perfectly normal. Have you used Linux before? Did you ask for help? The usual way to run something once per hour on Debian-based systems like PVE is to drop a regular bash script...

I use OpenWRT, which is Linux- rather than BSD-based and it is on a dedicated device in any case. I'm afraid I can't help with OPNSense but they do seem to have some info on their website about running it on KVM-based hypervisors which PVE is. Might be worth taking a look.

Did you install the qemu guest tools in the VM and enable the virtio network driver in the Hardware tab of the VM configuration? Those would be the first things to check. See the manual (linked as "documentation" at the top of the PVE GUI) for details. Whether pass-through of individual ports...

The (easy-to-find) recommended method is to back up and restore the container. You can change the mode during the restore.

It is "obviously" not syncing or the time would be correct. What is the actual output of "chronyc sources"?

If your wg_server is behind a normal ISP router it isn't going to be reachable from the Internet without making some configuration changes there, like enabling a port forward.

According to Intel this chip does theoretically support VT-d but based on this [ 0.056635] DMAR: IOMMU enabled [ 0.417629] pci 0000:00:00.0: DMAR: Disabling IOMMU for graphics on this chipset [ 0.417632] pci 0000:00:00.0: DMAR: Forcing write-buffer flush capability it may not be...

If he removes it he will find out what if anything depends on it. Apt will tell him :)

Interesting. I installed mine via Debian so maybe there is some difference after all. Seems pretty clear that it isn't needed for anything though and it is safe to remove it.

I don't have nmap on my PVE 8.3.3. I don't think it is a dependency of any PVE components. You can use "apt rdepends" to find out what might be depending on it.

The following variation allows you to disable the storage (with pvesm or the GUI) and unmount the drive. Later you can plug it back in and re-enable the storage and it will automatically be mounted. I use a label rather than a UUID so I can rotate my backup drives (they all have the same label)...