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.
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
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
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”
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
Read and assess your situation by following carefully the paragraphs: A to Japplicable 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”.