I would like to make a point. At this time I am upgrading all my PVE servers. I am observing that in servers where previously the original installation was PVE 7 and later upgraded to PVE 8 I have this problem with the latest kernel update. In the servers where I installed PVE 8 from the...
I solved it this way:
inxi -n
I took note of the new network interfaces nomenclature and then changed the references inside:
nano /etc/network/interfaces
Rebooted everything and now it seems to work.
hello jjasen, I also noticed that all the networking features do not work with kernel 6.8.4-2 and 6.8.4-3.
i don't think it is not a problem related to the x710 network card...
X722 card also does not work for me. I also have the X710 card
these are my network cards:
inxi -N
Network...
yes! now i can log in! i will apply for a new certificate, hopefully everything will go smoothly
the path you gave me was missing a /local/ :D
rm /etc/pve/local/pveproxy-ssl.*
no, it's a server at one of our sites, there are no proxies or anything, this problem occurred when I applied for the new let'encrypt certificate which couldn't be renewed... I was accessing it until just before renewing the certificate.
sorry fabian, what an idiot I made of myself :-P
apr 14 20:43:37 umox systemd[1]: Starting PVE API Proxy Server...
apr 14 20:43:39 umox pveproxy[1324]: Using '/etc/pve/local/pveproxy-ssl.pem' as certificate for the web interface.
apr 14 20:43:39 umox pveproxy[1326]: starting server
apr 14...
it seems to be from February...
# journalctl -u pveproxy
-- Journal begins at Sat 2023-02-25 18:27:16 CET, ends at Mon 2023-04-17 17:19:37 CEST. --
feb 25 18:27:25 umox systemd[1]: Starting PVE API Proxy Server...
feb 25 18:27:26 umox pvecm[1299]: Generating public/private rsa key pair.
feb 25...
wow! yes the field must be empty!
only now I had a problem when renewing the certificate on another server:
An error occurred while connecting to xxxx.XYZ.it:8006.
PR_END_OF_FILE_ERROR
Error code: PR_END_OF_FILE_ERROR
The page you are trying to view cannot be displayed because the...
I don't think the service is offline ... If I try to request a registration I get a response ...
I use this link in the ACMEDNS_BASE_URL field: https://auth.acme-dns.io/update
How could the acme configuration be messed up? Actually, I have also tried doing a wipe of the whole configuration from...