Make sure that you’re going to http://merciadragon.net/wp/ *not* https://merciadragon.net/wp/
As for how the DNS is pointing right now, when a domain is registered or altered, there is a process called propagation, where information about the domain name is passed to internet service providers all over the world. This process can take up to 72 hours (though usually much less). During that time, your domain may go to its old location, and you may also receive a warning message in your browser about “redirect errors.”
If you still have trouble viewing the site after 48 hours have passed, please try clearing your browser’s cache.
If that doesn’t work, try clearing your local DNS cache: https://support.opendns.com/entries/26336865-Clearing-the-DNS-Cache-on-Computers-Servers-and-Web-Browsers
Thanks James for getting back to me. I think I have worked it out with the errors that I was getting. It is showing an SSL certificate that should not be there and pointing to the host not me. Chrome locks me out altogether and Firefox once I clear the cache lets me in once then jumps back to wordpress.com. Interesting that the default index.htm file was reporting a setup fault but I was thinking it was me not working on it. I have just put in a ticket and hopefully when I wake in the morning all should be fixed.
Robert…
Right, you need to visit HTTP for your site now, not HTTPS. You’re seeing your host’s default SSL certificate at HTTPS, and the warning, because you haven’t acquired a valid SSL certificate for your domain yet. That’s one of the safeguards of HTTPS.
If you want HTTPS to work right, you need to acquire a valid SSL certificate for your domain.
https://make.wordpress.org/support/user-manual/web-publishing/https-for-wordpress/
James, thank you for your time in responding. I finally worked out the problem finally. In the browser when I entered http:// …. it just switched to https:// …. and up came the error. I went to bed and looked at it on the tablet and no problem but the tablet was pointed to the ISP (Virgin media) DNS. I can’t change that in the router. My desktop points to OpenDNS. Once I had pointed the DNS to VM and flushed the cache it worked normally.
I relied on the propagation tool WhatsMyDNS.net showed that all DNS was updated. Clearly a OpenDNS server I was using was not fully updated. I will certainly remember this in future.
Thank you for the links and with all this I am wondering if SSL would be worth it as you can get some low cost certificates,
Back to trying to build the site,
Robert…
You’re welcome!
I highly recommend purchasing a certificate and switching over to HTTPS if it’s in your budget. Alternatively, ask your hosting provider if they support Let’s Encrypt: https://letsencrypt.org
