exit code 14 after upgrading to fedora41 beta

[DaRandomCube]

what happened is, simply upgrading to f41 beta and boom, cannot connect via rdp anymore the issues with the same error didn't tell the fix winapps flavor: podman here is the log:

[21:16:39:348] [43332:0000a945] [ERROR][com.freerdp.core.transport] - [transport_default_write]: BIO_should_retry returned a system error 32: Broken pipe
[21:16:39:348] [43332:0000a945] [ERROR][com.freerdp.core] - [transport_default_write]: ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
[21:16:36:913] [43332:0000a945] [INFO][com.freerdp.client.x11] - [xf_setup_x11]: Enabling X11 debug mode.

[DaRandomCube]

i tried pinging the vm ip address, no output

[friday06]

this is common among the winapps flavors, i tried the workaround mentioned in other error 14 topic, none of them worked for me. try doing the /cert:ignore in flags of winapps conf

[DaRandomCube]

this is common among the winapps flavors, i tried the workaround mentioned in other error 14 topic, none of them worked for me. try doing the /cert:ignore in flags of winapps conf

tried it, doesn't work

[friday06]

try toggling that ( allow connections only ) off & run the script again ?

[DaRandomCube]

already off :(

[DaRandomCube]

here is the fun thing when you try to connect using setup script, there should be something in ~/.config/freerdp/server/ however, it's empty

[friday06]

here is the fun thing when you try to connect using setup script, there should be something in ~/.config/freerdp/server/ however, it's empty

for me, there is black screen when i launch with that option off, also /freerdp/server has a pem file for me though it ain't of any use as i added ignore cert there in winapps conf

[DaRandomCube]

any fix/updates?

[DaRandomCube]

Hello?

[DaRandomCube]

guess i found a solution, not recommended to do it, but that what worked for me remove the installed firewall and reboot there is obviously a better solution by manually allowing for the port, but lazy to do so

[DaRandomCube]

soo, it returned again, even without a firewall i noticed something when trying to stop the container, it outputs

internal:0:0-0: Error: Could not process rule: No such file or directory

searching give me nothing helpful

[DaRandomCube]

update, now it works after reinstalling firewalld and adding ports

firewall-cmd --zone=trusted --add-port=3389/udp

firewall-cmd --zone=trusted --add-port=3389/tcp

firewall-cmd --runtime-to-permanent

plus, adding missing tables in nft

sudo nft add table inet firewalld

cannot guarantee that the problem won't happen again, will leave open for a while this should fix it so it doesn't happen again

[ccbadd]

update, now it works after reinstalling firewalld and adding ports

firewall-cmd --zone=trusted --add-port=3389/udp

firewall-cmd --zone=trusted --add-port=3389/tcp

plus, adding missing tables in nft

sudo nft add table inet firewalld

cannot guarantee that the problem won't happen again, will leave open for a while

I logged into the web interface and added a password to default user, "Docker", and the error goes away. Now I just get a blank screen.

[DaRandomCube]

for now i should able to login normally by setting the above rules to be permanent

firewall-cmd --runtime-to-permanent

lemme update the og reply

---

update, now it works after reinstalling firewalld and adding ports

firewall-cmd --zone=trusted --add-port=3389/udp

firewall-cmd --zone=trusted --add-port=3389/tcp

plus, adding missing tables in nft

sudo nft add table inet firewalld

cannot guarantee that the problem won't happen again, will leave open for a while

I logged into the web interface and added a password to default user, "Docker", and the error goes away. Now I just get a blank screen.

did you put the password also in winapps.conf?

[ccbadd]

did you put the password also in winapps.conf? Yes I did. The step needed to open the web link and set the username/password really should be added to the howto.

[ccbadd]

I did get it working. In the config file I had to set "MULTIMON=true" and docker-compose up after and it works fine now. I do have a 3 monitor setup.

[DaRandomCube]

I did get it working. In the config file I had to set "MULTIMON=true" and docker-compose up after and it works fine now. I do have a 3 monitor setup.

Well thats the cause Multimon is know for resulting in black screen

[ccbadd]

Well thats the cause Multimon is know for resulting in black screen

I did read that but I took it that having it set to true would be what caused the black screen. It turned out the opposite for me.

[DaRandomCube]

huh anyway will close the issue, since your issue is different, open a different issue