Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error Encountered During WinApps Setup Using Docker and Tiny11 Image #391

Open
tomjpalamattam opened this issue Jan 20, 2025 · 3 comments
Open

Comments

@tomjpalamattam
Copy link

tomjpalamattam commented Jan 20, 2025

Description

I successfully set up Docker with the Tiny11 image. After installation, I could access the output via the VNC address: http://127.0.0.1:8006/. However, I encountered an error when running the setup script.

Steps to Reproduce

  1. Set up tiny11 using Docker.
  2. Setup the compose.yaml and winapps.conf files.
  3. Follow the official setup script:
    bash <(curl https://raw.githubusercontent.com/winapps-org/winapps/main/setup.sh)
################################################################################
#                                                                              #
#                            WinApps Install Wizard                            #
#                                                                              #
################################################################################

Q) Install or uninstall WinApps? --> Install
Q) Configure WinApps for the current user 'tom' or the whole system? --> Current User
Q) Automatically install supported applications or choose manually? --> Manual (Default)

WinApps installation already present at /home/tom/.local/bin/winapps-src. Updating...
Already up to date.
Installing WinApps.
Checking for existing conflicting WinApps installations... Done!
Attempting to load WinApps configuration file... Done!
Checking whether dependencies are installed... Done!
Checking container status... Done!
Checking for an open RDP Port on Windows... Done!
Attempting to establish a Remote Desktop connection with Windows... Failed!

ERROR: REMOTE DESKTOP PROTOCOL FAILURE.
FreeRDP failed to establish a connection with Windows.
--------------------------------------------------------------------------------
Please view the log at /home/tom/.local/share/winapps/FreeRDP_Test_20250120_1527_497914124.log.
Troubleshooting Tips:
  - Ensure the user is logged out of Windows prior to initiating the WinApps installation.
  - Ensure the credentials within the WinApps configuration file are correct.
  - Utilise a new certificate by removing relevant certificate(s) in /home/tom/.config/freerdp/server.
  - If using 'libvirt', ensure the Windows VM is correctly named as specified within the README.
  - If using 'libvirt', ensure 'Remote Desktop' is enabled within the Windows VM.
  - If using 'libvirt', ensure you have merged 'RDPApps.reg' into the Windows VM's registry.
  - If using 'libvirt', try logging into and back out of the Windows VM within 'virt-manager' prior to initiating the WinApps installation.
--------------------------------------------------------------------------------
Exiting with status '14'.

I was able to Connect to RDP using the following command:

xfreerdp3 /u:User1 /p:password1 /v:127.0.0.1 /cert:tofu

Additional Notes

  • I removed the file extensions from configuration files to include them as attachments in this post.

Attachments

FreeRDP_Test_20250120_1527_497914124.log

compose.txt

winapps.txt

@oskardotglobal
Copy link
Member

Did you try putting /cert:ignore instead of /cert:tofu into your Winapps config?

@tomjpalamattam
Copy link
Author

Did you try putting /cert:ignore instead of /cert:tofu into your Winapps config?

I tried it now, but is of no use

@whacka
Copy link

whacka commented Jan 21, 2025

I have the same issue, running Fedora 41, Podman and a full Win11 install.
Connecting directly via xfreerdp works with either /cert:ignore or /cert:tofu, but setup.sh fails to connect.

Oddly enough, despite running Windows via Podman I can use xfreerdp without the issue described in #251.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants