Stuck at Got response code 404

[tlvdllc]

Wonderful idea for a plugin. Unfortunately, the process hangs even after new commit process has passed —

Got response code 404, waiting 15 seconds...
Got response code 404, waiting 15 seconds...
Got response code 404, waiting 15 seconds...

[JustinAiken]

• Do you have the CI setup to autobuild/deploy your pages on a commit?
• Did the build succeed?
• The plugin should give you the link it's trying to hit - does going to it manually work for you, or is it 404'ing too?
  • It might be a matter of a missing or extra / passed on your pretty permalink options..
  • Or some other way it's set up

If you want to gist more info, I'll be happy to 👀 more into it..

[tlvdllc]

• Yes to autobuild/deploy pages on a commit.
• Yes, build succeeded.
• Ended up going the manual way and not using the plugin, although it will be great it can be resolved by next TLS expiration date.

You can close the ticket for now, or if you like to look into it more I can try and help with debugging.

Thank you Justin.

[jmromer]

I'm seeing 301 redirects

Waiting 120 seconds before we start checking for challenge..
Got response code 301, waiting 15 seconds...
Got response code 301, waiting 15 seconds...
Got response code 301, waiting 15 seconds...
Got response code 301, waiting 15 seconds...
Got response code 301, waiting 15 seconds...
Got response code 301, waiting 15 seconds...
Got response code 301, waiting 15 seconds...
Got response code 301, waiting 15 seconds...
Got response code 301, waiting 15 seconds...
Got response code 301, waiting 15 seconds...
Got response code 301, waiting 15 seconds...
Got response code 301, waiting 15 seconds...
Got response code 301, waiting 15 seconds...
Got response code 301, waiting 15 seconds...
Got response code 301, waiting 15 seconds...
Got response code 301, waiting 15 seconds...
Got response code 301, waiting 15 seconds...
Got response code 301, waiting 15 seconds...

[JustinAiken]

Hmm, try curl -I'ing the url it's trying to get your challenge at... see where it's attempting to redirect to.

[jmromer]

Ah. It's because it's sending a request using http but I have a rule set to redirect all http traffic to https. I modified this to get it working:

jekyll-gitlab-letsencrypt/lib/jekyll/gitlab/letsencrypt/process.rb

Lines 109 to 113 in 3efb9af

	@challenge_url ||= begin
	url = "http:https://#{domain}/"
	url += challenge.filename
	url += "/" if pretty_url?
	url

Thanks!

[JustinAiken]

I have a rule set to redirect all http traffic to https.

How did you do that on Gitlab!?

I modified this to get it working:

See if it looks #3 would allow to use this without local file modifications

[jmromer]

How did you do that on Gitlab!?

I think GitLab might do that automatically for pages served from gitlab.io, but for a custom domain I had to set up cloudflare as my nameserver and set up a page rule:

See if it looks #3 would allow to use this without local file modifications

Thanks!

[JustinAiken]

Pushed out as v0.0.2 - 90 days from now you should be able to just update the gem and your config, without changes!

[jmromer]

Nice! Thanks man 🎉