Search results

  1. D

    2node Proxmox with identically configured firewall unable to connect to 8006 on one node.

    I am at a loss trying to figure out how this is not working as expected. 2 basic servers where I have firewall open for 3 public IPs to be Allowed to connect to 8006, and same for 22. No other entries. I can successfully connect only to node2 from 1 IP. I can connect to either node from the...
  2. D

    Logical Volume not found after reboot.

    Hello, I have 2 colocated servers. Both have 2 Intel 2TB SSDs in RAID-1 and 2 WD Black NVMEs in RAID-1 (some other spinning drives) I installed the latest Proxmox 8.0.3 yesterday linked both servers and processed to test some of the Proxmov features (ie. migrating between nodes... etc..) Was...
  3. D

    [TUTORIAL] Using IPv6 on SYS (probably similar on OVH)

    IPv6 issued to me by SYS XXXX:XXXX:XX:XX6e::/64 (X's are redacted for privacy) I am using Windows 10 as a testbed running in Proxmox 7.1-8 For IPv6 config: Address: XXXX:XXXX:XX:XX6e:0000:0000:0000:1000 (you can change any of the 0's in the last 4 blocks, I used 1000) Prefix: 64 GW...
  4. D

    [SOLVED] No Repositories option under Updates

    Upgraded from the latest 6 (can't remember the exact revision but I kept it updated) to 7.1-8. There is no dropdown in Updates to see the Repositories menu. Had to manually edit out the Enterprise option. So just throwing this out there in case it's a bug...
  5. D

    Private IP server for just Quorum?

    Hi, This is just my learning and testing playground. HA is not needed... just basic testing VMs. I have 2 servers already in a Cluster with public IPs. They work without any problems. Just ran into an issue when upgrading one of these it came offline and I couldn't do much because I had no 3rd...
  6. D

    Unable to open Shell : Connection failed (Error 500: Timeout while waiting for port '5900' to get ready!)

    I haven't had any issues with this previously and it seems like this started after applying last updates. (Especially since I was able to apply them previously without any problems.) Now any time I try to open shell to either of my 2 nodes this comes up. Mar 12 08:58:50 node1 pvedaemon[7683]...