if I create a new website named example.com cyberpanel creates dns zones for this domain, but if I create a new website named subdomain.anotherexample.com it doesn’t create a dns zone. However, I can manually create a dns zone for subdomain.anotherexample.com. It would be convenient if zone creation for a new website was done for every site, or maybe done based on a checkbox (something like “click here to also create a new dns zone for this domain”)
I tried this but when I go into DNS → Add delete records, and select the newly converted subdomain, it says: ‘Cannot fetch records. Error message:Domains matching query does not exist.’
furthermore, if I go to “delete zones” it shows up in the list, but when I pick it it says:
Cannot delete zone. Error message: Domains matching query does not exist.
+1
Am I right in thinking this is related to why SSL isn’t working for me?
- example.com dns is hosted elsewhere (with an A record pointing test.example.com at my cyberpanel server)
- test.example.com is hosted on cyberpanel server
- no explicit DNS zones set up on cyberpanel server
- cyberpanel says SSL issued for test.example.com but browser treating it like self-signed
I haven’t had any trouble getting ssl certs issued through letsencrypt when setting up subdomains like you describe.
maybe clear cache in browser, switch browsers, etc… maybe the unsigned cert is cached or something… also try an ssl checker site that will pull your website and give a report on the cert
Type your comment> @andjules said:
+1
Am I right in thinking this is related to why SSL isn’t working for me?
- example.com dns is hosted elsewhere (with an A record pointing test.example.com at my cyberpanel server)
- test.example.com is hosted on cyberpanel server
- no explicit DNS zones set up on cyberpanel server
- cyberpanel says SSL issued for test.example.com but browser treating it like self-signed
When LetsEncrypt fails at issuing a certificate, CyberPanel fails silently and generates a self-signed certificate automatically. Make sure your domain resolves correctly, and allow some time for your DNS records to propagate across the web (at least TTL seconds since last try!) before re-issuing the SSL certificate in CyberPanel.
i have same problem, any answer?