I am having an issue where the padlock in the browser does not appear. This is because the domain name on the SSL certificate does not match the domain name of the URL being navigated to in the browser. Is there some way to resolve this?
We have a store on a platform called Storenvy. It is a marketplace for buyers and sellers, like Etsy. We have it set up so that our domain name store.stelladivina.com goes to our store hosted on Storenvy’s server. This is implemented by changing the A record for store.stelladivina to the IP address of the Storenvy server.
Store.stelladivina and Storenvy are both hosted on different servers. We do not have control or access to Storenvy’s server.
Things were fine until a week or so ago. Now when you navigate to store.stelladivina in the browser, you get this:
Basically, to my understanding, the error message means that the SSL certificate for the Storenvy site has *.storenvy and storenvy. While the website you are navigating to has the domain name of store.stelladivina. Because these don’t match, the browser thinks it’s some kind of attack.
According to Storenvy, you can solve that by integrating with Cloudflare. (https://support.storenvy.com/hc/en-us/articles/360038746152-How-do-I-get-my-custom-domain-to-show-as-secure-) So I went through the hassle of setting this up. However, when I turn the orange cloud on with Full (strict mode) for store.stelladivina, it then looks like this:
Which pretty much looks like the original problem I encountered. The Storenvy SSL certificate is still valid since it expires in March 2021. I would guess the problem is again, that the SSL certificate lists *.storenvy and storenvy instead of store.stelladivina. So my question is, is there any way to resolve this through Cloudflare? Or is this problem just not solvable?
I double checked that the IP address in the A record is correct. It is. I also did a test to see whether I did something wrong with my Cloudflare setup. I created a test subdomain at test.stelladivina. It works properly:
Storenvy Customer Service is no help. They say, “What i am Suggesting is you contact your Hosting Service, If its Couldfare and tell them you are having trouble Pointing the Domain to Storenvy and they will help you fix it easily. SSL is totally different from the existing issue you are facing. That needs to be fixed first. I would have helped you if i could. Please reach out to your hosting Service.” (that’s a literal copy/paste)
I would guess that if the domain was not pointing correctly to Storenvy, then I would not be getting errors about the SSL certificate having *.storenvy and storenvy on it. Also, in the first screenshot, you can see the site if you click on the link that says “Proceed to store.stelladivina (unsafe).” But the long term solution isn’t to tell prospective customers to ignore the message.