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

./setup.sh Exiting with status '14' #287

Open
keego776 opened this issue Oct 7, 2024 · 4 comments
Open

./setup.sh Exiting with status '14' #287

keego776 opened this issue Oct 7, 2024 · 4 comments

Comments

@keego776
Copy link

keego776 commented Oct 7, 2024

trying to install winapps on arch and the ./setup.sh failing at Remote Desktop connection with Windows (status 14)
log:

[11:15:01:195] [858162:000d1835] [WARN][com.freerdp.crypto] - [verify_cb]: Certificate verification failure 'self-signed certificate (18)' at stack position 0
[11:15:01:195] [858162:000d1835] [WARN][com.freerdp.crypto] - [verify_cb]: CN = DOCKERW-GCRDEJI
[11:15:02:672] [858162:000d1835] [ERROR][com.winpr.sspi.Kerberos] - [kerberos_AcquireCredentialsHandleA]: krb5glue_get_init_creds (Client '[email protected]' not found in Kerberos database [-1765328378])
[11:15:02:046] [858162:000d1835] [ERROR][com.winpr.sspi.Kerberos] - [kerberos_AcquireCredentialsHandleA]: krb5glue_get_init_creds (Client '[email protected]' not found in Kerberos database [-1765328378])
[11:15:02:048] [858162:000d1835] [ERROR][com.freerdp.core.nla] - [nla_recv_pdu]: SPNEGO failed with NTSTATUS: (null) [0xFF00006D]
[11:15:02:048] [858162:000d1835] [ERROR][com.freerdp.core] - [nla_recv_pdu]: ERRCONNECT_AUTHENTICATION_FAILED [0x00020009]
[11:15:02:048] [858162:000d1835] [ERROR][com.freerdp.core.rdp] - [rdp_recv_callback_int][0x5a3a9db53940]: CONNECTION_STATE_NLA - nla_recv_pdu() fail
[11:15:02:048] [858162:000d1835] [ERROR][com.freerdp.core.rdp] - [rdp_recv_callback_int][0x5a3a9db53940]: CONNECTION_STATE_NLA status STATE_RUN_FAILED [-1]
[11:15:02:048] [858162:000d1835] [ERROR][com.freerdp.core.transport] - [transport_check_fds]: transport_check_fds: transport->ReceiveCallback() - STATE_RUN_FAILED [-1]
[11:15:01:140] [858162:000d1835] [INFO][com.freerdp.client.x11] - [xf_setup_x11]: Enabling X11 debug mode.

@keego776
Copy link
Author

keego776 commented Oct 7, 2024

with RDP_FLAGS="/sec:tls" in winapps.conf it produces a black screen and crushes still with Exiting with status '14'
log:
[11:35:13:571] [860202:000d202d] [WARN][com.freerdp.crypto] - [verify_cb]: Certificate verification failure 'self-signed certificate (18)' at stack position 0
[11:35:13:571] [860202:000d202d] [WARN][com.freerdp.crypto] - [verify_cb]: CN = DOCKERW-GCRDEJI
[11:35:13:588] [860202:000d202d] [WARN][com.freerdp.core.license] - [license_read_binary_blob_data]: license binary blob::type BB_ERROR_BLOB, length=0, skipping.
[11:35:14:977] [860202:000d202d] [WARN][com.freerdp.client.x11] - [xf_Pointer_get_window]: xf_Pointer: Invalid appWindow
[11:35:14:982] [860202:000d202d] [WARN][com.freerdp.client.x11] - [xf_Pointer_get_window]: xf_Pointer: Invalid appWindow
[11:35:14:982] [860202:000d202d] [WARN][com.freerdp.client.x11] - [xf_Pointer_Set]: handle=0
[11:35:14:017] [860202:000d202d] [WARN][com.freerdp.client.x11] - [xf_Pointer_get_window]: xf_Pointer: Invalid appWindow
[11:35:14:017] [860202:000d202d] [WARN][com.freerdp.client.x11] - [xf_Pointer_Set]: handle=0
[11:35:14:059] [860202:000d202d] [WARN][com.freerdp.client.x11] - [xf_Pointer_get_window]: xf_Pointer: Invalid appWindow
[11:35:14:059] [860202:000d202d] [WARN][com.freerdp.client.x11] - [xf_Pointer_Set]: handle=0

@keego776
Copy link
Author

keego776 commented Oct 7, 2024

im running winapps with docker

@ccbadd
Copy link

ccbadd commented Oct 12, 2024

I had the same issue and what I had to do was, after I got the container created and running, logged into the container via the web interface and created a password for the default user "Docker" and added the user and password to the config file. I also had to change the option MULTIMON=true in order to get past the black screen. Be sure to do the docker-compose down before making the changes and then do a docker-compose up after before trying to run the setup.sh script again.

@DaRandomCube
Copy link

it can be your firewall

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