I am currently running a nextcloud for my personal use - its the ubuntu appliance version I got from techandme some time back.
I am very green to linux - actually my ‘skill’ is blindly copying and pasting commands and hoping they are doing what I want.
How I’m currently setup:
My Fritz router handles the DNS registration https://update.dedyn.io/ for my domain dlmw.dedyn.io
When I fumbled around getting certificates installed for https, I just ran the certbot commands on the nextcloud server. All works just fine
but…the nextcloud server is effectively hosting the dlmw.dedyn.io domain, which I don’t think is correct (feel free to disagree). Indeed, when I configure the clients, they point to dlmw.dedyn.io
I’m thinking that it should be using a certificate such as nextcloud.dlmw.dedyn.io instead.
Reason being, I am planning to have a play with nginix on a separate VM, and I assume if I go certbot, it’ll get issues trying to have the same domain.
I think I should have nextcloud.dlmw.dedyn.io and nginx.dlmw.dedyn.io, for example.
Am I correct in this, or am I looking at it incorrectly?
If I am correct, then I need help for two things…
- how to de-certify/deregister the existing certificate on the nextcloud server
- how to re-configure it to go get the new certificate
My domain is: dlmw.dedyn.io
I ran this command: N/A
It produced this output: N/A
My web server is (include version): Server version: Apache/2.4.29 (Ubuntu)
The operating system my web server runs on is (include version): Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
My hosting provider, if applicable, is: N/A
I can login to a root shell on my machine (yes or no, or I don’t know): yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): No
The version of my client is (e.g. output of certbot --version
or certbot-auto --version
if you’re using Certbot): certbot 0.28.0