Custom domain SSL cert not provisioning SSL_ERROR_INTERNAL_ERROR_ALERT #2822

blaves commented 2026年06月29日 08:38:40 +02:00

Comment

Custom domain pointing to git-pages. DNS fully propagated to 217.197.84.141 worldwide. .domains file is correct. Webhook set to http:// scheme with branch filter pages. HTTP returns 302 to HTTPS correctly but TLS handshake fails with SSL_ERROR_INTERNAL_ERROR_ALERT. Been down 15+ hours. Please force cert provisioning retry.
Username: blaves

Repo: blaves/blaves

### Comment Custom domain pointing to git-pages. DNS fully propagated to 217.197.84.141 worldwide. .domains file is correct. Webhook set to http:// scheme with branch filter pages. HTTP returns 302 to HTTPS correctly but TLS handshake fails with SSL_ERROR_INTERNAL_ERROR_ALERT. Been down 15+ hours. Please force cert provisioning retry. Username: blaves Repo: blaves/blaves

Gusted commented 2026年06月29日 17:36:59 +02:00

We no longer offer the old pages for newer users. You're recommended to use the new method: https://codeberg.page/

We no longer offer the old pages for newer users. You're recommended to use the new method: https://codeberg.page/

blaves commented 2026年06月29日 17:50:39 +02:00

I'm a new user so I can only use git-pages. The docs say custom domains currently only work with the old method. How do I set up a custom domain with git-pages specifically? DNS is pointing to 217.197.84.141, .domains file contains blaves.com, webhook is set to https://blaves.codeberg.page/blaves/ with branch filter pages.

I'm a new user so I can only use git-pages. The docs say custom domains currently only work with the old method. How do I set up a custom domain with git-pages specifically? DNS is pointing to 217.197.84.141, .domains file contains blaves.com, webhook is set to https://blaves.codeberg.page/blaves/ with branch filter pages.

Gusted commented 2026年06月29日 17:56:54 +02:00

https://docs.codeberg.org/codeberg-pages/using-custom-domain explains how to do it for custom domains.

https://docs.codeberg.org/codeberg-pages/using-custom-domain explains how to do it for custom domains.

blaves commented 2026年06月29日 18:00:21 +02:00

The docs at that link state: "Currently, websites that use custom domains can only be deployed using the old method." As a new user I cannot use the old method. Does this mean custom domain support for new git-pages users is not available yet, or is there something specific I am missing in my setup?

The docs at that link state: "Currently, websites that use custom domains can only be deployed using the old method." As a new user I cannot use the old method. Does this mean custom domain support for new git-pages users is not available yet, or is there something specific I am missing in my setup?

Gusted commented 2026年06月29日 18:02:06 +02:00

The docs does not state that? Could you open the page in a private window? Maybe you have a old version in your cache?

The docs does not state that? Could you open the page in a private window? Maybe you have a old version in your cache?

blaves commented 2026年06月29日 18:33:25 +02:00

Still getting Error 400: "forge client: new users/orgs are not allowed to use the old pages server." I have added the _git-pages-repository TXT record pointing to https://codeberg.org/blaves/blaves.git as per the updated docs. A, AAAA, and TXT records are all set correctly. What else is needed?

Still getting Error 400: "forge client: new users/orgs are not allowed to use the old pages server." I have added the _git-pages-repository TXT record pointing to https://codeberg.org/blaves/blaves.git as per the updated docs. A, AAAA, and TXT records are all set correctly. What else is needed?

bearbearean commented 2026年06月29日 19:17:57 +02:00

I believe I'm experiencing the same issue. Or at least I'm not finding what I'm missing to make custom domains work.

I have the following DNS records set:

A thelivingroom.bearbearean.dev -> 217.197.84.141
AAAA thelivingroom.bearbearean.dev -> 2a0a:4580:103f:c0de::2
TXT _git-pages-repository.bearbearean.dev -> https://codeberg.org/bearbearean/pages.git
TXT _git-pages-repository.thelivingroom.bearbearean.dev -> https://codeberg.org/bearbearean/pages.git

I'm not sure which of two TXT records are necessary for only deploying to a subdomain, but I figured both won't hurt?

I'm trying to deploy the website to https://thelivingroom.bearbearean.dev using the webhook method so I have that set as the Target URL. And then when the webhook runs it returns a TLS error:

Delivery: Post "https://thelivingroom.bearbearean.dev": remote error: tls: internal error

And manually visiting the site gives the same TLS error as the OP: SSL_ERROR_INTERNAL_ERROR_ALERT

I'd love to know what I'm missing, thanks in advance!

Edited to add: Setting the target URL to https://bearbearean.codeberg.page/pages does deploy the website successfully, but it sadly doesn't make the custom domain work.

I believe I'm experiencing the same issue. Or at least I'm not finding what I'm missing to make custom domains work. I have the following DNS records set: ``` A thelivingroom.bearbearean.dev -> 217.197.84.141 AAAA thelivingroom.bearbearean.dev -> 2a0a:4580:103f:c0de::2 TXT _git-pages-repository.bearbearean.dev -> https://codeberg.org/bearbearean/pages.git TXT _git-pages-repository.thelivingroom.bearbearean.dev -> https://codeberg.org/bearbearean/pages.git ``` I'm not sure which of two TXT records are necessary for only deploying to a subdomain, but I figured both won't hurt? I'm trying to deploy the website to `https://thelivingroom.bearbearean.dev` using the webhook method so I have that set as the Target URL. And then when the webhook runs it returns a TLS error: ``` Delivery: Post "https://thelivingroom.bearbearean.dev": remote error: tls: internal error ``` And manually visiting the site gives the same TLS error as the OP: `SSL_ERROR_INTERNAL_ERROR_ALERT` I'd love to know what I'm missing, thanks in advance! **Edited to add**: Setting the target URL to `https://bearbearean.codeberg.page/pages` does deploy the website successfully, but it sadly doesn't make the custom domain work.

Gusted commented 2026年06月30日 00:20:31 +02:00

@blaves I checked again and it seems blaves.com is working now.

@blaves I checked again and it seems blaves.com is working now.

Gusted commented 2026年06月30日 00:22:44 +02:00

@bearbearean after doing that, you can try to set it to the custom domain (with http://) that should work.

@bearbearean after doing that, you can try to set it to the custom domain (with http://) that should work.

bearbearean commented 2026年06月30日 00:31:21 +02:00

@Gusted well, that was a simple fix... Thanks very much!

I suggest that to be added to the documentation, I didn't realize setting it specifically to http:// was a necessary step.

@Gusted well, that was a simple fix... Thanks very much! I suggest that to be added to the documentation, I didn't realize setting it specifically to http:// was a necessary step.

Gusted commented 2026年06月30日 00:32:12 +02:00

Weird, I thought this was documented already. @whitequark sorry to ask you, the first deployment for custom domains needs a http:// scheme right?

Weird, I thought this was documented already. @whitequark sorry to ask you, the first deployment for custom domains needs a `http://` scheme right?

whitequark commented 2026年06月30日 00:33:38 +02:00

Yes.

Yes.

blaves commented 2026年06月30日 08:04:02 +02:00

@Gusted It seems to be working now not sure how? But if any issues persist I will comment on this or just open a new issue

anyways thanks for the help!

@Gusted It seems to be working now not sure how? But if any issues persist I will comment on this or just open a new issue anyways thanks for the help!