大网数据广告活动
服务器运维问答

Let’s Encrypt Certbot: How to use HTTPS for the server validation

· 52CE 我爱测

When using Let’s Encrypt Certbot, the Let’s Encrypt server makes a HTTP request to the temporary file on the web server to validate that the requested domain resolves to the server where certbot runs. However, my provider blocks …

问题原文

原帖链接 · Nasu Altercho · CC BY-SA 4.0

When using Let’s Encrypt Certbot, the Let’s Encrypt server makes a HTTP request to the temporary file on the web server to validate that the requested domain resolves to the server where certbot runs.

However, my provider blocks port 80 in its firewall and will not open it, not even temporarily. Neither can I use DNS validation, because I cannot edit the DNS record.

(How) Can I use the Let’s Encrypt validation process over https (with Apache listening on Port 443 with a self-signed certificate) instead of over http?

已采纳解答

原帖链接 · Henrik Pingel · CC BY-SA 4.0

Letsencrypt recommends to keep port 80 open:

Allowing port 80 doesn’t introduce a larger attack surface on your server, because requests on port 80 are generally served by the same software that runs on port 443.

But they got this scenario covered:

Unfortunately, you might not have control over whether port 80 is blocked for your site. Some (mostly residential) ISPs block port 80 for various reasons. If your ISP does this but you’d still like to get certificates from Let’s Encrypt, you have two options: You can use DNS-01 challenges or you can use one of the clients that supports TLS-ALPN-01 challenges (on port 443).

So the recommended way is to use tls-alpn-challenge

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2020-05-04)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。