I have three domains using the pages on my infinityfree directory.
Was working on getting two of them to appear secure upon initial entry using the redirected URLs bobfarleymusic.com and littlestbigband.com . Had changed the bobfarleymusic dns codes on doteasy to the InfinityFree set, and after it propagated a few hours later, the page no longer appeared; as I recall it opened to the same one it opens on now, referenced above. So I decided to get rid of the faulty work I’d done, but still the domain URL does not work for the page in Safari, where it rotates ads.
In Chrome, the unsecure address opens a page that warns of the page being unsecure and a link to Proceed Anyway, and it does. However, when I type in the https address, Chrome says it can’t open it at all.
Meanwhile, my forwarded littlestbigband.com page, which has the https prefix, opens a warning page on Chrome saying it is unsecure and providing a link to continue to it, where it quickly gathers up its secure lock icon.
I suppose the problem is with waiting again for the propagation to settle in.
My main page, raggedyedgemusic.com, is secured at the current host (doteasy) until the end of the year, but I surmise that after I no longer have it secured there, I’ll run into the same problem with people running into the WARNING page before they can enter my site.
Anyone have a solution to the security issue of a domain coming from another provider? Moving it to infinityfree, perhaps? How hard could that be?
I am a bit confused on exactly what you are asking / what you are trying to accomplish.
You cannot transfer domains to InfinityFree, as InfinityFree is not a domain registrar. Keeping your domain at your current registrar is not any less secure than moving them elsewhere. Just change the namservers to IF, and work from there.
What I want to do is to have the website (https://www.bobfarleymusic.com) open without going through a unsecured warning page or a page that says it cannot be opened. This only happens when the visitor tries to open the page the first time. If they go on (if they can–they don’t get the choice if the link it https), the page displays the secure lock and as long as it’s in the visitor’s cache, it is fine.
I did have the nameservers changed, but the problem did not go away. I switched them back to the original nameservers and after a while, it is working like it did before.
Of my three URLS, only the one that is currently hosted on doteasy with an SSL opens without the warning pages. After my hosting plan with doteasy ends, I will probably run into the same warning pages problem, I think.
The second one doesn’t give me an unsecured warning, but instead redirects to https://raggedyedge.free.nf/littlestbigband.html
That would seem to indicate it’s a URL redirect. Are you sure it’s set to InfinityFree’s nameservers and has its SSL certificate set up properly?
Both of your domains are using DotEasy’s nameservers, and pointing to an IP address from DotEasy. They are not pointing to our hosting in any way and are not assigned to any hosting account.
So any issue you’re experiencing with the redirect, including connection issues or HTTPS issues, are the result of your setup on DotEasy’s side, which are unrelated to the website you’re actually hosting with us.
If this is the setup you want, then you’ll have to talk to DotEasy about this, because they know a lot more about their service than we do.
Alternatively, you could setup the domains on our hosting. Then you can either redirect the domains on our end to your free subdomain, or even setup the pages directly on your domain name.
The actual website is already hosted with us, so you don’t need to migrate anything.
No, that link doesn’t work. It does work without HTTPS, but it appears that (what I presume is) DotEasy’s domain redirect service does not support HTTPS, and any HTTPS connection is simply blocked on the network level.
Please be aware that for a HTTPS link to work, the site must have a valid SSL certificate. This is even necessary if it’s just a redirect.
If you want to be able to with HTTPS to, that could also be a reason to setup the redirect on our hosting instead: we do offer HTTPS support.