[{"data":1,"prerenderedAt":1059},["ShallowReactive",2],{"navigation_docs_zh_tw":3,"-zh-tw-pml-2-troubleshooting":75,"-zh-tw-pml-2-troubleshooting-surround":1054},[4,26],{"title":5,"path":6,"stem":7,"children":8,"page":25},"PML 2 外掛開發指南","\u002Fzh_tw\u002Fpml-2-plugin","zh_tw\u002Fpml-2-plugin",[9,13,17,21],{"title":10,"path":11,"stem":12},"外掛開發綜述","\u002Fzh_tw\u002Fpml-2-plugin\u002Fintro","zh_tw\u002Fpml-2-plugin\u002F01.intro",{"title":14,"path":15,"stem":16},"外掛系統觸發點說明","\u002Fzh_tw\u002Fpml-2-plugin\u002Ftriggers","zh_tw\u002Fpml-2-plugin\u002F02.triggers",{"title":18,"path":19,"stem":20},"外掛系統運算子說明","\u002Fzh_tw\u002Fpml-2-plugin\u002Foperators","zh_tw\u002Fpml-2-plugin\u002F03.operators",{"title":22,"path":23,"stem":24},"內建函式","\u002Fzh_tw\u002Fpml-2-plugin\u002Ffunctions","zh_tw\u002Fpml-2-plugin\u002F04.functions",false,{"title":27,"path":28,"stem":29,"children":30,"page":25},"PML 2","\u002Fzh_tw\u002Fpml-2","zh_tw\u002Fpml-2",[31,35,39,43,47,51,55,59,63,67,71],{"title":32,"path":33,"stem":34},"介紹 & 下載","\u002Fzh_tw\u002Fpml-2\u002Fintro","zh_tw\u002Fpml-2\u002F01.intro",{"title":36,"path":37,"stem":38},"安裝","\u002Fzh_tw\u002Fpml-2\u002Finstall","zh_tw\u002Fpml-2\u002F02.install",{"title":40,"path":41,"stem":42},"使用者指南","\u002Fzh_tw\u002Fpml-2\u002Fuser_guide","zh_tw\u002Fpml-2\u002F03.user_guide",{"title":44,"path":45,"stem":46},"故障排查","\u002Fzh_tw\u002Fpml-2\u002Ftroubleshooting","zh_tw\u002Fpml-2\u002F04.troubleshooting",{"title":48,"path":49,"stem":50},"設定檔","\u002Fzh_tw\u002Fpml-2\u002Fconfig","zh_tw\u002Fpml-2\u002F05.config",{"title":52,"path":53,"stem":54},"主題","\u002Fzh_tw\u002Fpml-2\u002Fthemes","zh_tw\u002Fpml-2\u002F06.themes",{"title":56,"path":57,"stem":58},"Plugin","\u002Fzh_tw\u002Fpml-2\u002Fplugin","zh_tw\u002Fpml-2\u002F07.plugin",{"title":60,"path":61,"stem":62},"PML 2 隱私權政策","\u002Fzh_tw\u002Fpml-2\u002Fpolicy","zh_tw\u002Fpml-2\u002F08.policy",{"title":64,"path":65,"stem":66},"PML 2 使用者條款","\u002Fzh_tw\u002Fpml-2\u002Fuser_agreement","zh_tw\u002Fpml-2\u002F09.user_agreement",{"title":68,"path":69,"stem":70},"DNS 供應商","\u002Fzh_tw\u002Fpml-2\u002Fdns_providers","zh_tw\u002Fpml-2\u002F10.dns_providers",{"title":72,"path":73,"stem":74},"遙測","\u002Fzh_tw\u002Fpml-2\u002Ftelemetry","zh_tw\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_tw\u002Fzh_tw\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},"ZwdmyAbvqkPYH_5YnkQT5jvWU_zq8WM3VwaTza7YUsA",[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 的設定檔。",1791004266911]