Support for HTTP-01 Challenge over Port 443 with Self-Signed Certificate (for Port 80-Blocked Environments)

MikeMcQ · July 16, 2025, 9:13pm

Just curious why it would. Requests inbound on port 443 get seen first by the uacme proxy handler. If it is a TLS-ALPN request it processes it. If it is not it passes it unchanged to nginx on some other port. Front-end proxies often proxy to backend servers on alternate ports.

Topic		Replies	Views
Is there a reason that the challenge can't be over port 443? Feature Requests	7	5273	November 12, 2017
Chicken-or-egg on port 443 vs 80 on challenge Help	26	294	January 1, 2025
Automatically try replacing http with https in ACME challenge? Feature Requests	9	2624	May 26, 2022
Acme challenges over HTTPS Feature Requests	38	12576	April 10, 2022
Standalone http-01 challenge worked on port 8080 in past, but now it does not work Server	5	8092	April 10, 2017

Support for HTTP-01 Challenge over Port 443 with Self-Signed Certificate (for Port 80-Blocked Environments)

Related topics