SSL wrong name
-
Hi.
I tried to connect my WordPress app to my domain at mondaa.com.au but it says NET::ERR_CERT_COMMON_NAME_INVALID. i thought WordPress was supposed to take care of ssl service. did i do something wrong i put A name on dns (I might have removed TXT that has been generated by WordPress).
The blog I need help with is: (visible only to logged in users)
-
If there were supposed to be additional dns records that’s generated by WordPress on Championweb, could you share it with me? i removed few TXT records thinking it was from previous firebase site.
-
the SSL that is assigned to my site seems to be (*.wordpress.com) which is different than my domain and i can’t access my website.
-
Hi there, I have checked the
mondaa.com.audomain, and the name servers are not pointed at WordPress.com, so the internet does not know that the site is hosted here.If you can log into your domain registrar account, and change the name servers on the domain to the following that will get things underway.
ns1.wordpress.com
ns2.wordpress.com
ns3.wordpress.comIt can take 24-72 hours for a change to the domain settings to fully propagate around the internet. Generally though in 4-6 hours things should have stabilized and it should be working for your site here.
Our system checks newly connected domains regularly to apply the SSL certificate, but if the domain is working but is not showing as secure (SSL) come back and we can manually set it. We cannot set it though till after the name servers are set to ours, and the bulk of the propagation has completed.
-
-
Hi there,
I see that the WordPress.com A records are still propagating. Give it 24-48 hours, and it should start working.
Once your domain is correctly connected, the SSL certificate will be automatically issued.
- The topic ‘SSL wrong name’ is closed to new replies.
WordPress.com Forums 