VirtualHost configuration:
*:443 is a NameVirtualHost
default server dr0.ch (/etc/httpd/conf.d/dr0-le-ssl.conf:2)
port 443 namevhost dr0.ch (/etc/httpd/conf.d/dr0-le-ssl.conf:2)
port 443 namevhost jargon.dr0.ch (/etc/httpd/conf.d/jargon-le-ssl.conf:2)
port 443 namevhost photos.dr0.ch (/etc/httpd/conf.d/photos-le-ssl.conf:2)
*:80 is a NameVirtualHost
default server dr0.ch (/etc/httpd/conf.d/dr0.conf:1)
port 80 namevhost dr0.ch (/etc/httpd/conf.d/dr0.conf:1)
port 80 namevhost jargon.dr0.ch (/etc/httpd/conf.d/jargon.conf:1)
port 80 namevhost photos.dr0.ch (/etc/httpd/conf.d/photos.conf:1)
I am lost. Where is the self-signed cert coming from? Because the only cert I see in your ssl.conf is the one from Let's Encrypt. That is not a self-signed cert and has the below domain names in it. Nothing to do with that vps-65ee61ee.vps.ovh.net I see when connecting to your domain on port 80.
Still, you should not see any cert when using port 80. Port 80 is for HTTP. Certs are used for HTTPS.
You need to trace the path of the incoming HTTP request through every component. Find out why when it reaches Apache that it gets treated like an HTTPS request
You might also try commenting out these lines from the ssl.conf file. They are in each VirtualHost so are just duplicates.
SSLEngine on
SSLCertificateFile /etc/letsencrypt/live/dr0.ch-0001/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/dr0.ch-0001/privkey.pem
Maybe by forcing SSLEngine On in your base conf it is forcing HTTPS for all incoming. I'm not sure and don't want to chase Apache docs. In any case, they are redundant. You may need to consult an Apache forum or your hosting site if that doesn't work.