blank screen when installing VM

[cptwonton]

on a 2 node cluster, trying to install fedora workstation v43 live using iso will get me to a blank screen on the network tab at the very end of the modal.



although clicking back can navigate me back, clicking next doesn't take me anywhere, and I'm stuck at the networking step with no way to proceed.

1. both nodes are running pveversion 9.1.2
2. not sure if this is related, but I did install proxmox on my first node with hostname A and then changed it to hostname B. this caused some issues, including breaking corosync. had to manually modify files and etc to get the node back up again. this issue installing VMs may be a remnant of that renaming, though my second node was not renamed and has stayed the same hostname since inception, yet I'm still unable to install the VM on either node using the webUI.
3. ssh-ing into a node and using qm cli commands to create the VM works just fine, and the UI reflects the creation. the CLI options I set aligned 1:1 with the UI options I picked. Yet UI gets stuck while CLI works.

Here are screenshots of what I had selected prior to getting stuck on the network tab. I just took defaults, though I have also tried changing various options like machine type to q35 or ram/core count to no avail

 

[dcsapak]

can you open the browser console before and then reproduce it? is there any error there?

 

[cptwonton]

thanks for the suggestion Dominik, wish I had thought to do that yesterday.

I tried just now, with console open, and proxmox decides it wants to behave.
I've changed nothing about my cluster since posting yesterday, so really unclear why it's suddenly working now.

for posterity, I was
- using safari v26.2
- on the same LAN as the boxes on my cluster when attempting to create all those times yesterday
- accessing my cluster via my externally published domain, but hitting only my local DNS via split horizon

now, unable to reproduce, I'm
- still using safari v26.2
- offsite, not on the same LAN as the boxes on my cluster. also tried VPN-ing in to get as close as possible to yesterday
- accessing via the same externally published domain name, but thru other DNS services first before the reverse proxy I have set up internally

 

[bl1mp]

hi cptwonton,
maybe it was a caching issue related to the node renaming. How long a ago die you performed the renaming?

Private browsertabs might also help with verifying webui issues and the browser console like Dominik already pointed out.

BR, Lucas

 

[cptwonton]

reproduced it. here is the console: