[{"data":1,"prerenderedAt":1059},["ShallowReactive",2],{"navigation_docs_zh_cn":3,"-zh-cn-pml-2-troubleshooting":75,"-zh-cn-pml-2-troubleshooting-surround":1054},[4,26],{"title":5,"path":6,"stem":7,"children":8,"page":25},"PML 2 插件开发指南","\u002Fzh_cn\u002Fpml-2-plugin","zh_cn\u002Fpml-2-plugin",[9,13,17,21],{"title":10,"path":11,"stem":12},"插件开发综述","\u002Fzh_cn\u002Fpml-2-plugin\u002Fintro","zh_cn\u002Fpml-2-plugin\u002F01.intro",{"title":14,"path":15,"stem":16},"插件系统埋点说明","\u002Fzh_cn\u002Fpml-2-plugin\u002Ftriggers","zh_cn\u002Fpml-2-plugin\u002F02.triggers",{"title":18,"path":19,"stem":20},"插件系统运算符说明","\u002Fzh_cn\u002Fpml-2-plugin\u002Foperators","zh_cn\u002Fpml-2-plugin\u002F03.operators",{"title":22,"path":23,"stem":24},"内置函数","\u002Fzh_cn\u002Fpml-2-plugin\u002Ffunctions","zh_cn\u002Fpml-2-plugin\u002F04.functions",false,{"title":27,"path":28,"stem":29,"children":30,"page":25},"PML 2","\u002Fzh_cn\u002Fpml-2","zh_cn\u002Fpml-2",[31,35,39,43,47,51,55,59,63,67,71],{"title":32,"path":33,"stem":34},"介绍 & 下载","\u002Fzh_cn\u002Fpml-2\u002Fintro","zh_cn\u002Fpml-2\u002F01.intro",{"title":36,"path":37,"stem":38},"安装","\u002Fzh_cn\u002Fpml-2\u002Finstall","zh_cn\u002Fpml-2\u002F02.install",{"title":40,"path":41,"stem":42},"用户指南","\u002Fzh_cn\u002Fpml-2\u002Fuser_guide","zh_cn\u002Fpml-2\u002F03.user_guide",{"title":44,"path":45,"stem":46},"故障排查","\u002Fzh_cn\u002Fpml-2\u002Ftroubleshooting","zh_cn\u002Fpml-2\u002F04.troubleshooting",{"title":48,"path":49,"stem":50},"配置文件","\u002Fzh_cn\u002Fpml-2\u002Fconfig","zh_cn\u002Fpml-2\u002F05.config",{"title":52,"path":53,"stem":54},"主题","\u002Fzh_cn\u002Fpml-2\u002Fthemes","zh_cn\u002Fpml-2\u002F06.themes",{"title":56,"path":57,"stem":58},"插件开发指南","\u002Fzh_cn\u002Fpml-2\u002Fplugin","zh_cn\u002Fpml-2\u002F07.plugin",{"title":60,"path":61,"stem":62},"PML 2 隐私政策","\u002Fzh_cn\u002Fpml-2\u002Fpolicy","zh_cn\u002Fpml-2\u002F08.policy",{"title":64,"path":65,"stem":66},"PML 2 用户协议","\u002Fzh_cn\u002Fpml-2\u002Fuser_agreement","zh_cn\u002Fpml-2\u002F09.user_agreement",{"title":68,"path":69,"stem":70},"DNS 提供商","\u002Fzh_cn\u002Fpml-2\u002Fdns_providers","zh_cn\u002Fpml-2\u002F10.dns_providers",{"title":72,"path":73,"stem":74},"遥测","\u002Fzh_cn\u002Fpml-2\u002Ftelemetry","zh_cn\u002Fpml-2\u002F11.telemetry",{"id":76,"title":44,"body":77,"description":1047,"extension":1048,"links":1049,"meta":1050,"navigation":1051,"path":45,"seo":1052,"stem":46,"__hash__":1053},"docs_zh_cn\u002Fzh_cn\u002Fpml-2\u002F04.troubleshooting.md",{"type":78,"value":79,"toc":1015},"minimark",[80,85,96,100,103,192,195,199,206,212,228,232,237,241,280,284,289,293,312,316,321,325,343,347,352,356,364,366,369,377,379,383,398,403,422,426,450,454,457,547,552,556,622,625,653,655,659,663,690,693,706,708,711,714,719,723,731,735,740,744,766,770,775,779,809,811,815,822,832,847,850,910,915,918,948,952],[81,82,84],"h1",{"id":83},"故障排查指南-隧道启动失败","故障排查指南 (隧道启动失败)",[86,87,88],"blockquote",{},[89,90,91,92,95],"p",{},"本文档配合 ",[93,94,40],"a",{"href":41},"「隧道状态与失败原因」章节使用。当隧道卡片显示红色「失败」状态时, 先点卡片上的「复制错误信息」拿到失败摘要, 再按下述路径排查。",[97,98,99],"h2",{"id":99},"常见失败类别",[89,101,102],{},"启动失败会被映射为以下几类 (卡片上直接显示可读文案, 非原始日志):",[104,105,106,122],"table",{},[107,108,109],"thead",{},[110,111,112,116,119],"tr",{},[113,114,115],"th",{},"类别",[113,117,118],{},"典型触发条件",[113,120,121],{},"排查方向",[123,124,125,148,159,170,181],"tbody",{},[110,126,127,131,145],{},[128,129,130],"td",{},"认证失败",[128,132,133,134,138,139,138,142],{},"token \u002F 登录态异常, 服务端返回 ",[135,136,137],"code",{},"401"," \u002F ",[135,140,141],{},"unauthorized",[135,143,144],{},"auth failed",[128,146,147],{},"见下方 §1",[110,149,150,153,156],{},[128,151,152],{},"端口占用",[128,154,155],{},"远程端口或本地端口被其他进程占用",[128,157,158],{},"见下方 §2",[110,160,161,164,167],{},[128,162,163],{},"节点不可达",[128,165,166],{},"节点连接被拒、域名无法解析、启动后 30 秒无在线确认",[128,168,169],{},"见下方 §3",[110,171,172,175,178],{},[128,173,174],{},"进程崩溃",[128,176,177],{},"mefrpc 进程异常退出 (退出码非 0)",[128,179,180],{},"见下方 §4",[110,182,183,186,189],{},[128,184,185],{},"未知",[128,187,188],{},"不属于以上任何一类的错误",[128,190,191],{},"见下方 §5",[193,194],"hr",{},[97,196,198],{"id":197},"_1-认证失败","§1 认证失败",[89,200,201,205],{},[202,203,204],"strong",{},"表现",": 失败摘要含「认证失败 \u002F token 无效 \u002F 未授权」等字样, 或服务端返回 401。",[89,207,208,211],{},[202,209,210],{},"排查路径",":",[213,214,215,219,222,225],"ol",{},[216,217,218],"li",{},"重新登录一次 (退出账号后重新登录, 刷新本地 token), 再启动隧道。",[216,220,221],{},"确认账号仍有该隧道的使用权限 (节点是否停用、账号是否欠费\u002F封禁)。",[216,223,224],{},"若频繁出现, 检查系统时间是否正确 (偏差过大会导致 token 签名校验失败)。",[216,226,227],{},"仍失败: 复制错误信息并附上账号节点信息提交反馈。",[97,229,231],{"id":230},"_2-端口占用","§2 端口占用",[89,233,234,236],{},[202,235,204],{},": 失败摘要含「端口被占用 \u002F address already in use」等字样。",[89,238,239,211],{},[202,240,210],{},[213,242,243,250,277],{},[216,244,245,246,249],{},"确认",[202,247,248],{},"远程端口","没有被其他隧道占用 (同一节点的同一远程端口只能分配给一条隧道)。",[216,251,245,252,255,256],{},[202,253,254],{},"本地端口","没有被本机其他程序占用 (如 80 端口被 IIS\u002Fnginx 等占用)。\n",[257,258,259,266],"ul",{},[216,260,261,262,265],{},"Windows: ",[135,263,264],{},"netstat -ano | findstr :端口号"," 查看占用进程。",[216,267,268,269,272,273,276],{},"Linux\u002FmacOS: ",[135,270,271],{},"lsof -i :端口号"," 或 ",[135,274,275],{},"ss -ltnp | grep 端口号","。",[216,278,279],{},"占用确认后: 停掉占用程序, 或在创建\u002F编辑隧道时更换端口。",[97,281,283],{"id":282},"_3-节点不可达","§3 节点不可达",[89,285,286,288],{},[202,287,204],{},": 失败摘要含「无法连接 \u002F 连接被拒绝 \u002F 节点不可达」, 或启动后 30 秒无在线确认 (超时)。",[89,290,291,211],{},[202,292,210],{},[213,294,295,306,309],{},[216,296,297,298],{},"使用隧道管理页的「刷新测速」确认该节点是否可达 (延迟\u002F超时\u002F失败)。\n",[257,299,300,303],{},[216,301,302],{},"超时: 节点过载或网络波动, 稍后重试, 或换一个节点。",[216,304,305],{},"失败 (连接被拒): 节点可能下线或未开放该端口。",[216,307,308],{},"检查本机网络: 能否正常访问其他网站\u002F服务; 代理\u002FVPN 是否干扰了到节点的连接。",[216,310,311],{},"检查本机防火墙\u002F安全软件是否拦截了 mefrpc 出站连接。",[97,313,315],{"id":314},"_4-进程崩溃","§4 进程崩溃",[89,317,318,320],{},[202,319,204],{},": 失败摘要含「进程异常退出 (退出码 N)」等字样。",[89,322,323,211],{},[202,324,210],{},[213,326,327,330,333,340],{},[216,328,329],{},"确认 mefrpc 版本是否与当前节点服务端兼容 (更新页可查看最新版本; 必要时重新下载客户端)。",[216,331,332],{},"查看崩溃前终端输出: 在终端页手动执行同样的启动命令, 观察报错点。",[216,334,335,336,339],{},"配置文件损坏时也会导致崩溃: 删除 ",[135,337,338],{},"Config\u002Ffrp"," 下对应的临时配置后重试。",[216,341,342],{},"仍崩溃: 复制错误信息 (含退出码), 提交反馈。",[97,344,346],{"id":345},"_5-未知错误","§5 未知错误",[89,348,349,351],{},[202,350,204],{},": 失败摘要为原始 API 错误信息。",[89,353,354,211],{},[202,355,210],{},[213,357,358,361],{},[216,359,360],{},"摘要通常已包含服务端返回的原始信息, 可据此关键词搜索或直接反馈。",[216,362,363],{},"将「复制错误信息」的内容 (应用版本 + mefrpc 版本 + 摘要) 完整粘贴到反馈中。",[193,365],{},[97,367,368],{"id":368},"通用建议",[257,370,371,374],{},[216,372,373],{},"反馈问题前, 一律使用卡片上的「复制错误信息」, 内容包含应用版本与 mefrpc 版本, 能大幅加快定位。",[216,375,376],{},"修改网络环境 (代理、DNS、防火墙) 后, 重新「刷新测速」验证节点连通性, 再尝试启动。",[193,378],{},[97,380,382],{"id":381},"证书申请失败-264","证书申请失败 (26.4)",[89,384,385,386,389,390,393,394,397],{},"「证书助手」基于 lego 的 DNS-01 流程, 有",[202,387,388],{},"两种验证方式"," (见用户指南「证书助手 → 验证方式」): ",[202,391,392],{},"DNS 账户 (一键自动)"," 由应用调用 DNS 服务商 API 自动读写 TXT 记录; ",[202,395,396],{},"手动 DNS"," 由您自行添加 TXT 记录。",[399,400,402],"h3",{"id":401},"lego-下载失败-无法准备证书组件","lego 下载失败 (无法准备证书组件)",[257,404,405,410,416],{},[216,406,407,409],{},[202,408,204],{},": 点「开始申请」后长时间停留在「正在准备 lego…」, 或直接提示「无法准备证书组件 lego (下载或校验失败)」。",[216,411,412,415],{},[202,413,414],{},"原因",": 网络无法访问 GitHub (主源) 与备用镜像, 或下载内容校验不通过。",[216,417,418,421],{},[202,419,420],{},"处理",": 确认网络与代理后重试; 应用会依次尝试主源与备用源, 校验失败通常意味着下载不完整, 重试即可。若始终不可用, 可改用「手动 DNS」模式 (仍需 lego, 仅验证方式不同)。",[399,423,425],{"id":424},"手动-dns-一直停留在请添加-txt-记录后继续","手动 DNS: 一直停留在「请添加 TXT 记录后继续」",[257,427,428,438,447],{},[216,429,430,433,434,437],{},[202,431,432],{},"这是正常等待状态"," (",[202,435,436],{},"仅手动模式","有这一步): 应用在等您到 DNS 服务商添加 TXT 记录, 不会自动超时。",[216,439,440,442,443,446],{},[202,441,420],{},": 复制窗口中的「记录主机」与「记录值」到 DNS 控制台 (类型选 ",[135,444,445],{},"TXT","), 保存后点窗口上的「我已添加」。",[216,448,449],{},"若误关闭窗口, 本次申请会被取消 (lego 进程被终止), 重新申请即可。",[399,451,453],{"id":452},"dns-账户-一键自动-模式失败","DNS 账户 (一键自动) 模式失败",[89,455,456],{},"自动模式下应用已拿到服务商返回的明确错误, 界面文案通常直接给出原因:",[104,458,459,469],{},[107,460,461],{},[110,462,463,466],{},[113,464,465],{},"界面提示",[113,467,468],{},"可能原因与处理",[123,470,471,479,487,495,503,511,519,527,535],{},[110,472,473,476],{},[128,474,475],{},"DNS 账户不可用: 账户已被删除或凭据不完整",[128,477,478],{},"账户被删或字段缺失; 重新选择, 或到「DNS 账户」编辑该账户后重试",[110,480,481,484],{},[128,482,483],{},"DNS 服务商认证失败: Token \u002F 密钥无效或已过期",[128,485,486],{},"重新生成 Token \u002F 密钥并更新账户 (注意别用全局账号密码)",[110,488,489,492],{},[128,490,491],{},"DNS 服务商拒绝访问: Token 权限不足",[128,493,494],{},"按界面提示授予最小 DNS 编辑权限 (并包含读取区域权限), 并限定到目标域名",[110,496,497,500],{},[128,498,499],{},"未在所选服务商找到该域名的解析区域",[128,501,502],{},"域名未托管在该账户下; 换成托管该域名的账户",[110,504,505,508],{},[128,506,507],{},"CA 域名校验失败: 挑战记录未被正确解析",[128,509,510],{},"域名解析服务商与所选账户不一致 (如域名解析实际不在该账户)",[110,512,513,516],{},[128,514,515],{},"等待 DNS 传播超时",[128,517,518],{},"解析尚未生效; 稍后重试 (默认等待上限 5 分钟); 不建议用「跳过 DNS 传播检查」绕过",[110,520,521,524],{},[128,522,523],{},"CA 限流",[128,525,526],{},"短时间申请次数过多; 先用 Staging 验证流程后再转 Production",[110,528,529,532],{},[128,530,531],{},"网络异常: 无法连接 CA 或 DNS 服务商 API",[128,533,534],{},"检查网络、代理或防火墙; 代理可能导致对 API 的访问被拦",[110,536,537,540],{},[128,538,539],{},"证书已签发但文件整理失败",[128,541,542,543,546],{},"查看运行日志; 确认 ",[135,544,545],{},"Config\u002FCertificates\u002F"," 目录可写",[86,548,549],{},[89,550,551],{},"申请过程中窗口会实时显示「运行日志」(已脱敏的 lego 输出), 失败时可直接展开定位原因。",[399,553,555],{"id":554},"手动-dns-模式常见失败","手动 DNS 模式常见失败",[104,557,558,568],{},[107,559,560],{},[110,561,562,565],{},[113,563,564],{},"可能原因",[113,566,567],{},"排查方式",[123,569,570,578,598,606,614],{},[110,571,572,575],{},[128,573,574],{},"TXT 记录值复制不完整或含多余空格\u002F引号",[128,576,577],{},"重新复制记录值, 注意不要包含外层引号",[110,579,580,587],{},[128,581,582,583,586],{},"记录主机缺少 ",[135,584,585],{},"_acme-challenge."," 前缀",[128,588,589,590,593,594,597],{},"主机名应形如 ",[135,591,592],{},"_acme-challenge.example.com"," (部分服务商只需填 ",[135,595,596],{},"_acme-challenge",")",[110,599,600,603],{},[128,601,602],{},"域名填写错误或非自有域名",[128,604,605],{},"确认域名拼写, 且您对该域名有 DNS 控制权",[110,607,608,611],{},[128,609,610],{},"CA 限速 (尤其 Production)",[128,612,613],{},"先用 Staging 验证流程; 生产环境需控制申请频率",[110,615,616,619],{},[128,617,618],{},"校验等待超时 (5 分钟)",[128,620,621],{},"DNS 尚未传播; 等待数分钟后重新申请",[399,623,624],{"id":624},"证书填了却启动失败",[257,626,627,633,647],{},[216,628,629,632],{},[202,630,631],{},"Staging 证书不可用于生产",": Staging 证书不被浏览器信任, 仅用于流程验证; 正式使用需改用 Production 重新申请。",[216,634,635,638,639,642,643,646],{},[202,636,637],{},"证书与私钥不匹配",": 请使用同一次申请产出的 ",[135,640,641],{},"fullchain.pem"," 与 ",[135,644,645],{},"privkey.pem","; 用「从证书助手选择」会成对填入, 避免手工配错。",[216,648,649,652],{},[202,650,651],{},"证书临期提醒",": 选择 Staging 证书时会提示「Staging (测试)」; 其他证书距到期不足 30 天会提示「即将到期 (N d)」。",[193,654],{},[97,656,658],{"id":657},"更新内容窗口-264","更新内容窗口 (26.4)",[399,660,662],{"id":661},"窗口显示暂时无法获取更新说明","窗口显示「暂时无法获取更新说明」",[257,664,665,670,675,684],{},[216,666,667,669],{},[202,668,204],{},": 升级后首次启动弹出「本次更新内容」, 但内容区显示「暂时无法获取更新说明, 可稍后在更新页查看。」。",[216,671,672,674],{},[202,673,414],{},": 更新接口不可达 (网络\u002F代理) 或服务端暂无当前版本条目。",[216,676,677,679,680,683],{},[202,678,420],{},": 检查网络后到「更新」页查看完整版本变更; 该窗口失败",[202,681,682],{},"不会影响启动",", 也不会因此重试弹窗。",[216,685,686,689],{},[202,687,688],{},"「博客更新」页签拉取失败",": 同上, 会提示获取失败; 可切换回「更新日志 (API)」页签或到更新页查看。",[399,691,692],{"id":692},"不希望再次弹出",[257,694,695],{},[216,696,697,698,701,702,705],{},"窗口只要展示过即记为已读 (记录在 ",[135,699,700],{},"Cache\u002Fwhats-new.json","), ",[202,703,704],{},"同一版本不会二次打扰","; 版本号未变化时也不会弹出。",[193,707],{},[97,709,710],{"id":710},"更新失败",[399,712,713],{"id":713},"获取更新信息失败",[89,715,716,718],{},[202,717,204],{},": 「更新」页状态区显示「获取更新失败」, 无最新版本信息。",[89,720,721,211],{},[202,722,210],{},[213,724,725,728],{},[216,726,727],{},"检查网络连接 (能否访问其他网站); 代理\u002FVPN 是否拦截了到更新 API 的请求。",[216,729,730],{},"点击「检查更新」重试; 若更新通道为「预览」, 可切回「稳定」通道再试 (预览通道偶发无发布)。",[399,732,734],{"id":733},"下载失败-校验失败","下载失败 \u002F 校验失败",[89,736,737,739],{},[202,738,204],{},": 状态区显示「更新下载失败…」或「下载文件校验失败…」, 出现「重试下载」按钮。",[89,741,742,211],{},[202,743,210],{},[213,745,746,749,756,759],{},[216,747,748],{},"点击「重试下载」重试一次 (网络波动常见)。",[216,750,751,752,755],{},"仍失败: 在「设置」页切换",[202,753,754],{},"下载源"," (TPCA ↔ 官方) 后重试。",[216,757,758],{},"校验失败且重试仍出现: 下载源文件可能损坏, 等待一段时间后重试, 或切换下载源。",[216,760,761,762,765],{},"若为 Windows 且下载的是安装包, 确认磁盘空间充足 (安装包数百 MB, 需预留 ",[135,763,764],{},"Cache"," 目录空间)。",[399,767,769],{"id":768},"首次启动隧道时-mefrpc-下载失败","首次启动隧道时 mefrpc 下载失败",[89,771,772,774],{},[202,773,204],{},": 启动隧道时提示下载 mefrpc 客户端失败, 隧道无法启动。",[89,776,777,211],{},[202,778,210],{},[213,780,781,792,798],{},[216,782,783,784,787,788,791],{},"确认 ",[135,785,786],{},"bin\u002Fmefrpc.exe"," (Windows) 或 ",[135,789,790],{},"bin\u002Fmefrpc.tar"," (Linux\u002FmacOS) 是否存在; 缺失时启动隧道会自动下载。",[216,793,794,795,797],{},"下载失败: 在「设置」页切换",[202,796,754],{}," (TPCA ↔ 官方) 后重新启动隧道。",[216,799,800,801,804,805,808],{},"校验失败 (文件损坏): 删除 ",[135,802,803],{},"bin"," 下残留的 ",[135,806,807],{},"mefrpc*.tmp"," 与损坏文件后重试。",[193,810],{},[97,812,814],{"id":813},"链接启动隧道-pml2","链接启动隧道 (pml2:\u002F\u002F)",[89,816,817,818,821],{},"应用支持 ",[135,819,820],{},"pml2:\u002F\u002F"," 通用链接, 用于从浏览器\u002F网页一键启动指定隧道:",[823,824,830],"pre",{"className":825,"code":827,"language":828,"meta":829},[826],"language-text","pml2:\u002F\u002FStartProxy\u002F\u003C隧道ID>?Name=\u003C隧道名>\n","text","",[135,831,827],{"__ignoreMap":829},[89,833,834,835,838,839,842,843,846],{},"(",[135,836,837],{},"mefrp:\u002F\u002F"," 前缀同样识别; ",[135,840,841],{},"Name"," 可省略, 省略时终端标签显示 ",[135,844,845],{},"#隧道ID","。)",[399,848,849],{"id":849},"首次使用的平台差异",[104,851,852,862],{},[107,853,854],{},[110,855,856,859],{},[113,857,858],{},"平台",[113,860,861],{},"协议注册方式",[123,863,864,880,898],{},[110,865,866,869],{},[128,867,868],{},"Windows",[128,870,871,872,875,876,879],{},"应用启动时写入 ",[135,873,874],{},"HKCU\\Software\\Classes\\pml2"," (当前用户, ",[202,877,878],{},"无需管理员","); 已指向本程序时跳过",[110,881,882,885],{},[128,883,884],{},"Linux",[128,886,887,888,891,892,138,895,597],{},"启动时写入 ",[135,889,890],{},"~\u002F.local\u002Fshare\u002Fapplications\u002Fpml2-handler.desktop"," 并注册为默认处理器 (依赖 ",[135,893,894],{},"xdg-mime",[135,896,897],{},"update-desktop-database",[110,899,900,903],{},[128,901,902],{},"macOS",[128,904,905,906,909],{},"由应用包的 ",[135,907,908],{},"Info.plist"," 声明, 无需运行时写入",[86,911,912],{},[89,913,914],{},"注册在主实例启动时进行一次; 应用目录被移动或重装后, 下次启动会自动改写为新路径。",[399,916,917],{"id":917},"点击链接的行为",[257,919,920,934],{},[216,921,922,925,926,929,930,933],{},[202,923,924],{},"应用未运行 (冷启动)",": 链接参数写入 ",[135,927,928],{},"Cache\u002Fstartup.json",", 主窗口在 ",[202,931,932],{},"2 分钟内","读到即拉起对应隧道 (读取后立即删除该临时文件, 不会重复启动)。",[216,935,936,939,940,943,944,947],{},[202,937,938],{},"应用已在运行",": 第二次启动会把链接",[202,941,942],{},"透传","给已运行实例 (命名管道 ",[135,945,946],{},"tech.rycb.pml2","), 由它显示主窗口并启动隧道。",[399,949,951],{"id":950},"链接点了没反应","链接点了没反应?",[104,953,954,963],{},[107,955,956],{},[110,957,958,961],{},[113,959,960],{},"现象",[113,962,468],{},[123,964,965,977,988,1002],{},[110,966,967,970],{},[128,968,969],{},"系统提示「没有可打开此链接的应用」",[128,971,972,973,976],{},"协议尚未注册 (如手动拷贝的绿色版从未启动过); ",[202,974,975],{},"先手动启动一次应用","即可自动注册",[110,978,979,982],{},[128,980,981],{},"应用打开了但没启动隧道",[128,983,984,985],{},"隧道 ID 不存在\u002F已删除、未登录或获取启动凭证失败; 先登录并在主界面确认该隧道可用, 失败原因见 ",[135,986,987],{},"Logs\u002F",[110,989,990,996],{},[128,991,992,993],{},"隧道名显示为 ",[135,994,995],{},"#123",[128,997,998,999,1001],{},"链接未带 ",[135,1000,841],{}," 参数, 属正常表现",[110,1003,1004,1007],{},[128,1005,1006],{},"想撤销协议注册",[128,1008,1009,1010,1012,1013],{},"Windows 删除 ",[135,1011,874],{},"; Linux 删除 ",[135,1014,890],{},{"title":829,"searchDepth":1016,"depth":1016,"links":1017},2,[1018,1019,1020,1021,1022,1023,1024,1025,1033,1037,1042],{"id":99,"depth":1016,"text":99},{"id":197,"depth":1016,"text":198},{"id":230,"depth":1016,"text":231},{"id":282,"depth":1016,"text":283},{"id":314,"depth":1016,"text":315},{"id":345,"depth":1016,"text":346},{"id":368,"depth":1016,"text":368},{"id":381,"depth":1016,"text":382,"children":1026},[1027,1029,1030,1031,1032],{"id":401,"depth":1028,"text":402},3,{"id":424,"depth":1028,"text":425},{"id":452,"depth":1028,"text":453},{"id":554,"depth":1028,"text":555},{"id":624,"depth":1028,"text":624},{"id":657,"depth":1016,"text":658,"children":1034},[1035,1036],{"id":661,"depth":1028,"text":662},{"id":692,"depth":1028,"text":692},{"id":710,"depth":1016,"text":710,"children":1038},[1039,1040,1041],{"id":713,"depth":1028,"text":713},{"id":733,"depth":1028,"text":734},{"id":768,"depth":1028,"text":769},{"id":813,"depth":1016,"text":814,"children":1043},[1044,1045,1046],{"id":849,"depth":1028,"text":849},{"id":917,"depth":1028,"text":917},{"id":950,"depth":1028,"text":951},"本文将介绍 PML 2 常见的故障排查方法。","md",null,{},true,{"title":44,"description":1047},"qZxK4chR7hrzUBet4yyIPTObSqv9OtTeoJ47r9buZj0",[1055,1057],{"title":40,"path":41,"stem":42,"description":1056,"children":-1},"本文将介绍如何使用 PML 2。",{"title":48,"path":49,"stem":50,"description":1058,"children":-1},"本文将介绍 PML 2 的配置文件。",1791004265205]