Custom domain certificate mismatch on Zeabur

TL;DR

The reporter assumed Zeabur did not issue SSL certificates for custom domains and asked for the feature to be added. (Issue filed in Chinese; paraphrased.)

Steps

1. https://github.com/zeabur/zeabur/issues/54: Issue zeabur/zeabur#54 (closed, 6 comments): After binding a custom domain to a Zeabur web app, the browser reports a certificate mismatch. The reporter assumed Zeabur did not issue SSL certificates for custom domains and asked for the feature to be added. (Issue filed in Chinese; paraphrased.)

When to use

You are seeing this: 1. https://github.com/zeabur/zeabur/issues/54: Issue zeabur/zeabur#54 (closed, 6 comments): After binding a custom domain to a Zeabur web app, the browser reports a certificate mismatch. Use this skill when you run into "Custom domain certificate mismatch on Zeabur".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://github.com/zeabur/zeabur/issues/54:

Issue gh:zeabur/zeabur#54: the reporter asked: Issue zeabur/zeabur#54 (closed, 6 comments): After binding a custom domain to a Zeabur web app, the browser reports a certificate mismatch. The reporter assumed Zeabur did not issue SSL certificates for custom domains and asked for the feature to be added. (Issue filed in Chinese; paraphrased.) The verified answer was: No missing feature: Zeabur auto-provisions an SSL certificate for every bound custom domain, usually within 30 seconds to a minute, per maintainer yuaanlin. If you see a cert mismatch, first check the domain status in the Zeabur dashboard and wait until it reads PROVISIONED. Second, if that domain was previously bound on another platform, your browser may be serving a cached certificate for the old binding; clear it or test in a fresh profile before concluding the cert is broken. Evidence thread: https://github.com/zeabur/zeabur/issues/54