Search results

Perhaps someone from Proxmox can provide confirmation that this is correct. Changing the host name is causing some problems. I would not recommend to change the host name, especially when VMs are added. Changing the host name needs to change some parts of the file structure where the hostname...

it seems thats an old problem https://forum.proxmox.com/threads/pve-cluster-startet-nicht-mehr.82083/

I moved the server to the new rack with another IP started the server with the old /etc/hosts Proxmox was starting the vms The proxmox interface was not accessible restating the server does not change anythin at this state as I did the experienxe of the deleted /etc/pve/ directory i did a rsync...

Maybe it not a bug, but It does not make sense, installing with pve-no-subscription from the console and pve throws the error with the first apt update. It is a strange behavior an maybe it will cause newbies to search a long time.

it seems that there is any kind of bug in the bullseye pve-non subsription installtation. The installation added a /etc/apt/sources.list.d/pve-enterprise.list file. After that an apt update is throwing an error [...] https://enterprise.proxmox.com/debian/pve/dists/bullseye/InRelease 401...

it seems that there is any kind of bug ind the bullseye pve-non subsription installtation. the installation added a /etc/apt/sources.list.d/pve-enterprise.list file. After that an apt update ist throwing an error [...] https://enterprise.proxmox.com/debian/pve/dists/bullseye/InRelease 401...

The pve-no-subscription was working during the installtion. The enterprice sourse list was installed with the installtion of the pve-non subsription system It is working with deleting the enterprise source list. and - it is only a root user available So it is not a changing hostname problem

I did a complete new installation with debian bullseye and proxmox /etc/apt/sources.list.d/pve-install-repo.list with deb [arch=amd64] http://download.proxmox.com/debian/pve bullseye pve-no-subscription and the issue of apt update: E: Failed to fetch...

I did a complete new installation with debian bullseye and proxmox /etc/apt/sources.list.d/pve-install-repo.list with deb [arch=amd64] http://download.proxmox.com/debian/pve bullseye pve-no-subscription and the issue of apt update: E: Failed to fetch...

but why was i am running in the enterprise files with the pve-no-subscription in the source list when starting apt update?

I will try it again, the server is empty - an will report here Teh folder was complete empty ...

What will happen if the server has a subscription and yo will end the subscription option: Does the server will work after that? The question comes up, because there was pve-no-subscription at /etc/apt/sources.list After changing the hostname and rebooting there was an error message at apt...

The old server is partially broken - i must remvove it. The question is why are the files in /etc/pve lost after changing the hostname An why is the system unstable after changing the hostname at the console ?

I will have two server completely installed with proxmox all vms and ssh The old one and the new one (like a mirror) The new server must replace the old server completely including the physical rack Therefore the new server will change the IPs in that moment when it will move to the original...

It seems to be a problem to change the hostname after installing Proxmox. I did a fresh Debian bullseye installation added Proxmox deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription Proxmox was working, i canged the hostname and after reboot, there the ssh key were not...

Debian Buster- Proxmox 6.3-6 Ich habe mehrere LXC Container laufen. Auf alle kann ich per SSH über die IPV6 Adresse zugreifen. Bei einem Container ist die Route nach einem Neustart weg: Ich kann per ssh ipv6 nicht mehr zugreifen: ip -6 route ::1 dev lo proto kernel metric 256 pref medium...

Update: Aus irgendeinem Grund übernimmt die VM die Host einstellungen nicht, obwohl bei Proxmox:VM:DNS Domain und proxmox:VM:DNS server "use host settings" eingetragen ist bei hetzner funktioniert (derzeit): proxmox:VM:DNS Domain: hydrogen.ns.hetzner.com oxygen.ns.hetzner.com...

Update auch wenn der ping6 zum host nicht funktioniert sind die VMs zu erreichen, auch wenn keine IPV4 Adresse vergeben ist. Aber, wenn keine IPV4 Adresse vergeben ist, funktioniert z.B ein ping6 google.de nicht. ping6 2a00:1450:4001:82a::2003 funktioniert Was müsste ich noch ändern, wenn ich...

Ich habe das um genau 4:00 nachts und suche da auch schon lange ... Das selbe habe ich auch auf den CT und auch auf zwei CT die nur über VPN zu erreichen sind. Deshalb vermute ich dass es von Proxmox kommen müsste, denn auf die VPN CT kommt niemand von außen drauf (außer dem proxmox host)

schau mal bei diesem Tread die (routed) IPV4 Konfiguration (Hetzner/Proxmox) funktioniert: https://forum.proxmox.com/threads/routing-ipv6-zu-von-vm.102928/ Den Fehler bei IPV6 hoffe ich noch zu lösen.