|
· 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 |
