dallasgroot/Documentation
1
0
Fork 0
mirror of https://codeberg.org/Codeberg/Documentation.git synced 2026-06-16 05:13:54 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions

Omitting default 'pages' for 'branch' and 'repo' sometimes causes SSL error

Browse source 
Related to https://codeberg.org/Codeberg/Community/issues/2447

Only updated info for Option 3 as that is the only place I was able to reproduce this
This commit is contained in:
Agam Singh 2026-03-17 17:38:35 -05:00
parent f717140c07
commit 9971f8b379
1 changed files with 11 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
content/codeberg-pages/using-custom-domain.md
View file

@ -198,6 +198,8 @@ In the end it should look like this:
</tbody>
</table>
### Option 3: A/AAAA record
If your service provider does not support `ALIAS records` you can also use `A records` and `AAAA records` instead.
@ -206,8 +208,9 @@ If your service provider does not support `ALIAS records` you can also use `A re
and an `AAAA record` for IPv6 which contains the ip address of the Codeberg Pages server. The servers' ip addresses are:
- `A record` which contains the IPv4 value `217.197.84.141`
- `AAAA record` which contains the IPv6 value `2a0a:4580:103f:c0de::2`
- Second, you need to setup a `TXT record` which contains the information of your repository
location as mentioned above. For example `[[branch.]repo.]user.codeberg.page`.
- Second, you need to setup a `TXT record` which contains the full information of your repository location as mentioned
above. For example `branch.repo.user.codeberg.page`. Do not omit `branch` or `repo` even if you are using the default
`pages` for each.
In the end, it should look like this:
@ -231,7 +234,7 @@ In the end, it should look like this:
<tr>
<td>yourdomain.com</td>
<td>TXT</td>
<td>reponame.username.codeberg.page</td>
<td>branchname.reponame.username.codeberg.page</td>
</tr>
</tbody>
</table>
@ -271,7 +274,7 @@ For the DNS configuration:
- otherwise, A/AAAA records must be used, together with one TXT record:
- name `myself.example.com`, type `A`, data `217.197.84.141`
- name `myself.example.com`, type `AAAA`, data `2a0a:4580:103f:c0de::2`
- name `myself.example.com`, type `TXT`, data `frida.codeberg.page`
- name `myself.example.com`, type `TXT`, data `pages.pages.frida.codeberg.page`
### Personal/Organization site, apex domain
@ -300,7 +303,7 @@ _Note that ALIAS records are not real DNS records and are typically incompatible
- otherwise, A/AAAA records must be used, together with a TXT record:
- name `example.com`, type `A`, data `217.197.84.141`
- name `example.com`, type `AAAA`, data `2a0a:4580:103f:c0de::2`
- name `example.com`, type `TXT`, data `frida.codeberg.page`
- name `example.com`, type `TXT`, data `pages.pages.frida.codeberg.page`
- name `www.example.com`, type `CNAME`, data `frida.codeberg.page`
### Project site, subdomain
@ -326,7 +329,7 @@ For the DNS configuration:
- otherwise, A/AAAA records must be used, together with one TXT record:
- name `colormix-app.example.com`, type `A`, data `217.197.84.141`
- name `colormix-app.example.com`, type `AAAA`, data `2a0a:4580:103f:c0de::2`
- name `colormix-app.example.com`, type `TXT`, data `colormix.frida.codeberg.page`
- name `colormix-app.example.com`, type `TXT`, data `pages.colormix.frida.codeberg.page`
### Project site, apex domain
@ -361,5 +364,6 @@ _Note that ALIAS records are not real DNS records and are typically incompatible
- otherwise, A/AAAA records must be used, together with one TXT record:
- name `example.com`, type `A`, data `217.197.84.141`
- name `example.com`, type `AAAA`, data `2a0a:4580:103f:c0de::2`
- name `example.com`, type `TXT`, data `colormix.frida.codeberg.page`
- name `example.com`, type `TXT`, data `pages.colormix.frida.codeberg.page`
- name `www.example.com`, type `CNAME`, data `colormix.frida.codeberg.page`