[{"data":1,"prerenderedAt":206},["ShallowReactive",2],{"docs:\u002Fdocs\u002Fssl\u002Fstates":3},{"id":4,"title":5,"body":6,"description":198,"extension":199,"meta":200,"navigation":201,"path":202,"seo":203,"stem":204,"__hash__":205},"docs\u002Fdocs\u002Fssl\u002Fstates.md","申请状态与失败排查",{"type":7,"value":8,"toc":189},"minimark",[9,19,23,115,123,127,130,178,181,184,186],[10,11,12,13,18],"p",{},"每一条申请在 ",[14,15,17],"a",{"href":16},"\u002Frecord","签发记录页"," 都有一个状态标签,六种状态对应申请生命周期的不同位置。失败不可怕,大多数失败改一次解析就能解决。",[20,21,22],"h2",{"id":22},"状态一览",[24,25,26,42],"table",{},[27,28,29],"thead",{},[30,31,32,36,39],"tr",{},[33,34,35],"th",{},"状态",[33,37,38],{},"含义",[33,40,41],{},"下一步",[43,44,45,57,71,82,93,104],"tbody",{},[30,46,47,51,54],{},[48,49,50],"td",{},"申请中",[48,52,53],{},"申请已创建,等待解析生效或等待你校验",[48,55,56],{},"加好解析后回到申请页点校验",[30,58,59,62,65],{},[48,60,61],{},"申请成功",[48,63,64],{},"证书已签发,可随时下载",[48,66,67],{},[14,68,70],{"href":69},"\u002Fdocs\u002Fssl\u002Fdownload","下载证书",[30,72,73,76,79],{},[48,74,75],{},"申请失败",[48,77,78],{},"签发服务返回错误",[48,80,81],{},"查看签发日志定位原因,重新申请",[30,83,84,87,90],{},[48,85,86],{},"申请超时关闭",[48,88,89],{},"长时间没有完成校验,申请进程被关闭",[48,91,92],{},"重新申请",[30,94,95,98,101],{},[48,96,97],{},"已取消",[48,99,100],{},"你自己点了「终止申请」",[48,102,103],{},"需要时重新申请",[30,105,106,109,112],{},[48,107,108],{},"DNS 校验失败",[48,110,111],{},"校验时解析不通过,最常见",[48,113,114],{},"见下方排查清单",[116,117,120],"callout",{"title":118,"type":119},"失败记录不影响下一次申请","info",[10,121,122],{},"任何失败状态的记录都只是历史,不会占用名额、不会阻塞新申请。改对之后直接重新申请一张即可。",[20,124,126],{"id":125},"dns-校验失败排查清单","DNS 校验失败排查清单",[10,128,129],{},"按命中率从高到低,绝大多数失败落在前两条:",[131,132,133,141,147,166,172],"ol",{},[134,135,136,140],"li",{},[137,138,139],"strong",{},"记录值抄错"," — TXT 值是一长串随机字符,手工敲容易漏字符、带空格。删掉这条记录,从申请页整条复制重加。",[134,142,143,146],{},[137,144,145],{},"解析还没生效"," — 保存成功 ≠ 全网生效。公共解析的缓存几分钟到十几分钟不等,等一等再重新申请;申请页提示「校验暂未开始」时,等解析同步到位再校验即可,申请还留着,不必重来。",[134,148,149,152,153,157,158,161,162,165],{},[137,150,151],{},"主机记录层级不对"," — 给 ",[154,155,156],"code",{},"api.example.com"," 签发时主机记录应是 ",[154,159,160],{},"_acme-challenge.api",",漏了 ",[154,163,164],{},".api"," 就加错了位置。对照申请页的「完整名称」逐级核对。",[134,167,168,171],{},[137,169,170],{},"同名冲突"," — 同一个主机记录下已有别的 TXT\u002FCNAME 记录,校验时读到错误的值。删掉冲突记录或换掉旧值。",[134,173,174,177],{},[137,175,176],{},"托管域名手动加了 TXT"," — 域名已托管时解析由系统代写,手动加的 TXT 会被 CNAME 带走,等于没加。终止申请后重新申请,走系统自动解析。",[20,179,180],{"id":180},"如何查看失败原因",[10,182,183],{},"签发记录页每一条记录都能「查看日志」,日志里保留了校验过程中的查询结果与签发服务的返回信息,失败原因通常直接写在里面。",[20,185,86],{"id":86},[10,187,188],{},"校验环节会等待解析生效,但申请进程不会无限等待:长时间没有完成校验(比如解析一直没加、页面一关好几天),申请会被自动关闭,状态变为「申请超时关闭」。重新申请即可,没有其他副作用。",{"title":190,"searchDepth":191,"depth":191,"links":192},"",3,[193,195,196,197],{"id":22,"depth":194,"text":22},2,{"id":125,"depth":194,"text":126},{"id":180,"depth":194,"text":180},{"id":86,"depth":194,"text":86},"签发记录里六种申请状态(申请中\u002F成功\u002F失败\u002F超时关闭\u002F已取消\u002FDNS 校验失败)的含义,以及校验失败最常见的原因与处理办法。","md",{},true,"\u002Fdocs\u002Fssl\u002Fstates",{"title":5,"description":198},"docs\u002Fssl\u002Fstates","ZfxMsgANWWLcXa-TCLgNcY_jXtRkKwbEPhi4hyUzqxs",1793537574519]