New setup my test page yesterday but now seems Parked

[jaikrishna.t]

SO install an ssl first?

[Greenreader9]

I don’t think I have ever seen that error before. For me, I get a parking page.

I recommend to not touch any settings for about 24-72 hours, and if it is still not working, remove the domain from your hosting account and add it back.

Please let me know if you have any questions!

[dra.l.fs.vampire]

Actually, I have added a new account and a new domain to test
Seems getting the same issue with parking page

[Greenreader9]

Make sure you are waiting for DNS propagation!

What is DNS propagation

You’ve added a new domain name to your account, just changed your nameservers or recently modified some DNS settings. However, they aren’t working yet. You’ve discovered already that it’s not working yet because of something called “DNS Propagation”. But what does that mean? Introduction to DNS Before you can understand how DNS Propagation works, you need to understand how DNS itself works. So let’s start with that. Servers on the internet are identified by a set of numbers called an IP addres…

When will my domain name start working

If you’ve just created your account, or just added a new domain name to an account, you may be surprised that you are unable to view your website when using the domain. Instead you may see: An advertisements page, with ?z being added to the URL. An error saying “This site can’t be reached”. This is usually caused by a system called DNS Caching. This article explains how DNS Caching works, why your website isn’t up yet and what you can do to see your website right now. When will I be able to …

[Admin]

The issue seems to be with your HTTPS redirect. Because you’ll probably want your site to redirect to https://ec783f256be1f8c3a73fdf5994e3f8bb.lovestoblog.com, but it actually redirects to only https:// . Since that last thing is not a valid URL, you’ll see the Oops page.

I’m not sure how you’re trying to enforce HTTPS, but you’ll probably want to remove it and check it because it doesn’t seem right.

[dra.l.fs.vampire]

Hi Admin,

It worked before. But just suddenly all things started NOT working including both HTTP and HTTPS in the next day.
The HTTPS url was valid and I tested.

Now, it shows me parking page again.
I really hope if you can help to check further?

[Oxy]

@dra.l.fs.vampire

I think I know what the problem is
ns2 returns the wrong data instead of pointing to the IP

and then depending on which NS serves you at a given moment, you see
normal website or you see parking service

What you need to do is remove the subdomain from the system and add it again after 10 minutes
so that the server is forced to refresh the data

[dra.l.fs.vampire]

OxyDac,

Really thank you. You are pretty right.
Clearly showed that 11776.bodis.com with alias set (which points to 199.59.243.200) does NOT serve my domain name in that server. It gives parking page and it is confirmed now.

I did try to get the 185.27.134.126 with a static host before using curl.
After I have read your message, I have TRIED AGAIN and figured out the curl must contain a user-agent header. I think I didn’t put that last time and I assumed this IP could not response too.
Now, it really returns a 200 OK with a javascript called ‘aes.js’ to test if my query is really a browser.
That is also interesting of return.

So, the mechanism of getting a subdomain from infinityfree.net is, by default, parked in 11776.bodis.com. Once I have created an account and request of a subdomain. It manages to create virtual hosting in other servers (in this case is 185.27.134.126), while 11776.bodis.com is NOT serving for the new hosting.

In my case, somehow the ns2.epizy.com is still not updated. That’s why I am wrongly pointed to a un-servicing host some time later.

Now it much make more sense. I think @Admin shall take a look into this case further.

[Admin]

@dra.l.fs.vampire

In my case, somehow the ns2.epizy.com is still not updated. That’s why I am wrongly pointed to a un-servicing host some time later.

I checked your domain and both nameservers return the right data now.