[GH-ISSUE #9] Error in ALPN protocol (with Cloudflare?) #1

Open
opened 2026-03-04 14:56:09 +03:00 by kerem · 1 comment
Owner

Originally created by @Minipada on GitHub (Mar 17, 2021).
Original GitHub issue: https://github.com/futurice/alley-oop/issues/9

Hi, thanks for the project and the education video 😉 .
I'm trying to set it up with Cloudflare but I keep getting this message (I replaced my domain by example.com):

WaitAuthorization error: acme: authorization error for alley-oop.example.com: 403 urn:ietf:params:acme:error:unauthorized: Cannot negotiate ALPN protocol "acme-tls/1" for tls-alpn-01 challenge

I use the DNS only option, non proxied by Cloudflare, which should let the server handle the negociation.
In /var/lib/alley-oop, I have 4 files:

CERT-acme_account+key
CERT-alley-oop.example.com+rsa
CERT-alley-oop.example.com
IPS-172-17-0-4.lan.example.com

I am not sure on how to debug this. I don't know if it's a cloudflare specific issue or how I could trace it. Any hint would be welcome. Thank you!

Originally created by @Minipada on GitHub (Mar 17, 2021). Original GitHub issue: https://github.com/futurice/alley-oop/issues/9 Hi, thanks for the project and the education video :wink: . I'm trying to set it up with Cloudflare but I keep getting this message (I replaced my domain by example.com): ``` WaitAuthorization error: acme: authorization error for alley-oop.example.com: 403 urn:ietf:params:acme:error:unauthorized: Cannot negotiate ALPN protocol "acme-tls/1" for tls-alpn-01 challenge ``` I use the DNS only option, non proxied by Cloudflare, which should let the server handle the negociation. In /var/lib/alley-oop, I have 4 files: CERT-acme_account+key CERT-alley-oop.example.com+rsa CERT-alley-oop.example.com IPS-172-17-0-4.lan.example.com I am not sure on how to debug this. I don't know if it's a cloudflare specific issue or how I could trace it. Any hint would be welcome. Thank you!
Author
Owner

@Minipada commented on GitHub (Mar 18, 2021):

Update: I reserved a new domain name on route53, which doesn't go through Cloudflare, created a self signed key for the domain following the link example but still get the same error.

<!-- gh-comment-id:801784069 --> @Minipada commented on GitHub (Mar 18, 2021): Update: I reserved a new domain name on route53, which doesn't go through Cloudflare, created a self signed key for the domain following the link example but still get the same error.
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/alley-oop#1
No description provided.