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!
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...
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...
@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...
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...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.