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 (463 forks)batch import
good first issue

Repository metrics

Stars
 (15,020 stars)
PR merge metrics
 (Avg merge 12h 59m) (3 merged PRs in 30d)

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

Research direction
Examine the netcat timeout usage and consider replacing with a more reliable connection test or removing it and handling errors later.
Tech stack
shell
Domain
backend
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.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitShell
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75