Paths

Table of Contentst

Serve Let's Encrypt validation directory in TLS too
ClosedPublic
Actions

Authored by dereckson on Jun 18 2018, 23:49.

Tags

None

Referenced Files

	F7094235: D1646.id4199.diff
	Sun, Apr 20, 15:03

	F7094016: D1646.id4200.diff
	Sun, Apr 20, 15:00

	F7093450: D1646.id.diff
	Sun, Apr 20, 14:48

	Unknown Object (File)
	Sat, Apr 19, 11:32

	Unknown Object (File)
	Fri, Apr 11, 16:19

	Unknown Object (File)
	Fri, Apr 11, 09:40

	Unknown Object (File)
	Fri, Apr 11, 04:58

	Unknown Object (File)
	Thu, Apr 10, 06:28

View All Files

Subscribers

None

Details

Reviewers

dereckson

Commits

rOPSc61bd8b2e5c8: Serve Let's Encrypt validation directory in TLS too

Summary

Let's Encrypt tries to validate challenges at https://, not at http://
so the .well-known/acme-challenge/ folder must be available in TLS too.

Test Plan

certbot renew

Diff Detail

Repository

rOPS Nasqueron Operations

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

dereckson requested review of this revision.Jun 18 2018, 23:49

dereckson created this revision.

Harbormaster completed remote builds in B2580: Diff 4199.Jun 18 2018, 23:49

dereckson accepted this revision.Jun 18 2018, 23:50

This revision is now accepted and ready to land.Jun 18 2018, 23:50

Closed by commit rOPSc61bd8b2e5c8: Serve Let's Encrypt validation directory in TLS too (authored by dereckson). · Explain WhyJun 18 2018, 23:50

This revision was automatically updated to reflect the committed changes.

Revision Contents
Changeset List

Path

Size

roles/

webserver-legacy/

nginx/

files/

vhosts/

wolfplex.org/

api.conf

4 lines

www.conf

2 lines

Diff 4200

View Options

roles/webserver-legacy/nginx/files/vhosts/wolfplex.org/api.conf