winapps-org/winapps

App start fails saying the RDP port is not open

Open

#270 opened on Sep 23, 2024

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Shell (15,020 stars) (463 forks)batch import
good first issue

Description

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.

Contributor guide

Tech stack
shell
Domain
desktopcli
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
shell scriptingbasic TCP/IP networking
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
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.
App start fails saying the RDP port is not open · winapps-org/winapps#270 | Good First Issue