Recent content by etron770

Since I didn't want to buy any new expensive IPv4 addresses, or might not be able to get any at some point, I did configure... Regardless of the strange /etc/network/interfaces file, which I simply cleaned up manually without knowing where these entries came from. I implemented the following...

It cannot be a coincidence that /etc/network/interfaces now shows network connections that no longer exist. I changed the network structure and reconfigured several network devices via the GUI. All Vserver (Debian 12) have these strange entries that originate from deleted network connections.

At the proxmox host auto vmbr111 iface vmbr111 inet static address 10.8.1.1 netmask 255.255.255.0 bridge-ports none bridge-stp off bridge-fd 0

This is a test server and I don't know how to reproduce these entries being created in the interfaces file. What I did last in Proxmox: Deleted the interface with 10.8.1.xx. Deleted the interface with 2222:333:444:555::113 and reinserted it. The fact is that this is now the second time In...

It is not the routing on the root server but the entries from Proxmox in the container. erver1] ~ # ip route default via x.y.z.18 dev eth0 10.8.0.254 dev eth1 scope link x.y.z.18 dev eth0 scope link [server1] ~ # ip route default via 10.8.1.1 dev eth111 10.8.1.0/24 dev eth111 proto kernel scope...

It looks like Proxmox has a bug in its network configuration. Reproduction of the error: 1. Insert a public IPv4/IPV4 network into a VM. 2. Add an internal IPv4 network, e.g., 10.8.0.1. Proxmox then sets the default route to the internal network I don't know exactly how it happened. Either I...

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...