2.3 upgrade to 3.0 ... web gui won't display but full html is being sent by server

joevsthevolcano

New Member
Dec 19, 2012
9
0
1
Hello,

I upgraded from 2.3 to 3.0 using the proxmox provided script and had no problems. That is, however, until I realized that the web GUI is no longer rendering. I can see all the HTML if I view source.

There are no errors in my daemon.log

I looked through the lengthy upgrade log and there wasn't anything that stuck out as indicative of this problem.

I have tried using Chrome, Opera, and Firefox on both Windows and *nix machines.

Is there a way to reinstall just the web interface?
 
Re: 2.3 upgrade to 3.0 ... web gui won't display but full html is being sent by serve

pls post the output of 'pveversion -v'

did you reload the browser page, empty cache?
 
Re: 2.3 upgrade to 3.0 ... web gui won't display but full html is being sent by serve

Yup, I emptied browser cache as well as hard reload. I even installed firefox and chromium on a new ubuntu to make sure it wasn't a caching issue.

# pveversion -v
pve-manager: 3.0-23 (pve-manager/3.0/957f0862)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-100
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-18-pve: 2.6.32-88
pve-kernel-2.6.32-17-pve: 2.6.32-83
lvm2: 2.02.95-pve3
clvm: 2.02.95-pve3
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-4
qemu-server: 3.0-20
pve-firmware: 1.0-22
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-8
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-13
ksm-control-daemon: 1.1-1
 
Re: 2.3 upgrade to 3.0 ... web gui won't display but full html is being sent by serve

try restarting pve-cluster and pveproxy (= webserver).

Code:
root@proxmox-6-175:~# service pve-cluster restart
Restarting pve cluster filesystem: pve-cluster.

root@proxmox-6-175:~# service pveproxy restart
Restarting PVE API Proxy Server: pveproxy.
root@proxmox-6-175:~#
 
Re: 2.3 upgrade to 3.0 ... web gui won't display but full html is being sent by serve

Done but no change. I tailed the daemon.log during the two restarts:

service pve-cluster restart
Code:
Jul  3 22:38:25 proxmox pmxcfs[100529]: [main] notice: teardown filesystemJul  3 22:38:32 proxmox pvestatd[5559]: WARNING: ipcc_send_rec failed: Transport endpoint is not connected
Jul  3 22:38:32 proxmox pvestatd[5559]: WARNING: ipcc_send_rec failed: Connection refused
Jul  3 22:38:32 proxmox pvestatd[5559]: WARNING: ipcc_send_rec failed: Connection refused
Jul  3 22:38:32 proxmox pvestatd[5559]: WARNING: ipcc_send_rec failed: Connection refused
Jul  3 22:38:32 proxmox pvestatd[5559]: WARNING: ipcc_send_rec failed: Connection refused
Jul  3 22:38:32 proxmox pvestatd[5559]: WARNING: ipcc_send_rec failed: Connection refused

service pveproxy restart
Code:
Jul  3 22:38:47 proxmox pveproxy[5589]: received terminate request
Jul  3 22:38:47 proxmox pveproxy[5589]: worker 70058 finished
Jul  3 22:38:47 proxmox pveproxy[5589]: worker 70059 finished
Jul  3 22:38:47 proxmox pveproxy[5589]: worker 70060 finished
Jul  3 22:38:47 proxmox pveproxy[5589]: server closing
Jul  3 22:38:50 proxmox pveproxy[100642]: starting server
Jul  3 22:38:50 proxmox pveproxy[100642]: starting 3 worker(s)
Jul  3 22:38:50 proxmox pveproxy[100642]: worker 100643 started
Jul  3 22:38:50 proxmox pveproxy[100642]: worker 100644 started
Jul  3 22:38:50 proxmox pveproxy[100642]: worker 100645 started

I have attached a txt file of the HTML being sent to the browser (but not rendering). I'm not a JS guy so I don't even know where to start debugging that.
 

Attachments

Re: 2.3 upgrade to 3.0 ... web gui won't display but full html is being sent by serve

Also try to restart service "pvedaemon" (after "pve-cluster)
 
Re: 2.3 upgrade to 3.0 ... web gui won't display but full html is being sent by serve

I tried restarting pvedaemon but no change. I have, however, discovered something really strange.

I have however partially figured out the culprit. All of the different browsers and computers I was trying this on connect to the proxmox server via openvpn. If I use the public IP of the proxmox server, so the traffic doesn't go over the VPN, the GUI loads fine. I'm not getting any errors though and I never had a problem with this under proxmox 2x. This only started happening when I upgraded to v3. I am going to guess that the change from apache may may not work well with a UDP vpn and I plan on testing this by swapping to TCP later tonight once the office has cleared out.