certificate

  1. H

    What's wrong about replacing /etc/pve/local/pve-ssl.* ?

    man pveproxy says this: Warning Do not replace the automatically generated node certificate files in /etc/pve/local/pve-ssl.pem and etc/pve/local/pve-ssl.key What's so wrong about replacing original snakeoil key+cert with eg. letsencrypt one? It seemed to work for me. I modified my...
  2. B

    Cluster - SSL3 - certificate verfiy failed

    Hallo liebe Community! Ich habe heute versucht ein Cluster aufzusetzen (Sparate Network Cluster) und stehe grade vor einer kleinen (hoffentlich) Hürde. Kurz vorab: Ich sehe auf beiden Server die Nodes aber auf jedem Node ist nur der eigene Online. BeispieL. Node 1 : one Node 2 : two Auf Node...
  3. F

    Strange issues with the web interface

    Hello, I just started using Proxmox and I have a very strange situation here. My setup I cannot post what could look like a link as I am a new member. Sorry if it is hard to read. I have 2 nodes behind a router, on which I do some port forwarding, to access them from outside using my own...
  4. E

    I can not open the web interface

    I was trying to install a COMODO SSL certificate specifically a wildcard, during one of the attempts I lost access the graphical interface, now even I achievement not install the certificate nor I have access via graphical interface. Someone could help me with this? root@rhodes:~# dpkg -l...
  5. G

    [SOLVED] Fresh VM do not start (pve certificate error)

    Hi, I created a new virtual machine (myvm1.mydomain.com) on a new physical proxmox 4 host (myhost.mydomain.com). As I have a wildcard certificate for my domain (*.mydomain.com), I replaced /etc/pve/local/pve-ssl.pem with my wildcard certificate. I then tried to start a VM and got this error...
  6. P

    Chrome "No data received" when trying to open the proxmox 4.1 web management portal

    Hi all, I was wondering if there is any fix for this issue. From what i read on the internet this has something to do with the proxmox webserver not supporting the new TLS protocols thus generating this error. However, this is not specific to chrome since it is also happening with firefox...