Search results

Hi, I've been following the suggestions and steps from the Upgrade_from_6.x_to_7.0 wiki and, right now, I am stuck at 93% for more than an hour or so in the apt dist-upgrade execution. This is what the SSH screen shows now: Setting up libmath-random-isaac-perl (1.004-1.1) ... Setting up g++-10...

Hi @roboboard, What I simply did is to configure Websocket connections in my reverse proxy service (nginx, Apache, HAProxy, Traefik, whatever). I've no access to the old config as I entirely changed my lab architecture, sorry!

Hey, Do you have public git with app release and so on? I'd like to see a changelog, as you update the app almost everyday :-).

Hey! Thank you for your deep analysis! You followed a similar procedure to proxmox-stuff git that @bootsie123 sent above. It's very useful for who are searching for a correct backup procedure as me.

Yes, that's exactly what I am looking for! Thanks. I will check it. Edit: script seems very good but I don't know if restore all /etc/ folder is a good practice. You may need to change a hardware component (i.e.: HDD) due to failure and files inside /etc/pve files won't be fully valid (if I...

Hey! Did you make a useful script then? Thanks!

Hi, Due to recent resizing issue which provokes me to restore backups from a VM, it seems that my metadata space are almost full now: I've read and try some suggestions of the forum, trying to expand tmeta or reduce tdata it but, as you can see, data_tdata has all the remaining space...

Hi, Thank you for your answer. I didn't know the fact that I need to recreate the partition. Probably I'll change to lvm logical as soon as I fix a new problem regarding metadata due to snapshots :confused:. Creating a new thread right now... Thank you again!

Hi, I'm in the middle of an issue which probably has a solution but my poor Linux knowledge seems to be a problem in these type of situations. I've a VM with 20GB assigned space, using Debian 9.9. I'd like to expand the space from 18.5G to ~100G. In Proxmox: I don't need to reboot to see...

Hi all, I recently upgraded the pending packages without no issues but since I restarted the server, web interface shows me the next message: Connection error 596: tls_process_server_certificate: certificate verify failed It seems it changes the node name (?) to "pve" and all the CT/VMs are...

Omg that was all! I've configured it and everything works quite well now! Thank you so much both! :)

@r.jochum the difference between both is: LAN -> you connect through https://localip:8006 WAN -> you connect from https://domain.ltd:8006 In my case, to avoid to open the port, I created a subdomain https://pve.domain.ltd, and here is the problem. I can navigate and interact with Proxmox web...

nc: connection timed out is the output in my case o_O

If I exec termproxy in terminal1 and then nc -l -p 5900 in terminal2, the results are: term1: timed out waiting for client term2: nc: bind to source 0.0.0.0 5900 failed: Address already in use However, if term2 first and then term1, it returns: term1: failed to open socket: Address already in...

Hmm, what do you mean exactly? Could you explain a bit more?

Hey, Thanks for reply. It was rebooted when I updated it to Proxmox v5 (not quite long ago). I'll update kernel now! Regarding the code above (/nodes/p33ps is correct :)): /usr/bin/termproxy 5900 --path /nodes/p33ps --perm Sys.Console -- /bin/login -f root The output is: timed out...

Hi, Is the output above useful? Thanks!

Yes, of course. Here you have: proxmox-ve: 5.2-2 (running kernel: 4.4.19-1-pve) pve-manager: 5.2-1 (running version: 5.2-1/0fcd7879) pve-kernel-4.15: 5.2-2 pve-kernel-4.15.17-2-pve: 4.15.17-10 pve-kernel-4.4.128-1-pve: 4.4.128-111 pve-kernel-4.4.35-2-pve: 4.4.35-79 pve-kernel-4.4.35-1-pve...

I opened 8006 just to test if xterm/VNC works outside LAN, and it worked like a charm through https://domain.ltd:8006, so it seems that something happens with subdomain setup but I cannot find anything :confused:

::::: It has been SOLVED ::::: Until few days ago, I was using https://domain.ltd:8006 to login into the web UI but I've changed it to https://sub.domain.ltd and it seems something has been broken because I cannot use noVNC or xterm console outside LAN (there is no problem in LAN, it works...