Custom domain certificate mismatch on Zeabur

Custom domain certificate mismatch on Zeabur

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.

Context from the issue

gh:zeabur/zeabur#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.)

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