"Unable to establish SSL connection" to custom domain codeberg site #2826

vigilantesculpting commented 2026年06月30日 13:52:06 +02:00

Comment

I have a pre-generated site at https://vigilantesculpting.codeberg.page/

This was previously hosted on github, and I decided to join you fine people here at codeberg.

I have a custom domain registered with namecheap: www.vigilantesculpting.com.
I tried to use the guide at
https://docs.codeberg.org/codeberg-pages/using-custom-domain/
to point the namecheap domain to the codeberg pages site.

To do this, I modified the CNAME entry on namecheap to read "pages.vigilantesculpting.codeberg.page."

After doing this, I get the following from dig:

$ dig CNAME www.vigilantesculpting.com
...
;; ANSWER SECTION:
www.vigilantesculpting.com. 30 IN CNAME pages.vigilantesculpting.codeberg.page.
...

so this seems ok?

But if I try to access my custom domain via webbrowser it gives me a security issue.
And using wget gives me

$ wget https://www.vigilantesculpting.com
--2026年06月30日 21:40:59-- https://www.vigilantesculpting.com/
Resolving www.vigilantesculpting.com (www.vigilantesculpting.com)... 217.197.84.141
Connecting to www.vigilantesculpting.com (www.vigilantesculpting.com)|217.197.84.141|:443... connected.
OpenSSL: error:0A000438:SSL routines::tlsv1 alert internal error
Unable to establish SSL connection.

I don't do this kind of thing very often, and I am not sure of what to try next.
I have seen mentions of a .domain file that some people seem to store in their repo?
Also, I used to have a CNAME file hosted on github. Do I need this?

Any help would be greatly appreciated, thank you!

### Comment I have a pre-generated site at https://vigilantesculpting.codeberg.page/ This was previously hosted on github, and I decided to join you fine people here at codeberg. I have a custom domain registered with namecheap: www.vigilantesculpting.com. I tried to use the guide at https://docs.codeberg.org/codeberg-pages/using-custom-domain/ to point the namecheap domain to the codeberg pages site. To do this, I modified the CNAME entry on namecheap to read "pages.vigilantesculpting.codeberg.page." After doing this, I get the following from dig: ``` $ dig CNAME www.vigilantesculpting.com ... ;; ANSWER SECTION: www.vigilantesculpting.com. 30 IN CNAME pages.vigilantesculpting.codeberg.page. ... ``` so this seems ok? But if I try to access my custom domain via webbrowser it gives me a security issue. And using wget gives me ``` $ wget https://www.vigilantesculpting.com --2026年06月30日 21:40:59-- https://www.vigilantesculpting.com/ Resolving www.vigilantesculpting.com (www.vigilantesculpting.com)... 217.197.84.141 Connecting to www.vigilantesculpting.com (www.vigilantesculpting.com)|217.197.84.141|:443... connected. OpenSSL: error:0A000438:SSL routines::tlsv1 alert internal error Unable to establish SSL connection. ``` I don't do this kind of thing very often, and I am not sure of what to try next. I have seen mentions of a .domain file that some people seem to store in their repo? Also, I used to have a CNAME file hosted on github. Do I need this? Any help would be greatly appreciated, thank you!

vigilantesculpting commented 2026年06月30日 14:53:42 +02:00

I have also tried to modify the CNAME entry on namecheap to
vigilantesculpting.codeberg.page.
and after waiting for the record to propagate (and checking with dig) I still can't connect to the site.
wget reports the same tlsv1 alert internal error as before.

I have also tried to modify the CNAME entry on namecheap to `vigilantesculpting.codeberg.page.` and after waiting for the record to propagate (and checking with dig) I still can't connect to the site. wget reports the same tlsv1 alert internal error as before.

vigilantesculpting commented 2026年07月01日 00:05:49 +02:00

Update: Having left the site alone for a couple of hours, I now see this when visiting vigilantesculpting.com with Firefox:

Failed Dependency (Error 424)!
Sorry, but this page couldn't be served:
"target is no codeberg page"

If I visit vigilantesculpting.codeberg.page instead, the site loads without problems.

Update: Having left the site alone for a couple of hours, I now see this when visiting vigilantesculpting.com with Firefox: Failed Dependency (Error 424)! Sorry, but this page couldn't be served: "target is no codeberg page" If I visit vigilantesculpting.codeberg.page instead, the site loads without problems.

Gusted commented 2026年07月01日 00:24:20 +02:00

It might help if you have https://codeberg.org/vigilantesculpting/pages/src/branch/pages/.domains to only contain
www.vigilantesculpting.com, because vigilantesculpting.com is not pointing to codeberg pages.

It might help if you have https://codeberg.org/vigilantesculpting/pages/src/branch/pages/.domains to only contain `www.vigilantesculpting.com`, because `vigilantesculpting.com` is not pointing to codeberg pages.

vigilantesculpting commented 2026年07月01日 00:26:57 +02:00

Thank you @Gusted, I'll give it a go. I could not find any documentation for the .domains file here, bit found references to it on other blogs, so I was cargo culting this and basically just guessing.

Thank you @Gusted, I'll give it a go. I could not find any documentation for the .domains file here, bit found references to it on other blogs, so I was cargo culting this and basically just guessing.

vigilantesculpting commented 2026年07月01日 00:45:28 +02:00

I've removed the invalid entry from the .domains file. Now visiting www.vigilantesculpting.com tells be that I should migrate to git-pages, since new users are not allowed to use pages V2.

However, I have already followed the instructions on https://docs.codeberg.org/codeberg-pages/migrating-from-pages-v2/

At this point I'm not sure what I'm doing wrong.

I've removed the invalid entry from the .domains file. Now visiting www.vigilantesculpting.com tells be that I should migrate to git-pages, since new users are not allowed to use pages V2. However, I have already followed the instructions on https://docs.codeberg.org/codeberg-pages/migrating-from-pages-v2/ At this point I'm not sure what I'm doing wrong.

vigilantesculpting commented 2026年07月01日 08:34:50 +02:00

Here is a discrepancy I have found. Please keep in mind I have no experience setting these things up, so I am guessing most of the time:

$ dig www.vigilantesculpting.com
...
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;www.vigilantesculpting.com. IN A
;; ANSWER SECTION:
www.vigilantesculpting.com. 1075 IN CNAME vigilantesculpting.codeberg.page.
vigilantesculpting.codeberg.page. 2876 IN A 217.197.84.141
...

However:

$ dig vigilantesculpting.com
...
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;vigilantesculpting.com. IN A
;; ANSWER SECTION:
vigilantesculpting.com. 1523 IN A 185.199.108.153
vigilantesculpting.com. 1523 IN A 185.199.111.153
vigilantesculpting.com. 1523 IN A 185.199.109.153
vigilantesculpting.com. 1523 IN A 185.199.110.153
...

Is this my problem? My namecheap domain name registration uses one CNAME entry, which I have updated to "vigilantesculpting.codeberg.page."
According to dig, the apex domain vigilantesculpting.com still points to (what I believe are) github's servers.

Any help with this please?

Here is a discrepancy I have found. Please keep in mind I have no experience setting these things up, so I am guessing most of the time: ``` $ dig www.vigilantesculpting.com ... ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;www.vigilantesculpting.com. IN A ;; ANSWER SECTION: www.vigilantesculpting.com. 1075 IN CNAME vigilantesculpting.codeberg.page. vigilantesculpting.codeberg.page. 2876 IN A 217.197.84.141 ... ``` However: ``` $ dig vigilantesculpting.com ... ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;vigilantesculpting.com. IN A ;; ANSWER SECTION: vigilantesculpting.com. 1523 IN A 185.199.108.153 vigilantesculpting.com. 1523 IN A 185.199.111.153 vigilantesculpting.com. 1523 IN A 185.199.109.153 vigilantesculpting.com. 1523 IN A 185.199.110.153 ... ``` Is this my problem? My namecheap domain name registration uses one CNAME entry, which I have updated to "vigilantesculpting.codeberg.page." According to dig, the apex domain vigilantesculpting.com still points to (what I believe are) github's servers. Any help with this please?

vigilantesculpting commented 2026年07月02日 05:13:32 +02:00

In the meantime I have replaced the A record entries for vigilantesculpting.com with a single A record pointing to the 217.197.84.141 server address.

When visiting vigilantesculpting.com I still get the same "Bad Request (Error 400)!" page, which says
"forge client: new users/orgs are not allowed to use the old pages server. See https://codeberg.page on using git-pages"

I have not followed any documentation to use the old pages server. In fact I have only followed the git-pages documentation.
What is weird is that visiting vigilantesculpting.codeberg.page works!
So there is just something in my domain registration that is screwed up, I'm sure...

However, at this point, I am out of ideas. I would have loved to host my site on codeberg, because I think you guys have the right approach to privacy and llms.

In the meantime I have replaced the A record entries for vigilantesculpting.com with a single A record pointing to the 217.197.84.141 server address. When visiting vigilantesculpting.com I still get the same "Bad Request (Error 400)!" page, which says "forge client: new users/orgs are not allowed to use the old pages server. See https://codeberg.page on using git-pages" I have not followed any documentation to use the old pages server. In fact I have only followed the git-pages documentation. What is weird is that visiting vigilantesculpting.codeberg.page works! So there is just something in my domain registration that is screwed up, I'm sure... However, at this point, I am out of ideas. I would have loved to host my site on codeberg, because I think you guys have the right approach to privacy and llms.