I've now removed all 4 .htaccess files, restarted apache2 after each one but the error persists.
I'm off for today.
Thank you very much for your effort, I will be following any further tips tomorrow.
Have a nice evening/weekend.
Okay. I am starting to think that Apache config you are showing is not the Apache that is actually replying. Do you have multiple Apache servers running? Is your public IP correct.
We can check your Apache access logs to make sure it shows the 404.
By the way, the HTTP request for your cumulus "home" page does not mention NextCloud. I don't know that it would be you said it should be the NextCloud landing page so I thought it would. You might try using HTTP to that domain from outside your local network (like a phone w/wifi off) and see if that's what you expect.
Good morning,
you are my hero!
As it is so often, I only saw the problems I may have created during the editing of the conf files in the last weeks while trying to solve obvious problems in the nextcloud configuration.
There is indeed another http-server in the network which needed port 80 during the initial setup (and for which there's a port forwarding to use 81 externally) but the initial forwarding was never disabled and now lead to the renewal problem.
Alas, I have learned some things about mod_md and how Letsencrypt works.
Thank you very much and have a nice Sunday.
Excellent. That explains a lot.
Still, the domain names in your certs don't align very well with your VirtualHost setup. That can easily lead to problems in the future.
mod_md would sort that out as you define the cert domain names in the Apache config alongside your VHost config. But, with Certbot sometimes more care is needed when reorganizing VHosts and domain names.
If you plan to stay with Certbot we should get your certs in better alignment with your config. For small setups some people prefer one cert with all the domain names in it. I prefer having a cert for each separate VHost for just the domain name(s) in that VHost. It makes it easier to add and remove VHosts in the future. Right now you have several certs with different name overlaps between them.
Let us know if you need help with that.
Your Certbot 2.9 could also benefit from updating to the latest 5.x. You would add major features like ARI and Profile support. Ubuntu easily supports the "snap" install for Certbot which would keep it updated automatically. See: Certbot Instructions
As often, the problem sits in front of the screen...
Have already streamlined the vhosts now.
I will think about mod_md but will probably not touch this until I have at least a few days without daytime work...
I keep my system up to date using apt but was not aware that certbot stopped using it.
Have upgraded using this documentation: