Search results

I have dug through the source code of both Proxmox VE and acme.sh. The error you are getting is from this file: /usr/share/proxmox-acme/dnsapi/dns_transip.sh In particular, this part: if [ -f "$TRANSIP_Key_File" ]; then if ! grep "BEGIN PRIVATE KEY" "$TRANSIP_Key_File" >/dev/null 2>&1...

Does your key file start with the text "BEGIN PRIVATE KEY"? If it does not, add it and try again. Note: This is case-sensitive.

Yes, the remote PBS needs to access port 8007. It would be a good idea to only allow traffic to port 8007 from the IP address where you have the remote PBS. You cannot limit what API functions are available via port 8007, but you can limit what the API token can do. I usually create a user...

Yes, you can install PBS into a PVE host (i.e. side-by-side). Or, you can run PBS as a VM in PVE. Proxmox Backup Server - Installation

This should be a new post. Your original post was about network connectivity. This is about backups. No, PVE backups are for the VMs and LXCs. You might want to run a Proxmox Backup Server as a guest on Host 2. Alternatively, use something like rclone as a cronjob to sync the data.

Is this a layer 3 switch? Getting from 192.168.1.0/24 to 192.168.20.0/24 needs a router. There are a lot of options to do backups depending on what you want to achieve. There is a backup built into PVE. You can backup the whole VM.

To share data between VMs does not require it to be added as storage in PVE. If the VMs are on the same VLAN, you can just share it directly as if they were physical servers on the same subnet.

It is okay to have NFS on a VM. I am not sure what you want to achieve with NFS on the VM and adding it as PVE storage. The VM's storage is on the PVE host. I would assume the storage drives in your PVE host. You then share that storage back with the PVE host. Once you have shared it back...

I will not ask why you want to mount an NFS share of a VM in PVE... :) A bit more information would be helpful. What is the IP address and subnet of your PVE node? What is the IP address and subnet of your VM? Please run this command on your node and post the output: cat...

@Kevin José connect a monitor to node0 and log into it. Once logged in, use the command ip a and it will list all your IP addresses.

Interesting. Once you dig a little further, please update. If a ping works and an HTTP connection starts but fails, I would focus on the OPNsense VM and work from there. Stateful firewalls can behave that way with asymmetric routing — not necessarily your issue. For testing, I would remove...

Thanks for sharing the config and the side answer :) Can you tell me more about the testing and what you see when things fail? Have you tested with two computers as devices on eno3, eno4 and eno5? Or just with a computer and one of the APs? If only connecting one AP, are your tests...

Hi, fundamentally, what you are trying to do is possible. Please post the configuration for your OPNsense VM. You will find it here: /etc/pve/nodes/<node>/qemu-server/ Side question: Is there a reason you have your PVE node with IP addresses on both bridges?

Without looking at your current /etc/pve/ceph.conf It would appear you need to remove the monitor: mon.pmox02-scan-hq Here is a guide on how to do it manually: https://docs.ceph.com/en/latest/rados/operations/add-or-rm-mons/ After you remove that monitor, check Ceph's health and make sure...

Scott Looks like something changed. Is pmox02-scan-hq offline? Please post the current version of /etc/pve/ceph.conf Please also post the output of these commands: ceph mon stat ceph config show mon.pmox03 ceph config show mon.pmox01-scan-hq ceph config show mon.pmox02-scan-hq ceph config...

I have taken a deeper look at the configs you posted. Your /etc/pve/storage.cfg has the following: cifs: frigate path /mnt/pve/frigate server 192.168.2.90 share frigate content iso,images preallocation off prune-backups keep-all=1...

Cool. Did you have these powered off for a bit? Did ceph -s change after being online for a bit? Where are you at now?

Please share the config for the Frigate LXC.

Let me see if I understand correctly: You were running TrueNAS Scale as a VM in PVE. The TrueNAS Scale VM had a CIFS share called frigate. You mounted the frigate CIFS share in PVE. What was writing to the frigate CIFS share?

If the share is defined in the web GUI (or CLI) using a specific storage type (e.g. CIFS or NFS), Proxmox VE looks after it. It has more information and control over the share. If you use /etc/fstab and the Directory type storage, you need to manage whether it is online or not. Proxmox VE only...