|
Föderation EN Fr 19.07.2024 20:36:31 I cannot figure out what this error is trying to tell me. ``` Sorry, but this page couldn't be served. "could not obtain repo owner from custom domain" Can anybody help? I've used the tutorial on codeberg for setting up a custom domain, I've made the .domains file and I've edited cloudflares DNS settings. It's not being proxied. |
|
Föderation EN Fr 19.07.2024 20:48:23 @tripplehelix I think you need to publish a TXT DNS record for helix.me.uk which indicates which repository your domain should be served from. See Option 3 under: https://docs.codeberg.org/codeberg-pages/using-custom-domain/#setting-the-dns-record |
|
Föderation EN Fr 19.07.2024 21:01:01 @dwm It ends up with cloudflares error with a big cross over host, I think I remember it stating some SSL issue. |
|
Föderation EN Fr 19.07.2024 21:05:35 @tripplehelix When I do a query against your DNS, what I see is: $ dig -t TXT helix.me.uk +short You need to add another TXT record to your DNS with a value like reponame.username.codeberg.page — in your case, I think you probably want to add a TXT record to "helix.me.uk" with the value "terminalthemedwebsite.tripplehelix.codeberg.page". |
|
Föderation EN Fr 19.07.2024 21:17:02 @dwm `terminalthemedwebsite.tripplehelix.codeberg.page` is in the CNAME records, I guess I need to wait for it to propagate? |
|
Föderation EN Fr 19.07.2024 21:20:34 @dwm I've added the TXT record as well, to see what happens. |
|
Föderation EN Fr 19.07.2024 21:26:12 @dwm Shows up in dig, so nope, that didn't fix it. |
|
Föderation EN Fr 19.07.2024 21:37:57 @tripplehelix So, that's looking better, in that you're no-longer getting an HTTP 424 — Codeberg now knows which repository it should be looking in when you go to https://helix.me.uk. However, it's clear that something else is now wrong with the TLS certificate configuration. This is progress, but that wasn't the last hurdle! Looking around, I think Codeberg tries to set up TLS certificates automatically for you with Let's Encrypt. It might just sort itself out with time? |
|
Föderation EN Sa 20.07.2024 03:39:35 @tripplehelix @dwm Perhaps you might need to wait a bit further? ^n |
|
Föderation EN Fr 19.07.2024 20:54:16 @tripplehelix Via what way did you specify what repository should be used for this custom domain? `TXT`, `CNAME` or `ALIAS`. |
|
Föderation EN Fr 19.07.2024 20:58:23 @Gusted I used CNAME. Cloudflare don't seem to have an ALIAS option and the A, AAAA, TXT option fails with an SSL error. |
|
Föderation EN Fr 19.07.2024 21:02:37 @tripplehelix Executing `dig helix.me.uk CNAME` locally yields that there is no CNAME record for this domain. Even weirder if I use cloudflare's DNS resolver it yields the same result. It seems like the CNAME record isn't propagated (or maybe incorrectly configured?) |
|
Föderation EN Fr 19.07.2024 21:04:08 @Gusted Here's all the configured CNAME recods.
(Medien: 1) |
|
Föderation EN Fr 19.07.2024 21:07:05 @Gusted It's definitely pointing to codeberg pages, because this is where the current error is originating from. |
|
Föderation EN Fr 19.07.2024 21:14:55 @tripplehelix It's pointing to Codeberg pages because the A record is configured to the Codeberg pages IP. It's weird https://dnschecker.org/#CNAME/helix.me.uk doesn't show any results either. |
|
Föderation EN Fr 19.07.2024 21:17:51 @Gusted I guess I need to wait for it to propagate then? There's no A record configured, but there was in the recent past. |
|
Föderation EN Fr 19.07.2024 21:09:44 @Gusted Are you using a custom domain on codeberg? Your repo doesn't have a .domains file. |
|
Föderation EN Fr 19.07.2024 21:16:03 @tripplehelix I don't use the Codeberg pages. |
