UPDATE - after more testing, I narrowed it down to wget defaulting and failing while using IPv6 - if I force IPv4 - it works !!!
Used this command:
wget --inet4-only https://github.com/tteck/Proxmox/raw/main/turnkey/turnkey.sh
so something strange about IPv6 from this particular node's console...
Funny enough - I have a PiHole running as a LXC container on said node and I can use the wget command just fine to fetch the script - just not from the node console ?!? :confused:
Thx for the suggestions - here's what I checked:
Pinging with IPs and names works fine . . .
Networking config on all nodes appears to be correct . . .
Switches checked - all OK, and YES - using VLANs and LACP for quite some time without issue . . .
Firewall live view shows nothing strange when...
OK - so it appears to be something with the wget command not being able to fetch the script ?!? Hangs during the connection - here's the output from both examples - the broken node (R86s) and a working one (awowfox)
So it would appear to be a networking issue of sorts . . . will investigate...
Thanks for your prompt reply - The exact same command line works on 4 out of 5 Proxmox nodes - so it's not the scripts themselves, it's something with the bash execution on this particular machine ?!?
Take this one for example:
bash -c "$(wget -qLO -...
I have a small cluster of 5 mixed machines - one of which is running a virtual OPNSense as firewall. Everything is running fine, but recently I noticed a strange issue which I can't find what's causing it . . .
When running a script from Proxmox Helper Scripts...
Turns out, after many tests - my main machine which I use to access Proxmox was in the wrong VLAN segment - so this issue only affected ONE machine and Proxmox seems fine - So my bad for jumping to conclusions something was wrong with the servers Thanks again and have a great day!
Thanks Luckyj for your response - YES, I have multiple IPs assigned to different VLAN segments (see attachment) and that has worked fine since over 14 months - not the issue. Turns out, after many tests - my main machine which I use to access was in the wrong VLAN segment - so this issue only...
Greets and Happy belated New Year! I just started having problems with a 4 node cluster running different machines - running latest Proxmox VE version - NEVER had console or terminal issue until just recently (only added a new switch to the network) - now when I open a console from the Proxmox...
I just tested on the same network a stand alone Promox node - and it works without issue (running htop or btop constantly in window) - when I do this with any node in my cluster - the console freezes / hangs - This was not happening in the past ?!?
Greets and Happy belated New Year! I just started having problems with a 4 node cluster running different machines - NEVER had console or terminal issue until just recently (only added a new switch to the network) - now when I open a console from the Proxmox GUI - or start a console with VNC or...
Greets and Happy belated New Year! I just started having problems with a 4 node cluster running different machines - NEVER had console or terminal issue until just recently (only added a new switch to the network) - now when I open a console from the Proxmox GUI - or start a console with VNC or...
Looks like I may have a similar problem - using R86s with 3xi225-LM and 2x10GB Mellanox - running latest Proxmox and OPNSense as VM - OPNSense serving up IPs through DHCP - having issues between VLANs and DHCP broadcast :-( Been racking my brain trying to figure out why certain devices can get a...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.