You do realise the certificate you're requesting a certificate for has 22 FQDN's in it? At least that's what the certificate from
server.sio4.org is giving me:
certbot tries to renew all those FQDN's.. So there's no such thing as a single "my Letsencrypt Virtualhost", unless you've got all those FQDN's as a ServerAlias in that single
Anyway, back to your "VirtualHost".. I don't see a
<VirtualHost> section.. Could it be that's because the forum stripped those things, thinking it's HTML? Or did you just not include it yourself? Because now I don't know if I'm looking at the HTTP VirtualHost, the HTTPS VirtualHost with a lot of things missing.. No clue.. Could be anything.
Also, you said the following: "Here my DocumentRoot https for the FQDN". Which FQDN? Like I said, there are 22 in your certificate! There's no such thing as the FQDN, unless you specify which FQDN you meant. For more information about the definition of a FQDN, see https://en.wikipedia.org/wiki/Fully_qualified_domain_name
What I'm seeing mostly here is, no offence, serious lack of understanding of how a webserver (in this case Apache) actually works, what the different directives actually do. You're pasting a piece of configuration file with an
Alias directive in it. Have you read the Apache documentation about the
Alias directive? It also has a
RedirectMatch directive. You should read what that does too.
Also, you say you removed all the
DocumentRoot directives. I hope you commented them, not delete them. Making permanent changes you don't actually know the ramifications of is unwise. A comment you can remove. Remembering what you deleted is a lot harder.
The page you're refering to called "RedirectSSL" has a
Redirect directive in place. I'm not seeing such a directive in any of your configuration pieces you posted in this thread. (Spoiler, the
RedirectMatch isn't actually redirecting anything.) So I have no idea if that was wise, possible or very unwise. I'm lacking that information.
Best thing for you to do is:
a) Read. Read alot. Read alot about managing a webserver in Apache;
b) Place all of your Apache configuration files on something like http://pastebin.com/ and post the links here.
c) Post the contents of /etc/letsencrypt/renewal/server.sio4.org.conf in this thread.
Perhaps then it's possible to sort things out.