Web1.0 Hosting Forum - HTTPS for custom domains

HTTPS for custom domains (reply)

pnppl — Tue, 10 Feb 2026 23:54:42 +0000

Update: got it all fixed! For anyone else with this issue, make sure you email support directly, because I think my browser didn't like the contact form. They were extremely prompt when I emailed directly.

Another thing to know is that the SSL certificate will not cover the www subdomain. I was able to solve this with my domain name provider by setting up a 301 redirect from www.pnppl.cc to pnppl.cc. Without this, some people will type the www and then just think your website does not exist.

HTTPS for custom domains (reply)

pnppl — Thu, 05 Feb 2026 23:28:27 +0000

Cool! Guess I just need to be patient then. :)

HTTPS for custom domains (reply)

tibi — Thu, 05 Feb 2026 23:07:37 +0000

I emailed support and they set it up instantly. Thanks, support!

HTTPS for custom domains (reply)

pnppl — Thu, 05 Feb 2026 23:01:09 +0000

It looks like you got this resolved. Did support help you or did you have to do something yourself? Facing the same issue here.

HTTPS for custom domains (reply)

Turboblack — Wed, 12 Nov 2025 14:35:35 +0000

Hi.

Contact our technical support team support@w10.host and they will issue you a certificate.

HTTPS for custom domains (reply)

tibi — Tue, 11 Nov 2025 17:00:23 +0000

Hi, I have the same problem as OP. I've moved my domain over and the HTTP version loads fine but the HTTPS version throws up an error. ERR_CERT_COMMON_NAME_INVALID on firefox and SSL_ERROR_BAD_CERT_DOMAIN on chrome. The regular domain has no errors.

Sorry for being a bit inexperienced, but what can I do to fix this? Do I need to set up my own SSL for this domain?

HTTPS for custom domains (reply)

Turboblack — Tue, 23 Sep 2025 09:18:02 +0000

ok.

as example https://elpis.ws and http://elpis.ws

the same as https://elpis.w10.site/ http://elpis.w10.site/

also .w0.am, .narod.ws and .oldcities.org

You can use both HTTP and HTTPS.

no settings were used

The NET::ERR_CERT_COMMON_NAME_INVALID error indicates a problem with a website's SSL/TLS certificate, specifically a mismatch between the domain name in the certificate and the domain name being accessed. This means the browser cannot verify the website's identity, leading to a security warning.

HTTPS for custom domains (reply)

kotik-ocelotik — Mon, 22 Sep 2025 09:13:15 +0000

Have you read the Subject and the question itself? I have already seen the FAQ and still, there is not a single word about SSL/HTTPS configuration.

HTTPS for custom domains (reply)

Turboblack — Mon, 22 Sep 2025 09:03:32 +0000

How to link my own domain name for the website on the Web1.0 Hosting?

You can link any your domian name to the website hosted on the Web1.0 Hosting. The only one requirement here: the left part before a point of your domain has to be the same, as your website login. for example:

You have a site called mysupermegawebsite.w10.site, then you can link the following domain names: mysupermegawebsite.com same as mysupermegawebsite.mydomain.com

It can be A record pointed to the IPv4 address 135.181.118.12 or AAAA record pointed to the IPv6 address 2a01:4f9:4b:1e30::3

Also you can use CNAME record and point it to your website address, same as w10.host, it also will be working.

HTTPS for custom domains

kotik-ocelotik — Sat, 20 Sep 2025 11:58:05 +0000

Hi! I have a website hosted with this hosting and I have a subdomain. I've made my subdomain to point on the hosting's via A record and it works... only when I visit it with HTTP. When I do HTTPS request, my browser sends NET::ERR_CERT_COMMON_NAME_INVALID and if I proceed, I get this forum opened.
You can check it youself if you open my website via HTTP and HTTPS. Can it be fixed somehow?