Search results

For my internal PVE nodes I want to get ACME working. Since I'm behind a NAT firewall and the single IP's port 80 is not available, I'm trying with the DNS API challenge. Unfortunately, my own web hoster does not provide a DNS API, so I forwarded a subdomain to 1984.hosting, which has a built-in...

Thanks for your reply, @Dominic ! Yes, I was aware of that. I just didn't know that leaving the original file in /etc/systemd/system would cause the disk still to appear in node -> Disks -> Directory. That's the first thing I did, expecting it to make the storage 'removable' on the node-level...

In my attempts to understand how Proxmox storage works in a cluster, I took a spare disk and tried to add it through the web GUI via node -> Disks -> Directory -> Create: Directory. I selected my spare disk but the only filesystems I could pick were either EXT4 or XFS. I went for EXT4. Now...

It's a conspiracy by the hardware manufacturers, I tell you! They're using Proxmox to get us to spend all our savings on hardware! :eek::cool:;)

You seem to be in somewhat the same boat as me, @danielo515. I too started out with a single simple Proxmox server (an old Dell Optiplex 7010 in my case) which I soon upgraded to 16GB ram and a consumer SSD. Worked pretty nice, until I got my hands on a second Optiplex 7010 and decided I wanted...

Documentation is incomplete, unfortunately. A bug has been filed about this, but it might be bigger than described here: https://forum.proxmox.com/threads/feedback-on-admin-guide-removing-node-from-cluster.87112/

Good point @frankz. I kind of have the same issue - after removing a node, all kinds of traces are left of this node across the cluster config: /etc/pve/nodes/[nodename] --> so apparently, we can safely delete this manually? /etc/pve/priv/known_hosts --> still contains entries from removed node...

@Dominic - A few weeks 'wiser' (and another unvoluntary removal of a node from the cluster later), I'm starting to wonder is this isn't actually a bug rather than just a missing piece of documentation? I'm asking because my latest encounter with the removal of a node happened with a node that...

Done - https://bugzilla.proxmox.com/show_bug.cgi?id=3375 :)

Thanks for your reply. And good point. I'd really like to prevent having to reinstall, since that caused a lot headaches the first time (i.e. a Sandybridge node causing the PVE installer to crash because of bugs in the Linux Intel graphics driver which will never be fixed). That's why I went...

I'm running into the same issue, but in my case I (think I) cannot use the solution mentioned by @ph0x since I only have a single SSD which contains everything (default Proxmox installation on single disk (RAID0) ZFS). So I cloned the disk using Clonezilla, which actually worked pretty well (as...

In the current version of the admin guide, the instructions on removing a node from a cluster (https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_remove_a_cluster_node) are missing a vital piece of info - existing replication jobs (and perhaps more, but at least this). If you fail to...

Well... My plan certainly is not going to work as I had in mind - the system does not boot from the new SSD after cloning. I've searched and read a lot of articles and posts on migrating PVE from one disk to another, but none seem to describe my specific situation: An existing full ZFS setup on...

Thanks for your reply. While I've been unable so far to find the same sizes / prices, I did find a reseller offering used Samsung SM863a's (480GB) drives for €100 a piece. Do you think that's a good price? And would I get away with 1 of those for each node (which would set me back €400 for 4...

Having started with Proxmox VE for my home / smb environment very enthusiastically on old consumer hardware (the clustering feature is AWESOME, (live) migrating VM's and containers is just pure MAGIC), I'm now forced to reconsider as (presumably) ZFS is killing my SSD(s). Current situation is a...

As per https://github.com/lxc/lxc/issues/1854 and specifically https://github.com/lxc/lxc/issues/1854#issuecomment-606241047 , I did the following in the container: sudo apt update && sudo apt dist-upgrade sudo apt install squashfuse fuse sudo apt install snapd sudo mkdir /lib/modules From...

Found it! Apparently, the network card was called "enp7s0" during installation. After first boot, the adapter suddenly became "enp6s0" but Proxmox was unaware of this and continued using "enp7s0". Which of course failed, since the card was no longer available under that name (so much for...

Never mind, I found an old PCI graphics card in my basement. After plugging it in I was able to start the Proxmox installation without issues. After that, pulled it back out and the system boots fine. Now to fix my next issue...

Just ran into this issue as well. r8169 works fine from an Ubuntu 20.04 live session, but when booting ProxMox, the link goes down (the light on my switch turns off as well). Rebooting into Ubuntu 20.04 - light goes back on, link is restored. But ProxMox just keeps knocking the card back down...

Trying to install Proxmox VE 6.3 on my good 'ol i5-2500 (Sandy Bridge) machine. Thing is, the built-in graphics have been badly supported by the Linux kernel since the dawn of time, causing the installer to freeze since it's trying to run in 'full' graphics mode. This is not ProxMox' fault, I...