Fix this

Hosting Support
1

Website URL

all of it

Error Message

The selected name is invalid.

Other Information

i cant use www. anymore it just says that error fix it asap because my whole stuff is ruined and im to lazy to change it all.

2

this is when i make cname btw

3

That’s by design.

Our free subdomains can only be hosted with us. Some decided to work around that by pointing the www subdomain to an external hosting service. We don’t want that to happen, so that functionality has been blocked.

And if you have your own domain name and you want to host it elsewhere, you can and should use a DNS hosting provider that gives you full control over your DNS records, or just use the nameservers of your new hosting.

In any case, everything is working as intended. The exploit has been fixed.

6 Likes
4

Unfortunately, that’s really the only option.

1 Like
5

i dont think of it as an exploit i think of it as using a subdomain as my frontend and my backend external its kinda like buying a domain as frontend and hosting backend external i think you should put it back to how it was before this is really bad for me as my thing is on multiple sites as www. and it just ruins everything and will probably lead to me shutting down

6

Please understand that free subdomains are still our domains. You don’t own them, we do, and we decide what you can do with them.

You didn’t buy them, and thinking that thinking that you did is the wrong way to think about it. Had you actually bought your own domain name, you wouldn’t have this issue, because you actually would have full control over the domain’s DNS.

And you have to understand: you can still host your backend elsewhere! You could for example:

  • Host it on a free subdomain from the hosting provider where you are hosting the backend. It doesn’t matter if it doesn’t look as nice: it’s the backend, so it’s invisible to the user.
  • You can even host it on a subdomain from us, just not on a domain like example.ct.ws or www.example.ct.ws. But you can still setup a CNAME record for backend.example.ct.ws or api.example.ct.ws.

So unless the actual reason you need this is different than the reason you’re giving us here, you really have no need to setup a CNAME record for the www subdomain. It just won’t work exactly the same as it did before.

5 Likes
7

I get it now I really do thought it through and realized it’s your domain you own it and I was trying to use www. with an external service which wasn’t the right move. my bad. ill figure out something else to use instead of www. once I’ve got the energy.

8

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.