Recent content by Andrey Zentavr

@emersonfelipesp another issue is that the code want to write something into .venv folder here: https://github.com/emersonfelipesp/proxbox-api/blob/faa7f4bcb115b19f4a0a4b9d398d82226fd946e7/proxbox_api/proxmox_to_netbox/netbox_schema.py#L20-L23 I think that should be configurable. I had 116 VMs...

The image is expected to be executed as root which is forbidden in our organization. So I had to attach the volume into `/data` and set up some extra variables: - name: PROXBOX_BIND_HOST value: "0.0.0.0" - name: PORT value: "8000" - name: PROXBOX_LOG_LEVEL value: "INFO" -...

Tried to fix the token - no luck. In the netbox I did: ubuntu@netbox-7f4d9cb878-knt9k:/opt/netbox/netbox$ python manage.py proxbox_fix_tokens --fix loaded config '/etc/netbox/config/configuration.py' loaded config '/etc/netbox/config/extra.py' loaded config '/etc/netbox/config/logging.py'...

I had upgraded the plugin to `netbox_proxbox: 0.0.21` and have the same error when come to Proxbox - Homepage, pick up proxmox endpoint and go to Cluster Nodes tab.

Unfortunately after fixing the error with `cluster/status` the sync did not started to work. In 3 consoles (netbox, proxbox, netbox-worker) I do not see any traces, but the sync of nodes, VMs, etc fails. When I'm trying to check `Cluster Nodes` - see the error: [2026-06-28 01:57:00 +0000]...

Ok, nevermind - fixed that. I had to add the user to the group, assign the permissions especially for the group and for the token. ...complex Proxmox ACLs, huh!

Hello @emersonfelipesp. I'm trying to set up your plugin and have this: proxbox [2026-06-28 01:17:38,979] [WARNING] proxmox_core: Connected to Proxmox 1.2.3.4:8006 but cluster/status is forbidden; continuing in restricted mode INFO: 10.42.1.248:38162 - "GET...

There are a couple servers available at Hetzner (Finland region). You can also order additional hard drives and switches is needed, so you can build a cluster.

Any support for ARM64 CPUs?

We have that smaller server from Hetzner as well. Right now Ubuntu is there, but there is a request from our dev.team to have a dozen of VMs so I would like to build a cluster and attach our CEPH storage.

Not yet, but we are seeking for virtualization solution

You can also change limits on already running process as well: #!/usr/bin/env bash for PID in $(ps aux | grep /usr/bin/kvm | grep -v grep | awk '{ print $2 }'); do SOFT_LIMIT="1048576" HARD_LIMIT="2097152" echo "Changing the limits for PID ${PID}" prlimit...

Please try my solution (steps 3...6) from this reply. You can check the limits with this script: #!/usr/bin/env bash for PID in $(ps aux | grep /usr/bin/kvm | grep -v grep | awk '{ print $2 }'); do SOFT_LIMIT=$(cat /proc/${PID}/limits 2>/dev/null | grep "Max open files" | awk '{ print $4 }')...

The workaround is the next: 1. **/etc/sysctl.d/90-rs-proxmox.conf**: ``` # Default: 1048576 fs.nr_open = 2097152 # Default: 8388608 fs.inotify.max_queued_events = 8388608 # Default: 65536 fs.inotify.max_user_instances = 1048576 # Default: 4194304...

I have the same issue when I have DB server with 10 virtio drives per VM.