GUI for what? Shouldnt be any configuration needed.
This is how I did it on four nodes:
https://blog.k0nsl.org/2016/09/01/lets-encrypt-tls-ssl-for-proxmox-ve/
Best wishes,
-k0nsl
please don't post wrong information on the internet there is a documented way to get Proxmox to use third party certificates for the web interface, including ones issued by Let's Encrypt: https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)
just replacing the self-signed certificates creates problems - for example, adding new nodes and spice are broken.
pve-manager/4.1-5
0 0 * * * "/root/.acme.sh"/acme.sh --cron --home "/root/.acme.sh" > /dev/null
0 0 * * * /root/.acme.sh/acme.sh --cron --home /root/.acme.sh > /dev/null
Hi,I've successfully followed the instructions and am happily using my letsencrypt certificate but I have a few questions left:
- how come authentication via port 80 worked? I am not blocking it but neither was I aware there was anything running as proxmox is running on port 8006 so how does this work?
- can someone look at the cron job given in the wiki? That looks very dodgy to me, feels like a few too many "s are in there. Original:works for me:Code:0 0 * * * "/root/.acme.sh"/acme.sh --cron --home "/root/.acme.sh" > /dev/null
Code:0 0 * * * /root/.acme.sh/acme.sh --cron --home /root/.acme.sh > /dev/null
I've successfully followed the instructions and am happily using my letsencrypt certificate but I have a few questions left:
- how come authentication via port 80 worked? I am not blocking it but neither was I aware there was anything running as proxmox is running on port 8006 so how does this work?
- can someone look at the cron job given in the wiki? That looks very dodgy to me, feels like a few too many "s are in there. Original:works for me:Code:0 0 * * * "/root/.acme.sh"/acme.sh --cron --home "/root/.acme.sh" > /dev/null
Code:0 0 * * * /root/.acme.sh/acme.sh --cron --home /root/.acme.sh > /dev/null
It's a good idea to test the cron entry by running it manually from the command line to check that it's working OK:
"/root/.acme.sh"/acme.sh --cron --home "/root/.acme.sh"
thanks @fabian, the point is that beneath that, it said to test and that didn't work so I changed my cronjob. Does this work for you?
Code:It's a good idea to test the cron entry by running it manually from the command line to check that it's working OK: "/root/.acme.sh"/acme.sh --cron --home "/root/.acme.sh"
/root/.acme.sh"/acme.sh --cron --home "/root/.acme.sh
@fabian : sorry, the mistake was sitting in front of the PC this time :-(
I assumed the outer "" were part of the quote so I tried:
I just realized it actually works exactly as suggested in the wiki.Code:/root/.acme.sh"/acme.sh --cron --home "/root/.acme.sh
Sorry for the fuss, just wanted to make sure the wiki is correct.
Does anyone know who to resolve this?[Tue Feb 21 00:06:40 EST 2017] Standalone mode.
[Tue Feb 21 00:06:40 EST 2017] LISTEN 0 128 :::80 :::* users("apache2",pid=13662,fd=4),("apache2",pid=13661,fd=4),("apache2",pid=1240,fd=4))
[Tue Feb 21 00:06:40 EST 2017] tcp port 80 is already used by 80
[Tue Feb 21 00:06:40 EST 2017] Please stop it first
[Tue Feb 21 00:06:40 EST 2017] _on_before_issue.
Hi,I have followed the steps in the guide (https://pve.proxmox.com/wiki/HTTPS_Certificate_Configuration_(Version_4.x_and_newer)#Prerequisites) I have gotten to step 5. where it say to exicute acme.sh --issue --standalone --keypath /etc/pve/local/pveproxy-ssl.key --fullchainpath /etc/pve/local/pveproxy-ssl.pem --reloadcmd "systemctl restart pveproxy" -d $DOMAIN and it says
Does anyone know who to resolve this?
ss -patn | grep 80