Let's Encrypt certificate error on some multisite domains

Hello,

I have a domain.com and a domain.fr.
I have hosting on the .com, with a Let’s Encrypt certificate enabled. The site is OK and operational.
I recently transferred the domain.fr to OVV, thinking it would be simpler to manage everything in one place. Following OVV’s advice, I created a multisite on domain.com by adding domain.fr. The DNS for domain.fr are OK and point to the “correct” IP (of the hosting on .com).
The Let’s Encrypt generation for domain.fr has been “in creation” for 3 days and a task in progress is in error, but I have no details. I therefore cannot rectify the problem.
The multisite shows as green everywhere for all domains.
I am completely stuck. My traffic from .fr is lost because domain.fr is not secured with HTTPS. I cannot delete the certificate request either to start over.
I am blocked. I tried contacting the hotline again, but it hangs up on its own after a while.

HELP

Hello,
To check, he gives us the OVH ticket number or the domain in question :slight_smile:

Ticket #CS16260619
In the meantime, I managed to get in touch with someone from the hotline who said they will take the necessary steps internally.
Let's hope this time it works :folded_hands:

Hello @gomm.net

I confirm that this ticket has indeed been escalated internally because the generation of your certificate failed. The administrators will be able to fix this quickly; for now we need to wait for their response :wink:

Asterix

So, yes, the certificate was generated but on cluster100.hosting.ovh.net and not on my domain.fr.
Consequently, browsers don’t accept it at all. I don’t understand how to make the certificate be on the “right” domain.

Your two domain names point to the hosting on cluster100 and SSL is active for both domain names.

As is, all requests that will be made to the .fr and the .com, whether in HTTP or HTTPS, will be redirected to the URL you have chosen for the site URL in the WordPress admin panel: “Settings” > “General”

If needed, here is our documentation on this subject: https://docs.ovh.com/fr/hosting/passer-site-internet-https-ssl/#etape-3-activer-le-https-sur-votre-site_1

Astérix

Thank you but I don’t agree with your answer.
For domaine.com, the “raw” certificate correctly shows Common Name domaine.com
For domaine.fr, the “raw” certificate shows Common Name cluster100.hosting.ovh.net

It should be domaine.fr as the Common Name.

WordPress only accepts a single URL (the .com) and that works fine. In this case, my .htaccess already contains:

RewriteEngine on RewriteCond %{HTTP_HOST} ^(?:www\.)domaine\.fr$ [NC] RewriteRule ^https://domaine.com/ [L,R=301]

Another option is to add an additional redirect in the .htaccess but I don’t understand why :thinking:

And there is also this in .htaccess:
<IfModule mod_rewrite.c> RewriteEngine on RewriteCond %{HTTP_USER_AGENT} !lscache_runner [NC] RewriteCond %{HTTP:X-Forwarded-Proto} !https RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L] </IfModule>

Well, after another discussion with the hotline. The issue is resolved (probably a cache during certificate generation).
Very hard to get the hotline, but their response is always appropriate and this forum also replies quickly.
Topic to close

Hello @gomm.net

Take a look at some reading:

Here is a short guide I wrote that could give you clarification for a Complete and clean installation of your site.

Guide – Understanding the Domain → DNS Zone → Hosting → Site folder

See → CMS – WordPress – Installation Guide at OVH

Read and assess your situation by following carefully the paragraphs: A to J applicable to all CMSs

Feel free to give me feedback: positive or negative.
That’s how I fine‑tune my guide.
If my answer is the solution, feel free to click “Approve the solution”.

When your WordPress site is finished and operational, don’t forget to back it up on your PC.

________________________________________________________________________________________________

Backups of your site at OVH are not permanent.

Excerpt from my guide: [T - Restauration OVH de votre site à une date antérieure](https://wordetweb.com/word-et-web/WORDPRESS-guide-installation-de-WordPress-premier-domaine-chez-OVH-FR.htm#_T_–_Restauration “T - Restauration OVH de votre site à une date antérieure”)

At OVH, restoring your hosting can only go back at most two weeks.

If your site was hacked three weeks ago, you’re screwed and have to delete everything and completely rebuild your site.

At OVH, restoring your database can only go back at most two months

Remember to back up Hosting and Database on your PC once a month.
See the paragraph in my guide: Ua - Sauvegarde complète de votre site sur votre PC

See the paragraph in my guide: [Ub - Restauration complète de votre site depuis votre PC](https://wordetweb.com/word-et-web/WORDPRESS-guide-installation-de-WordPress-premier-domaine-chez-OVH-FR.htm#_W_-_PLUGINS “Ub - Restauration complète de votre site depuis votre PC”)