Replies: 15 comments
-
|
Hello! Thank you for your interest in this project 😊 I appreciate your efforts to debug this issue on your own and apologise for the bad experience you have had thus far. The error message suggests that the Additionally, as a further debugging step, enable debugging in Looking forward to hearing the results! |
Beta Was this translation helpful? Give feedback.
-
|
I attempted the Here is the debug output after adding set -x ( - also running the extracted command in isolation does not appear do anything but present a |
Beta Was this translation helpful? Give feedback.
-
|
It appears the complete Please run the following command and share the results, replacing the IP address following xfreerdp3 /cert:tofu /d: /u:"testuser" /p:1234 /scale:100 +auto-reconnect +home-drive -wallpaper +dynamic-resolution /app:program:'C:\Windows\System32\cmd.exe',cmd:'/C type NUL > \\tsclient\home\A_WINAPPS_CONNECTION_TEST_FILE && tsdiscon' /v:"192.168.122.219" |
Beta Was this translation helpful? Give feedback.
-
|
just tried your suggestion, no test file is created. If I run the terminal I only see the original log error messages, but if I run this test command from the console I do see a lot of extra output though... |
Beta Was this translation helpful? Give feedback.
-
|
The logs demonstrate a certificate mismatch issue, which can be resolved by removing the problematic certificate. WinApps instructs To remove the problematic certificate, run: rm ~/.config/freerdp/server/172.17.9.35_3389.pemOnce the old certificate is deleted, please rerun the test command I mentioned earlier. |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately that does not work and here is what I am observing: When I run installer.sh this fails to connect (as per the set -x debug message from earlier) and after running this script the path ~/.config/freerdp/server/ still does not exist. When I run the test command you gave me, the ~/.config/freerdp/server/ path is newly createsd and a certificate file also appears, but deleting that certificate and then trying to either run the installer.sh again (givess same issue and no certificate created ) or re-running the test command recreates a new certificate but still gives all the same certificate errors exactly as in the large debug post as before, so I'm stuck in a loop. I am running absolutely everything default as per WinApps instruction in the readme and I am testing on both a fresh Ubuntu & LMDE image (each test rolling back from snaphot) I get exactly same issues with either flatpak or freerdp3-x11 packages. |
Beta Was this translation helpful? Give feedback.
-
|
@itiligent a side note here. If you want rootless docker use podman instead. Can you check if the vm is pingable? Maybe something is wromg with the network configuration. What do you mean with vmware esxi? |
Beta Was this translation helpful? Give feedback.
-
|
@KernelGhost I've identified the issue. Due to the compose file being moved the bind mount for @itiligent Please try keeping your compose file in the same directory as installer.sh, that should work |
Beta Was this translation helpful? Give feedback.
-
|
@LDprg I am trying to install WinApps in a Linux LMDE vm under Esxi. In the ESXi vm the Docker container s pingable and also accessible via a remote windows rdp client & remoteley via http://x.x.x.x:8006. Docker and networks are fine. @oskardotglobal The compose file and installer.sh are in the same directory and always have been. I have narrowed it down a bit further...
Whats going on with Esxi vs a hardware OS install? Edit: I've updated the issue name to now better reflect the issue |
Beta Was this translation helpful? Give feedback.
-
|
@oskardotglobal I resolved that issue in commit e99a210, as I noted that the |
Beta Was this translation helpful? Give feedback.
-
|
@itiligent While I wouldn't suggest this as a long-term solution, you could try changing |
Beta Was this translation helpful? Give feedback.
-
|
here is the /cert:ignore output. Still no luck on a system hosted on ESXi, but the exact same config and command works ok if I run this on my LMDE6 Lenovo laptop |
Beta Was this translation helpful? Give feedback.
-
|
In my experience that error always showed up when the reg file isn't installed, can you double check that it is? |
Beta Was this translation helpful? Give feedback.
-
|
If the fix suggested by @oskardotglobal does not resolve the issue, I’m afraid I’m out of ideas. It seems like this might be more closely related to |
Beta Was this translation helpful? Give feedback.
-
|
The reg file is indeed being applied, so I'll take a deeper look into FreeRDP a litttle more when I get the chance and come back. Thanks all for your efforts. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
Great project!
I've spent ages on this, but no matter what I try and following instructions to the letter, the installer.sh cannot make the final RDP connection to set up WinApps. However the Windows container builds fine and can be reached via a normal rdp client over the network. VNC over http is also fine.
I've built several OS versions and tried as number of Linux flavors from Ubuntu 24, LMDE and Debian Bookworm. Also tried flatpak and source built FreeRDP3 versions with --user settings, and have tried configuring docker to not require root also, but no matter what I do all attmepts give the exact same error outputs. I am also making sure the container is logged out before running installer.sh
and freerdp test log shows:
BTW if I use orignial repo (https://github.com/Fmstrat/winapps) with Freerdp2 to connect to the docker container, the old Winapps installs just fine
what am I doing wrong? Or is something broken?
Beta Was this translation helpful? Give feedback.
All reactions