Search results

  1. J

    Problems with linode_v4 and ACME DNS plugin

    Really glad I wrote that up since I did end up reinstalling proxmox again. But I ran into more problems. First, make sure you login as root. ACME configurations don't seem to be available to any other user. Not sure if there is a permission you can add for that, but my regular user who had the...
  2. J

    Problems with linode_v4 and ACME DNS plugin

    I was struggling with this, too, but I think I have a working solution. Open the web gui Select datacenter from the side bar Select that ACME tab Add your Let's Encrypt account Enter letsencrypt for the account name Enter your email Use Let's Encrypt V2 for the directory Check Accept TOS...
  3. J

    api key

    I used LINODE_V4_API_KEY=<API_KEY> without quotes and it worked for me. No spaces anywhere else. No blank line before the export. A single newline at the end. It seems to be extremely picky on what works.
  4. J

    virtio network cards don't work with ssh

    Yes, changing to the Chelsio network cards fixed the issue. There seems to be a problem with the Q-Logic (formerly Brocade) BR1860 adapter and virtio drivers.
  5. J

    virtio network cards don't work with ssh

    Thanks for the suggestion, but the kernel downgrade did not make any difference.
  6. J

    virtio network cards don't work with ssh

    I've been doing some testing. I have a couple other proxmox hosts that aren't part of this cluster. I have no issues using virtio and ssh with them. I was trying to look for differences between the installs. I noticed that the working proxmox hosts were on 5.3, while the non-working ones are on...
  7. J

    virtio network cards don't work with ssh

    I'm setting up a new proxmox cluster. If I use the virtio network card, I cannot ssh into the virtual machines. If I switch to e1000, it works. By not working, I mean the ssh connection just hangs. It never shows a login prompt. I see packets traveling back and forth, but it never completes the...
  8. J

    ssh_known_hosts readability

    Yeah, I know I only have to accept the key once, but the /etc/ssh/ssh_known_hosts files should be globally readable so that all users can benefit. Without that, every user needs to verify the signature of every server individually, which is a difficult process. Just accepting the key is a...
  9. J

    ssh_known_hosts readability

    I want to login to a server as a non-root user, and be able to ssh into another server in the cluster without it asking whether the key is okay.
  10. J

    ssh_known_hosts readability

    The ssh_known_hosts file in the proxmox cluster is stored in the /etc/pve/priv directory, which is not world readable. This means I can't use it with my normal users. Is there a reason why this couldn't be somewhere else in /etc/pve that would be world readable? Thanks.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!