@oreolek Gitlab.io (CE). I think it might be my understanding of Jekyll? I followed the instructions at https://about.gitlab.com/2016/04/11/tutorial-securing-your-gitlab-pages-with-tls-and-letsencrypt/ but it just won't build the page.

https://gitlab.com/steveivy/steveivy.gitlab.io/blob/master/.well-known/acme-challenge/L-cztDWtEcUrKOWuZZlQ6ELa89rCKX1EEh8dsn582gk

Should be published to:

http://steveivy.gitlab.io/.well-known/acme-challenge/L-cztDWtEcUrKOWuZZlQ6ELa89rCKX1EEh8dsn582gk.html

@sivy i don't know about gitlab.com, but maybe check this out: https://github.com/rolodato/gitlab-letsencrypt

@sivy @oreolek hmm I'm a bit in the dark here, but from the gitlab howto document I don't think the committed-to-git filename is supposed to have ".well-known", but rather the generated page knows where to go because of the permalink: in the front matter. "Just create a file in your blog folder that looks like this: ..."

@stylus @oreolek It depends on the Jekyll version - I need to figure out which version I'm getting.

@oreolek @stylus jekyll 3.3.1, so I should be good with the default setup; let me tweak that.

@stylus @oreolek So, was editing the wrong file, found the right file, but gitlab insists on publishing to "<code>.html" and site 404s on the challenge request for "/<code>"

computer is hard

@sivy @oreolek hmm their example does show the ".html" suffix in the frontmatter's permalink:, weird.

@stylus Yeah, that's what I've been using. The Jekyll build is just not working. I know I've done it before (which is why I'm doing this at all - my cert expired earlier this year)