Nethserver backup issues

Support
22

@steve

LE: It still can be done - working for BOTH servers!

  1. On your Nethserver, use a named based virtual host for the second server, pointing that name to the IP of the second server.
  2. Set the virtual host on NethServer to handle all SSL for the second server.
  3. Use that defined alias, eg owncloud.domainname.tld as an Alias in NethServer’s LetsEncrypt configuration.

The toughest bit: moving the SSL certs to server 2!

Enable root ssh access (trustedhosts !) from your nethserver to your second server.
Using something like this script (started everytime NethServer updates it’s LE cert!). Adapt paths and targets as needed.

(Taken from here: Howto install NethServer as Samba AD domain controller v0.2, use search for the exact point!)

touch /etc/e-smith/events/certificate-update/nsdc-cert
nano/etc/e-smith/events/certificate-update/nsdc-cert

and copy the following (adapted!) contents to the newly created file:

#!/bin/bash
cp -f /etc/pki/tls/private/localhost.key /var/lib/machines/nsdc/var/lib/samba/private/tls/key.pem
cp -f /etc/pki/tls/certs/localhost.crt /var/lib/machines/nsdc/var/lib/samba/private/tls/cert.pem
chmod 600 /var/lib/machines/nsdc/var/lib/samba/private/tls/key.pem
chmod 644 /var/lib/machines/nsdc/var/lib/samba/private/tls/cert.pem

This should do:
Copy over both relevant certs to your second server (owncloud)
Restart the relevant apache services on the owncloud server.

This should work!
I use this to allow my AD to have a correct LE cert, as certain AD enabled Apps (In my case a JAVA one) needed a valid SSL cert on the AD itself!

My 2 cents
Andy

1 Like