Difference between revisions of "SSL - ESXi"
Jump to navigation
Jump to search
m (removed an "either" from the sentence as there is only one in this instance) |
|||
| Line 5: | Line 5: | ||
*The file you're replacing <code>rui.crt</code> with is either <code>cert.pem</code> or <code>fullchain.pem</code> (depending on whether you've set up with one or more than one domain in your certs. | *The file you're replacing <code>rui.crt</code> with is either <code>cert.pem</code> or <code>fullchain.pem</code> (depending on whether you've set up with one or more than one domain in your certs. | ||
| − | *The file you're replacing <code>rui.key</code> with is | + | *The file you're replacing <code>rui.key</code> with is <code>privkey.pem</code>. |
*Both of the files from certbot may have a number attached to the end of the filename itself. | *Both of the files from certbot may have a number attached to the end of the filename itself. | ||
| Line 21: | Line 21: | ||
*<code>reboot</code> | *<code>reboot</code> | ||
| − | == Using SCP to install the certs == | + | ==Using SCP to install the certs== |
You should be able directly install certs on your ESXi server thanks to vmWares bad habit of allowing SSH as root... | You should be able directly install certs on your ESXi server thanks to vmWares bad habit of allowing SSH as root... | ||
| Line 28: | Line 28: | ||
'''You have been warned.''' | '''You have been warned.''' | ||
| − | * <code>scp /etc/letsencrypt/live/NAME.DOMAIN.TLD/fullchain.pem root@NAME.DOMAIN.TLD:/etc/vmware/ssl/rui.crt</code> | + | *<code>scp /etc/letsencrypt/live/NAME.DOMAIN.TLD/fullchain.pem root@NAME.DOMAIN.TLD:/etc/vmware/ssl/rui.crt</code> |
| − | * <code>scp /etc/letsencrypt/live/NAME.DOMAIN.TLD/privkey.pem root@NAME.DOMAIN.TLD:/etc/vmware/ssl/rui.key</code> | + | *<code>scp /etc/letsencrypt/live/NAME.DOMAIN.TLD/privkey.pem root@NAME.DOMAIN.TLD:/etc/vmware/ssl/rui.key</code> |
| − | * <code>ssh root@NAME.DOMAIN.TLD reboot</code> | + | *<code>ssh root@NAME.DOMAIN.TLD reboot</code> |
Of course, you'll replace '''NAME.DOMAIN.TLD''' with the actual name of your server... | Of course, you'll replace '''NAME.DOMAIN.TLD''' with the actual name of your server... | ||
Revision as of 05:13, 2 July 2020
Installing manual certs on an ESXi server
PIKEDOM.COM has some very good instructions.
Something to know if you got your certs from certbot:
- The file you're replacing
rui.crtwith is eithercert.pemorfullchain.pem(depending on whether you've set up with one or more than one domain in your certs. - The file you're replacing
rui.keywith isprivkey.pem. - Both of the files from certbot may have a number attached to the end of the filename itself.
So...
SSH into the server...
cd /etc/vmware/sslmv rui.crt orig.rui.crtmv rui.key orig.rui.keyvi rui.crt- Paste in the content of
fullchain.pem
- Paste in the content of
vi rui.key- Paste in the content of
privkey.pem
- Paste in the content of
reboot
Using SCP to install the certs
You should be able directly install certs on your ESXi server thanks to vmWares bad habit of allowing SSH as root...
THIS HAS NOT YET BEEN FULLY TESTED!
You have been warned.
scp /etc/letsencrypt/live/NAME.DOMAIN.TLD/fullchain.pem root@NAME.DOMAIN.TLD:/etc/vmware/ssl/rui.crtscp /etc/letsencrypt/live/NAME.DOMAIN.TLD/privkey.pem root@NAME.DOMAIN.TLD:/etc/vmware/ssl/rui.keyssh root@NAME.DOMAIN.TLD reboot
Of course, you'll replace NAME.DOMAIN.TLD with the actual name of your server...
