Search results

@fiona did this patch not make it into v1.0.1? or am I experiencing a new issue?

Yes, just nesting worked.

Thanks @fiona, the 2nd error was apparently if any features are set, the migration will fail. The failed migration also leaves the source LXC in a locked state. I was able to get this working by unsetting nesting/keyct features, then migrating, then re-setting on the new system. one other note...

I could replicate this in 0.1.9 Application panicked! Reason: panicked at /usr/share/cargo/registry/proxmox-yew-comp-0.3.6/src/rrd_graph_new.rs:637:41: index out of bounds: the len is 0 but the index is 0 when I tried to click on a graph that didn't seem to load.

Migrating offline LXC container from single node to cluster. Migration Error: 2024-12-29 12:44:09 remote: started tunnel worker 'UPID:pve-nuc-0:00108181:00814094:67719879:vzmtunnel:903:root@pam!pdm-admin:' tunnel: -> sending command "version" to remote tunnel: <- got reply 2024-12-29 12:44:09...

+1 ran into this issue as well

IPv6AcceptRA seems to be auto-set to False when setting LXC containers to DHCP on network settings for IPv6. Is there a setting I can adjust to change this to True?

@fabian any timeframe on the DNS validation option? AWS/R53? Potentially support for wildcard certs?

Thanks!

Can someone post clear instructions on how to downgrade novnc until this is resolved?

So I've selected xterm.js as my console default option in the cluster, and configured both the host and guest system to use it, which is working, yet when I select console via the sidebar, it still goes to novnc. Is there a setting I'm missing?

No luck, I get this issue on multiple browsers/systems and after full chrome resets.

I ran the upgrade from the web console, on 4 identical systems, same hardware, yet only one has this issue... very puzzling... I am able to login via SSH without issue, only the webui console is missing the realm. root@pve-2:~# pveversion -v proxmox-ve: 5.1-42 (running kernel: 4.13.16-2-pve)...

After my last update, I can't login to the web console because the realm is blank and it requires a realm to login. Oddly 3 other servers with the exact same configuration did not have this issue post-update.

Does anyone have instructions how to downgrade just noVNC to the version Proxmox 4 is using?

@mir can you expand on how to enable sticky sessions?

I am using a similar config based on https://pve.proxmox.com/wiki/Web_Interface_Via_Nginx_Proxy which is close to warinthestars and also am unable to get NoVNC working using a reverse proxy.

Thanks dcsapak - this did work, but seems rather intuitive.

Hello, I have a QNAP SAN with a specific folder full of ISO's. I configured this on my proxmox server and the NFS mount shows up, and the ISO's show up on disk on the pve server. I can also see ISO's when I browse: Yet when I attempt to create a new VM, and set the ISO: I am unable to...