winapps-org / winapps-org/winapps
App start fails saying the RDP port is not open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 16k
- Forks
- 508
- Avg merge
- 13h 35m
- Merged PRs (30d)
- 3
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting setup.sh and locating the app-start path that runs timeout 5 nc -z "$RDP_IP" "$RDP_PORT" &>/dev/null. Reproduce the check against a reachable VM running an RDP server, then verify that startup no longer fails when RDP is available and that the setup.sh Error 13 case is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, shell
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100