winapps-org/winapps

App start fails saying the RDP port is not open

Open

#270 建立於 2024年9月23日

在 GitHub 查看
 (2 留言) (0 反應) (0 負責人)Shell (15,020 star) (463 fork)batch import
good first issue

描述

The following command: timeout 5 nc -z "$RDP_IP" "$RDP_PORT" &>/dev/null; makes app startup fail, because it does not hear back over the rdp port, even though the VM is up and running RDP-server on said port.

This is also why setup.sh fails with Error 13 in some instances even though the VM is reachable through RDP. See #260. A fix should remedy both issues.

Maybe we can find an alternative to this port-check over netcat? Alternatively we could leave out the port-check entirely and just report the connection error if the rdp connection-attempt fails one step later in the connection-process.

貢獻者指南

技術棧
shell
領域
desktopcli
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
under 1 hour
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
shell scriptingbasic TCP/IP networking
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
75
研究方向
Examine the startup script (likely in the repository root) where the port check line `timeout 5 nc z "$RDP IP" "$RDP PORT" &>/dev/null;` is used. Consider removing the check and relying on the RDP connection error handling later, or replace netcat with a more reliable method. Also review the referenced issue #260 for additional context.