Challenge-Responder not launching in Nomad TLS environment about aleff

[stut]

Thanks for the report. I'm sorry it's taking a while for me to look at this. My test cluster does not use TLS so I'm not currently able to debug the issue, but it will as soon as I can find the time to implement it.

[stut]

I am struggling to reproduce this issue. Can you provide any further information?

What I find curious is that the error you're seeing is coming from the acme module which is what talks to Let's Encrypt so I'm not convinced your issue is to do with TLS but without being able to reproduce it I can't be certain.

[trissman]

Stuart, Unfortunately, I can't provide much additional information, but I think you are right. I concluded it was TLS that was causing this behavior because I didn't see it when I turned TLS off and then saw it again when I turned TLS on. I then saw similar behavior from Caddy and figured out that when Let's Encrypt uses its TLS algorithm (and not just plain HTTP), there needs to be a 1-to-1 NAT in place through the firewall and not just the port opened by the firewall for responses. With 1-to-1 NAT, Caddy works as expected. I have not gone back to Aleff since I put the Caddy solution in place, but my guess is that this would have fixed Aleff too. My apologies for not updating you earlier. Tom CONTACT INFORMATION Thomas W. Rissman McLachlan, Rissman & Doll 676 N. Michigan Avenue, Suite 2800 Chicago, IL 60611 Tel: [phone] Fax: [phone] email: ***@***.*** From: "Stuart Dallas" ***@***.***> To: "stut/aleff" ***@***.***> Cc: "trissman" ***@***.***>, "Author" ***@***.***> Date: 07/21/2023 03:09 PM Subject: Re: [stut/aleff] Challenge-Responder not launching in Nomad TLS environment (Issue #16) I am struggling to reproduce this issue. Can you provide any further information? What I find curious is that the error you're seeing is coming from the acme module which is what talks to Let's Encrypt so I'm not convinced your issue is to do with TLS but without being able to reproduce it I can't be certain. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>