winboat icon indicating copy to clipboard operation
winboat copied to clipboard

[Bug] Installation crashes if port 3389 is already in use

Open Alex-Gunn opened this issue 2 months ago • 2 comments

What version of WinBoat are you running?

0.8.7

Your Environment

Linux distro used: Ubuntu 24.04.3 LTS Desktop Environment used: LXQt 1.4.0 FreeRDP: flatpak 3.17.2 xrdp: 0.9.24-4

Steps to Reproduce / Context

Install WinBoat from a deb packet. Run WinBoat from the context menu. Proceed to the step when "WinBoat is now installing Windows. Please be patient..."

Logs

~/.winboat/install.log

545ccfce83e1 Extracting [==================================================>] 136B/136B 545ccfce83e1 Extracting [==================================================>] 136B/136B 545ccfce83e1 Pull complete windows Pulled Network winboat_default Creating Network winboat_default Created Container WinBoat Creating Container WinBoat Created Container WinBoat Starting Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint WinBoat (3b6c8915eef3b3fa3314cb141cea98df8456c9ef7a56acdd59e7b19ec30c8052): failed to bind host port for 0.0.0.0:3389:172.18.0.2:3389/tcp: address already in use

Expected Behavior

Installation finishes successfully.

Current Behavior

An error occurred while installing Windows. Please check the logs in ~/.winboat and verify docker logs WinBoat in your terminal for more information. To reset and try again, follow these instructions.

Image

Possible Solution

Solution 1. Add additional check into "Pre-Requisites" window. Solution 2. Update documentation to include a check whether port 3389 is already in use by any other software Solution 3. Allow custom port instead of 3389

Quality Notice

  • [x] I have checked the issue tracker and verified that this bug is a unique case.

Alex-Gunn avatar Nov 04 '25 05:11 Alex-Gunn

I ran into same issue, as soon as I stopped xrdpd the installation started fine.

Otlichno avatar Nov 04 '25 14:11 Otlichno

@Alex-Gunn @Otlichno I've submitted a pull request (removed) that addresses this issue: https://github.com/TibixDev/winboat/pull/removed What the fix includes:

Pre-installation port conflict detection - WinBoat now checks if port 3389 is in use before starting the installation Automatic xrdp detection - Identifies if xrdp is the conflicting service Resolution options - Provides clear instructions to stop xrdp or disable it during WinBoat installation Installation tools - Includes helper scripts to resolve the conflict and resume installation

This implements Solution 1 from your suggestions - adding a check into the pre-requisites phase so users are warned before the installation fails.

===================================================================================

EDIT: I apologize for this PR. I introduced scripts to address multiple issues I identified, but I now understand your contribution guidelines specifically prohibit adding scripts to the project. While I was trying to solve real problems, I should have reviewed your contribution policy before submitting. The approach was wrong for this project's standards. I've closed the PR and deleted the branch. I won't be introducing scripts in future contributions.

sprinteroz avatar Nov 05 '25 11:11 sprinteroz

This got fixed with #327, and will arrive as a feature in our 0.9.0 release. In the meantime you could try 0.9.0-alpha2.

Levev avatar Nov 22 '25 03:11 Levev

until that release is out

sudo xrdp -k

before installation is a workaround that seems to work

Guacam-Ole avatar Nov 22 '25 10:11 Guacam-Ole