TLS does not setup with pages deploy

Pages
1

I have a similar problem to this user. Difficulty with Pages deploy

Pages is deployed per codefloe docs as https://codefloe.com/l10n-swedish/fri-som-i-frihet/src/branch/pages

Pages is enabled, and static host is https://codefloe.com/l10n-swedish/fri-som-i-frihet/src/branch/pages/statichost.yml (it’s prebuilt).

I would expect it to end up at https://fri-som-i-frihet.l10n-swedish.codefloe.page/ but seems certs does not get generated. I tried disable and enable pages on the repo if there was a hickup somewhere.

Did some error hunting,:
$ dig +short CNAME fri-som-i-frihet.l10n-swedish.codefloe.page
codefloe.statichost.page. V

$ dig +short A fri-som-i-frihet.l10n-swedish.codefloe.page
codefloe.statichost.page.
sites.statichost.eu.
77.42.79.144
Great

$ curl -sS -o /dev/null -D - http://fri-som-i-frihet.l10n-swedish.codefloe.page/
HTTP/1.1 308 Permanent Redirect
Location: https://fri-som-i-frihet.l10n-swedish.codefloe.page/
Server: Caddy
GREAT

$ curl -sSI https://fri-som-i-frihet.l10n-swedish.codefloe.page/
curl: (35) OpenSSL/3.0.13: error:0A000438:SSL routines::tlsv1 alert internal error
Ouch.

This a subrepo to an org, does that matter - codefloe docs only show user repo example.

(If you look at repo, you will also find a more straightforward dns link, l10n.se, that is still pointing to the old codeberg pages host). Thanks for any help.

2

Ah, read this too now, Loading pages does not work due to ERR_SSL_PROTOCOL_ERROR - #3 by milos.kroulik and I see, there are still loose ends to pages support in codefloe. Oki, will think about how to go about.

3

@hanklank We’ve now added build log support to pages.

Besides that, we also had a closer look on your specific case. It currently looks like that the SHA-256 repo type is the issue (SH chokes on these, likely due to a non-compatible git binary).

The most likely fix (for now) is to use a “normal” SHA1 repo and see if that fixes it. If you go with that, you can now also inspect the build logs and hopefully should be able to get a successful deployment going!

4

Again, Thanks for looking into the issue, and for fixing a feature that will benefit all users. Ah, I solved it with using another Static page provider this time around, but will send a report to SH anyway so they get a chance to solve it if they wish, for someone else in the future. I know sha256 is not too common yet, but It will be the default (or so i read at least), in new Git 3, out. in a not to far future, so I started using it for new repos. Afa as I know, GitHub does not support it yet, but most other forges, forgejo, gitlab at least. Tooling is a mixed area. Support for SHA256 · Issue #706 · go-git/go-git · GitHub