[Bug]: Custom domain verified and HTTP works, but HTTPS presents no certificate

verified: true
misconfigured: false

Plain HTTP routing works correctly and reaches the InsForge-hosted frontend.

However, HTTPS does not present a certificate.

Repeated TLS checks showed:

TCP connection to port 443 succeeds
TLS handshake starts
NO PEER CERTIFICATE PRESENTED
connection closes

The TLS errors were consistently similar to:

unexpected eof while reading
no peer certificate available

I also checked the common client-side causes:

CAA: no restrictive policy found
DNSSEC: not implicated
Public DNS resolvers: consistent
Resolver split: none
HTTP ACME path: reaches the hosting edge correctly

During the test:

DNS: PASS
HTTP routing: PASS
InsForge domain verification: PASS
HTTPS certificate: NOT PRESENTED

I rolled the production domain back to the previous hosting for safety, so the live website is healthy again.

Could the InsForge team please check the certificate provisioning state for the custom domain and confirm whether certificate issuance is stuck or needs to be retriggered?

I can provide the exact domain and additional DNS details privately if needed.

### How to reproduce

1. Add an apex custom domain to an InsForge frontend deployment.
2. Point the apex A record to the A record value provided by InsForge.
3. Wait until InsForge reports:

   ```text
   verified: true
   misconfigured: false

4. Confirm that plain HTTP reaches the InsForge-hosted frontend.
5. Connect to the same domain over HTTPS / port 443.
6. Observe that the TLS connection starts but no peer certificate is presented.
7. HTTPS fails even though DNS verification and HTTP routing are working.



### Environment (optional)

Client/testing environment:

- Windows 11
- Google Chrome
- DNS checked against multiple public resolvers including Cloudflare (1.1.1.1) and Google (8.8.8.8)
- TLS tested independently from the browser
- InsForge custom domain reports `verified: true` and `misconfigured: false`
- Frontend deployment is reachable correctly over plain HTTP

Privacy / Public Issue Notes :

This version is intentionally safe for a public GitHub issue.

It does not include:

- previous production server IPs;
- mail server IPs;
- MX topology;
- rollback details;
- test-origin hostname;
- API keys;
- tokens;
- passwords;
- cookies;
- OTPs;
- private customer data.

If InsForge needs the exact domain name or detailed DNS records, provide those through a private support channel when possible.