Recent content by G0ldmember

Hey @fabian yeah maybe I messed something up while copy ' n pasting. If that's the case sorry for that. Now it seems to work, CDN now returns de3. Thank you

Another comment: The file coming from the ::249 node seems to be okay. The file coming from the ::167 node is corrupted: /tmp$ dpkg -x ceph-mgr_19.2.6-pve4_amd64.deb ddd/ dpkg-deb: Fehler: »ceph-mgr_19.2.6-pve4_amd64.deb« ist kein Archiv im Debian-Format

I think some of the CDN nodes are still delivering a (corrupted?) file with the same size but a wrong (or at least a different) hash. The file that @fabian mentioned coming from...

Now it's a different CDN node :) ➜ /tmp wget http://\[2a01:7e0:0:424::249\]/debian/ceph-squid/dists/trixie/no-subscription/binary-amd64/ceph-mgr_19.2.6-pve4_amd64.deb --2026-09-10 16:32:26--...

In the Packages file there's Filename: dists/trixie/no-subscription/binary-amd64/ceph-mgr_19.2.6-pve4_amd64.deb Size: 1233888 MD5sum: 5d870e8aebfdaac08865f5be41dfb0fd SHA256: e9926085a2db087f920b49116e5b6a57766c12383f433ea2e8cfdb864d3c937a SHA512...

Problem still persists:

Hi, it's download.proxmox.com is an alias for download.cdn.proxmox.com. download.cdn.proxmox.com is an alias for de.eu.cdn.proxmox.com. de.eu.cdn.proxmox.com is an alias for de.cdn.proxmox.com. de.cdn.proxmox.com has address 212.224.123.70 de.cdn.proxmox.com has IPv6 address 2a01:7e0:0:424::249

Hi, since yesterday we have a hash sum mismatch in the no-subscription repo that we use for testing before we update the prod servers with enterprise subscription. Example: Fehler: Fehlschlag beim Holen von...

Well this is just a workaround/addon in my opinion to make a insecure protocol more secure. Still SMB wasn't designed to exchange data over the internet, there are better ways to do that. From my experience, even SMB over VPN doesn't really work very smoothly so I don't use it. But that's just...

@mainjj67 there is a good reason why the Fritz!Box is blocking that by default ;) I wouldn't use SMB over internet. It's not only insecure (even if there is the "seal" option), it's also slow and not reliable for non-local networks IMHO.

It's always a bad idea to store credentials or keys in the filesystem or in a versioning system like git oder subversion. If you're using ansible, you should put it in ansible vault.

Right it's just for testing and we wanted to have the same repo with the same packages so it's reproducible 1:1 on the live environment. But buying 4x a 2 socket subscription just for that test system doesn't make sense for us so we'll fall back to the no-subscription repo for the test-system.

Hm okay, then the subscription info is actually wrong, it should not say "per physical CPU socket" but "per CPU socket and per server" and it doesn't matter if it's physical or not.

Hi, that's clear, we have 4x 1-core subscriptions and 1x 2 core. The question was just as we have 1 physical node with 2 physical sockets would we really need to purchase 4x 2-core subscriptions for this (one for the proxmox instance itself and one for each nested test-node which is...

Hi, we have a Proxmox Setup as follows: 1 3-node-cluster with 1 physical CPU each node 1 test machine with 2 physical CPU sockets running 3 paravirtualized nodes for testing 1 standalone node with 1 physical CPU socket So in total, we have 6 CPU sockets. As the subscription says: "The...