[SOLVED] - Fehler Aktivierung - 惯性聚合

推荐订阅源

DataBreaches.Net

Fortinet All Blogs

阮一峰的网络日志

博客园_首页

Apple Machine Learning Research

Help Net Security

MIT News - Artificial intelligence

美团技术团队

人人都是产品经理

freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More

Cyber Security Advisories - MS-ISAC

The Cloudflare Blog

有赞技术团队

博客园 - Franky

钛媒体：引领未来商业与生活新知

博客园 - 【当耐特】

SegmentFault 最新的问题

Visual Studio Blog

Blog — PlanetScale

Hugging Face - Blog

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice

[SOLVED] - Fehler Aktivierung

invalid@exam · 2026-06-02 · via Proxmox Support Forum

#1

Hallo zusammen,
ein Node möchte keine Subscription mehr annehmen. Fehlermeldung lautet: "Error checking subscription: io: No route to host (os error 113) (500)". Er hat aber - wie alle anderen - auch ganz normal Internetzugriff.
Weiß jemand wie ich den Fehler eingrenzen könnte?

Gruß Daniel

#2

Prüfe mal

Bash:

nslookup shop.proxmox.com
ping shop.proxmox.com
traceroute shop.proxmox.com

#3

Hallo Impact,

danke. Jetzt habe ich zumindest den Fehler. Im Gegensatz zu den anderen möchte dieser Node shop.proxmox.com via IPv6 erreichen, obwohl er ebenso die IPv4-Adresse aufgelöst bekommt. Jetzt suche ich mal weiter.

此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。原文来自 — 版权归原作者所有。