HSTS error but SSL and HSTS are enabled

Domain has added 4 nameservers

2 for hosting, 2 for cloudflare

Please unproxy (:grey:) these subdomains:

  1. ftp
  2. mail
  3. pop
  4. smtp

Because proxying will break the functionality they are ment to have.

Please remove the two “for hosting”!
So it in the end will just the two from CloudFlare.
Then, after maximum 48 hours it will for sure work

Ok, but will I be able to manage the domain through the hosting panel after that?

No, if you use CloudFlare you will be able to manage the domain in CloudFlares Dashboard.

Ok, i’ve made changes in DNS as you said

Yes, i’ve removed them

Have you also removed these two NameServers?

  1. ns1.smartape.ru
  2. ns2.smartape.ru

Good. then wait some hours and check here:

Once they are all reporting just CloudFlare NameServer your site will work.

Not all but most of them are cloudflare NS, but cloudflare says i need to proxy ftp, pop, smtp and mail to not expose ip’s (That protocols work for all my users even when proxied)

Thats true. un-proxy them will expose your IP, but proxying them will break function. Chose wisely.
Or take a complete different domain for pointing on your server and to use FTP, POP3, SMTP and Mail.

But anyway a Mail-Subdomain will always expose your IP. Therefore it is not recommended to host your MailServer on the same Server as your WebServer.

But again: if you proxy these subdomains it will break the function which they are ment to serve.

1 Like

Returning 404 page like this


This is a 4xx client side error, for troubleshooting visit 4xx Client Error – Cloudflare Help Center
Origin server was unable or unwilling to find the resource requested. This usually means the host server could not find the resource. To serve a more permanent version of this error one should use a 410 error code.

These errors typically occur when someone mistypes a URL on your site when there is a broken link from another page, when a page that previously existed is moved or removed, or there is an error when a search engine indexes your site. For a typical site, these errors account for approximately 3% of the total page views, but they’re often untracked by traditional analytics platforms like Google Analytics.

Website owners usually implement a custom page to be served when this error is generated.

Cloudflare does not generate 404s for customer websites, we only proxy the request from the origin server. When seeing a 404 for your Cloudflare powered site you should contact your hosting provider for help.

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