Search results

I found the configuration like below for proxy pve behind nginx, it works fine except novnc. When I open novnc window in chrome, it shows error: server { listen 443; server_name _; ssl on; ssl_certificate /etc/nginx/ssl/cert.pem; ssl_certificate_key /etc/nginx/ssl/key.pem...

When many people use novnc, the api server(web gui, novnc) will not response for new connection. But the novnc alreay opend still working, and the command 'pveproxy status' shows the service is running. After edit the /usr/share/perl5/PVE/Service/pveproxy.pm, change the 'max_workers' option...

For some reason, I disable the debian ipv6, after that in the 'network' tab of web gui the 'vmbr0' property 'Active' become 'No'. I find the error code in 'INotify.pm': if ($proc_net_if_inet6) { while (defined ($line = <$proc_net_if_inet6>)) { if ($line =~...

After upgrade to pve 4.0, I can't set the kvm note include chinese chractor, but in pve 3.x it works fine. It seems like a encode or decode bug.

After upgrade to pve 4, I got the error every time when I start or reboot my server. Oct 28 09:11:43 host00 systemd[1]: [/run/systemd/generator.late/qemu-server.service:7] Failed to add dependency on +iscsi.service, ignoring: Invalid argument I have...

When I config a linux bond "bond0" with gui, the option "Autostart" is checked. After reboot, the "bond0" is not correct configured, seems like 'Autostart' option is now work. Proxmox ve 3.4 does not have this problem.

I found this error : 'EV: error in callback (ignoring): received unhandled websocket opcode 10' form the log file /var/log/daemon.log when my pve-manager lose response again. The pve-manager gui won't work again until I restart the service pveproxy. And this problem occurs frequently.

When set qemu's 'arg' option, the system will notice me "only root can set 'arg' config". For some reason , I can not give user the root password, but the opertion user has the role 'Administrator'. I tried to change the file '/usr/share/perl5/PVE/API2/Qemu.pm', and edit the code...