无法生成令

发布于 2025-02-07 01:44:10 字数 4589 浏览 4 评论 0 原文

我正在使用Laravel Forge来管理我的服务器和网站。因此,通过让我们加密生成SSL证书也是Vie Forge的。不知何故,我的域之一给我带来了一个错误(请参阅附件)。

该域在拥有其他几个域的服务器上运行。 NGINX配置完全相同。

该应用程序是在Laravel Octane上运行的Laravel应用程序。

错误:

2022-06-13 10:41:26 URL:? env =生产[4653] - > “ letsencrypt_script1655109686” [1]克隆 进入“ letsencrypt1655109686'...注意:切换到 '91CCCC0C234E4DECF0A19595FA19A6F306788032'。

您处于“独立头”状态。你可以环顾四周 实验性更改并提交它们,您可以丢弃任何提交 您在这种状态下不通过切换而不会影响任何分支机构 返回分支。

如果您想创建一个新的分支来保留您创建的提交,则 可以(现在或以后)使用-c与switch命令一起使用。示例:

git开关-c

或以:

撤消此操作

git开关 -

通过设置配置变量建议关闭此建议。 false

头现在位于91cccc0 openssl.cnf错误:挑战无效! (返回:无效)(结果: [“ type”]“ http-01” [“状态”]“无效” [“错误”,“ type”]“ urn:ietf:params:acme:error:connection” [“错误”,“详细”]“ 111.222.333.444:提取 : 连接期间的超时(可能的防火墙问题)” [“错误”,“状态”] 400 [“ error”] {“ type”:“ urn:ietf:params:acme:error:rorry:connection”,“详细信息”:“ 111.222.333.444: 提取 : 连接期间超时(可能的防火墙问题)”,“状态”:400} [“ url”]” https://acme-v02.api.letsencrypt.org/acme/chall-v3/119151352296/awzdug” [“ token”]“ _BL98LTVQMOEJG-NCELZL2Z3VWUM7EJBA1I6IEBDULW” [“验证记录”,0,“ url”]” http://www.my-domain.de/.well-nown/acme-challenge/_bl98ltvqmoejg-ncell2z3vwum7ejbaba1i6iebdulw' [“验证记录”,0,“主机名”]“ www.my-domain.de” [“验证记录”,0,“端口”]“ 80” [“验证记录”,0,“ addressessolved”,0]“ 111.222.333.444” [“验证记录”,0,“ adverseSessolved”,1]“ 2A01:4F8:141:333 :: 84” [“验证记录”,0,“ adverseesSolved”] [“ 111.222.333.444”,“ 2A01:4F8:141:333 :: 84”] [“验证记录”,0,“地址”]” 2A01:4F8:141:333 :: 84” [“ verationRecord”,0] {“ url”:“ http://www.my-domain.de/.well-nown/acme-challenge/_bl98ltvqmoejg-ncell2z3vwum7ejba1ijba1i6ie6ie6iebdulw' de“,“ port”:“ 80”,“ adverseSesolved”:[“ 111.222.333.444”,“ 2A01:4F8:141:333 :: 84”],“地址”,“ 2A01:” 2A01:4F8:141:333 ::::: ::::::::: 84“} [“ validationRecord”,1,“ url”]” http://www.my-domain.de/.well-nown/acme-challenge/_bl98ltvqmoejg-ncell2z3vwwum7ejba1ijba1i6ie6iebdulw' [“验证记录”,1,“主机名”]“ www.my-domain.de” [“验证记录”,1,“端口”]“ 80” [“验证记录”,1,“ addressessolved”,0]“ 111.222.333.444” [“验证记录”,1,“ adverseSessolved”,1]“ 2A01:4F8:141:333 :: 84” [“ verationRecord”,1,“ addressessolved”] [“ 111.222.333.444”,“ 2A01:4F8:141:333 :: 84”] [“验证记录”,1,“地址”]“ 111.222.333.444” [“ verationRecord”,1] {“ url”:“ http://www.my-domain.de/.well-nown/acme-challenge/_bl98ltvqmoejg-ncell2z3vwum7ejba1ijba1i6ie6ie6iebdulw' de“,“ port”:“ 80”,“ addressessolved”:[“ 111.222.333.444”,“ 2A01:4F8:141:333 :: 84”],“地址”,“ 111.222.333.444”} [“验证记录”,2,“ url”]“ http://my-domain.de/.well-nown/acme-challenge/_bl98ltvqmoejg-ncelzl2z3vwum7ejba1ijba1i6iebdulw” [“验证记录”,2,“主机名”]“ my-domain.de” [“验证记录”,2,“端口”]“ 80” [“验证记录”,2,“ addressessolved”,0]“ 111.222.333.444” [“验证记录”,2,addressessolved”,1]“ 2A01:4F8:141:333 :: 84” [“验证记录”,2,addressessolved”] [“ 111.222.333.444”,“ 2A01:4F8:141:333 :: 84”] [“验证记录”,2,“寻址”]” 2A01:4F8:141:333 :: 84” [“ verationRecord”,2] {“ url”:“ http://my-domain.de/.well-nown/acme-challenge/_bl98ltvqmoejg-ncell2z3vwum7ejba1i6ie6iebdulw”端口“:“ 80”,“ addressessolved”:[“ 111.222.333.444”,“ 2A01:4F8:141:333 ::::: 84”],“地址”:“ 2A01:4F8:141:141:333 :: 84} [} [} [} [} [} [} [} [} [} [ “验证记录”] ,“ port”:“ 80”,“地址水解”:[“ 111.222.333.444”,“ 2A01:4F8:141:333 :: 84”],“地址”,“ 2A01:4F8:141:141:333 :: 84” },{“ url”:“ http://www.my-domain.de/.well-nown/acme-challenge/_bl98ltvqmoejg-ncelzl2z3vwum7ejba1i6ie6iebdulw” “:“ 80”,“ adverseSersolved”:[“ 111.222.333.444”,“ 2A01:4F8:141:333 ::: 84”],“地址”:“ 111.222.333.444444444”}, //my-domain.de/.well-known/acme-challenge/_bL98lTvqMOeJG-NCeLzl2Z3VWUm7EJBa1i6IEBDuLw","hostname":"my-domain.de","port":"80","addressesResolved":["111.222. 333.444“,” 2A01:4F8:141:333 :: 84“],“地址”:“ 2A01:4F8:141:333 :: 84”}] [“验证” 2022-2-06-13T08:41:41:47Z ”)

I am using Laravel Forge to manage my servers and websites. So generating SSL certificates via Let's Encrypt is also done vie Forge. Somehow one of my domains throws me an error (see attached).

This domain is running on a server which holds several other domains. The nginx configuration is exactly the same.

The application is a Laravel app running on Laravel Octane.

Error:

2022-06-13 10:41:26 URL:https://forge-certificates.laravel.com/le/1441847/1663342/ecdsa?
env=production [4653] -> "letsencrypt_script1655109686" [1] Cloning
into 'letsencrypt1655109686'... Note: switching to
'91cccc0c234e4decf0a19595fa19a6f306788032'.

You are in 'detached HEAD' state. You can look around, make
experimental changes and commit them, and you can discard any commits
you make in this state without impacting any branches by switching
back to a branch.

If you want to create a new branch to retain commits you create, you
may do so (now or later) by using -c with the switch command. Example:

git switch -c

Or undo this operation with:

git switch -

Turn off this advice by setting config variable advice.detachedHead to
false

HEAD is now at 91cccc0 ensure newline before new section in
openssl.cnf ERROR: Challenge is invalid! (returned: invalid) (result:
["type"] "http-01" ["status"] "invalid"
["error","type"] "urn:ietf:params:acme:error:connection"
["error","detail"] "111.222.333.444: Fetching
http://my-domain.de/.well-known/acme-challenge/_bL98lTvqMOeJG-NCeLzl2Z3VWUm7EJBa1i6IEBDuLw:
Timeout during connect (likely firewall problem)"
["error","status"] 400
["error"] {"type":"urn:ietf:params:acme:error:connection","detail":"111.222.333.444:
Fetching
http://my-domain.de/.well-known/acme-challenge/_bL98lTvqMOeJG-NCeLzl2Z3VWUm7EJBa1i6IEBDuLw:
Timeout during connect (likely firewall problem)","status":400}
["url"] "https://acme-v02.api.letsencrypt.org/acme/chall-v3/119151352296/awZDUg"
["token"] "_bL98lTvqMOeJG-NCeLzl2Z3VWUm7EJBa1i6IEBDuLw"
["validationRecord",0,"url"] "http://www.my-domain.de/.well-known/acme-challenge/_bL98lTvqMOeJG-NCeLzl2Z3VWUm7EJBa1i6IEBDuLw"
["validationRecord",0,"hostname"] "www.my-domain.de"
["validationRecord",0,"port"] "80"
["validationRecord",0,"addressesResolved",0] "111.222.333.444"
["validationRecord",0,"addressesResolved",1] "2a01:4f8:141:333::84"
["validationRecord",0,"addressesResolved"] ["111.222.333.444","2a01:4f8:141:333::84"]
["validationRecord",0,"addressUsed"] "2a01:4f8:141:333::84"
["validationRecord",0] {"url":"http://www.my-domain.de/.well-known/acme-challenge/_bL98lTvqMOeJG-NCeLzl2Z3VWUm7EJBa1i6IEBDuLw","hostname":"www.my-domain.de","port":"80","addressesResolved":["111.222.333.444","2a01:4f8:141:333::84"],"addressUsed":"2a01:4f8:141:333::84"} ["validationRecord",1,"url"] "http://www.my-domain.de/.well-known/acme-challenge/_bL98lTvqMOeJG-NCeLzl2Z3VWUm7EJBa1i6IEBDuLw"
["validationRecord",1,"hostname"] "www.my-domain.de"
["validationRecord",1,"port"] "80"
["validationRecord",1,"addressesResolved",0] "111.222.333.444"
["validationRecord",1,"addressesResolved",1] "2a01:4f8:141:333::84"
["validationRecord",1,"addressesResolved"] ["111.222.333.444","2a01:4f8:141:333::84"]
["validationRecord",1,"addressUsed"] "111.222.333.444"
["validationRecord",1] {"url":"http://www.my-domain.de/.well-known/acme-challenge/_bL98lTvqMOeJG-NCeLzl2Z3VWUm7EJBa1i6IEBDuLw","hostname":"www.my-domain.de","port":"80","addressesResolved":["111.222.333.444","2a01:4f8:141:333::84"],"addressUsed":"111.222.333.444"}
["validationRecord",2,"url"] "http://my-domain.de/.well-known/acme-challenge/_bL98lTvqMOeJG-NCeLzl2Z3VWUm7EJBa1i6IEBDuLw"
["validationRecord",2,"hostname"] "my-domain.de"
["validationRecord",2,"port"] "80"
["validationRecord",2,"addressesResolved",0] "111.222.333.444"
["validationRecord",2,"addressesResolved",1] "2a01:4f8:141:333::84"
["validationRecord",2,"addressesResolved"] ["111.222.333.444","2a01:4f8:141:333::84"]
["validationRecord",2,"addressUsed"] "2a01:4f8:141:333::84"
["validationRecord",2] {"url":"http://my-domain.de/.well-known/acme-challenge/_bL98lTvqMOeJG-NCeLzl2Z3VWUm7EJBa1i6IEBDuLw","hostname":"my-domain.de","port":"80","addressesResolved":["111.222.333.444","2a01:4f8:141:333::84"],"addressUsed":"2a01:4f8:141:333::84"} ["validationRecord"] [{"url":"http://www.my-domain.de/.well-known/acme-challenge/_bL98lTvqMOeJG-NCeLzl2Z3VWUm7EJBa1i6IEBDuLw","hostname":"www.my-domain.de","port":"80","addressesResolved":["111.222.333.444","2a01:4f8:141:333::84"],"addressUsed":"2a01:4f8:141:333::84"},{"url":"http://www.my-domain.de/.well-known/acme-challenge/_bL98lTvqMOeJG-NCeLzl2Z3VWUm7EJBa1i6IEBDuLw","hostname":"www.my-domain.de","port":"80","addressesResolved":["111.222.333.444","2a01:4f8:141:333::84"],"addressUsed":"111.222.333.444"},{"url":"http://my-domain.de/.well-known/acme-challenge/_bL98lTvqMOeJG-NCeLzl2Z3VWUm7EJBa1i6IEBDuLw","hostname":"my-domain.de","port":"80","addressesResolved":["111.222.333.444","2a01:4f8:141:333::84"],"addressUsed":"2a01:4f8:141:333::84"}] ["validated"] "2022-06-13T08:41:47Z")

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

水晶透心 2025-02-14 01:44:10

我终于找到了解决方案。 Laravel Forge不支持开箱即用的IPv6。因此,您要么必须配置Forge也使用IPv6,要么删除指向Laravel Forge管理的服务器的所有AAAA记录。

I've finally found the solution. Laravel Forge does not support IPv6 out of the box. So you either have to configure Forge to use IPv6 as well or remove all AAAA records pointing to the server managed by Laravel Forge.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文