HTML5 Gateway white screen during connection

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

HTML5 Gateway white screen during connection

L2 Linker

Hi,

 

When i try connect to TS via HTML5 gateway new tab is opened and i see white screen

In logs i can see this messages

 

/opt/tomcat/logs/localhost_access_log.2020-03-06.txt

 

10.0.0.13 - - [06/Mar/2020:10:40:46 -0500] "POST /guac/direct HTTP/1.1" 200 1945

10.0.0.13 - - [06/Mar/2020:10:40:46 -0500] "GET /guac/assets/guacamole-common-js/all.min.js HTTP/1.1" 200 68611

10.0.0.13 - - [06/Mar/2020:10:40:46 -0500] "GET /guac/styles.3d2115ec9b4c0bc574aa.bundle.css HTTP/1.1" 200 285699

10.0.0.13 - - [06/Mar/2020:10:40:47 -0500] "GET /guac/main.f27d6ee28025245ad570.bundle.js HTTP/1.1" 200 104172

10.0.0.13 - - [06/Mar/2020:10:40:47 -0500] "GET /guac/inline.dc22c8aa6e312c8b2bf1.bundle.js HTTP/1.1" 200 1447

10.0.0.13 - - [06/Mar/2020:10:40:47 -0500] "GET /guac/polyfills.4a55887047d75c1de2c4.bundle.js HTTP/1.1" 200 103273

10.0.0.13 - - [06/Mar/2020:10:40:47 -0500] "GET /guac/scripts.6fcbe1af6a0b103f5442.bundle.js HTTP/1.1" 200 165067

10.0.0.13 - - [06/Mar/2020:10:40:47 -0500] "GET /guac/vendor.9886ecd903245af8be12.bundle.js HTTP/1.1" 200 843157

10.0.0.13 - - [06/Mar/2020:10:40:47 -0500] "GET /guac/OpenSans-Regular.cd7296352d159532b66c.ttf HTTP/1.1" 200 106252

10.0.0.13 - - [06/Mar/2020:10:40:48 -0500] "GET /guac/websocket-tunnel?hostname=01PSM.sc-kavitech.com.ua&username=PSM@deb2e762-c92d-440a-9ff5-92de4e4aa3b6&width=1920&height=969&password=&KeepAliveInterval=60 HTTP/1.1" 101 -

10.0.0.13 - - [06/Mar/2020:10:40:48 -0500] "GET /guac/fontawesome-webfont.af7ae505a9eed503f8b8.woff2 HTTP/1.1" 200 77160

10.0.0.13 - - [06/Mar/2020:10:40:49 -0500] "GET /guac/favicon.ico HTTP/1.1" 200 5430

10.0.0.13 - - [06/Mar/2020:10:40:56 -0500] "GET /guac/roboto-v15-latin-regular.7e367be02cd17a96d513.woff2 HTTP/1.1" 200 14584

 

In /var/log/messages

 

Mar 6 10:40:01 rl0 systemd: Started Session 314 of user root.

Mar 6 10:40:48 rl0 guacd[8077]: Creating new client for protocol "rdp"

Mar 6 10:40:48 rl0 guacd[8077]: Connection ID is "$d392e39b-11c0-4e87-ae59-04ea65154af1"

Mar 6 10:40:48 rl0 guacd[8232]: Security mode: TLS

Mar 6 10:40:48 rl0 guacd[8232]: Resize method: none

Mar 6 10:40:48 rl0 guacd[8232]: User "@fed8aa58-6ce5-4123-b341-46a216630e37" joined connection "$d392e39b-11c0-4e87-ae59-04ea65154af1" (1 users now present)

Mar 6 10:40:48 rl0 guacd[8232]: Loading keymap "base"

Mar 6 10:40:48 rl0 guacd[8232]: Loading keymap "en-us-qwerty"

Mar 6 10:41:18 rl0 guacd[8232]: User is not responding.

Mar 6 10:41:18 rl0 guacd[8232]: User "@fed8aa58-6ce5-4123-b341-46a216630e37" disconnected (0 users remain)

Mar 6 10:41:18 rl0 guacd[8232]: Last user of connection "$d392e39b-11c0-4e87-ae59-04ea65154af1" disconnected

Mar 6 10:41:23 rl0 guacd[8232]: Client did not terminate in a timely manner. Forcibly terminating client and any child processes.

Mar 6 10:41:23 rl0 guacd[8077]: Connection "$d392e39b-11c0-4e87-ae59-04ea65154af1" removed.

 

In /var/opt/CARKpsmgw/logs/webapp/cyberark-psm-gateway-webapp.log

 

[PSMGW][10:47:08.223][[http-bio-443-exec-6]][DEBUG][c.c.psmgw.utils.CAPSMGWCORSHandler]: Yes

[PSMGW][10:47:08.224][[http-bio-443-exec-6]][DEBUG][c.c.psmgw.utils.CAPSMGWCORSHandler]: Adding CORS to request

[PSMGW][10:47:08.224][[http-bio-443-exec-6]][DEBUG][c.c.psmgw.utils.CAPSMGWCORSHandler]: All origins are allowed

[PSMGW][10:47:08.224][[http-bio-443-exec-6]][DEBUG][c.c.psmgw.utils.CAPSMGWHSTSHandler]: Setting Strict Transport Security for request

[PSMGW][10:47:08.224][[http-bio-443-exec-6]][DEBUG][c.c.p.m.root.CAPSMGWRootServlet]: Got request for file = /fontawesome-webfont.af7ae505a9eed503f8b8.

[PSMGW][10:47:08.387][[http-bio-443-exec-1]][DEBUG][c.c.p.modules.tunnel.CAPSMGWTunnel]: [f5f28aee-d5aa-4d22-b283-267fe58fc8ed] Connection to guacd and handshake completed successfully.

[PSMGW][10:47:08.388][[http-bio-443-exec-1]][INFO ][c.c.p.modules.tunnel.CAPSMGWTunnel]: Handshake finished.

[PSMGW][10:47:23.453][[Thread-12]][ERROR][o.a.g.w.GuacamoleWebSocketTunnelEndpoint]: Connection to guacd terminated abnormally: Connection to guacd timed out.

[PSMGW][10:47:23.454][[Thread-12]][DEBUG][o.a.g.w.GuacamoleWebSocketTunnelEndpoint]: Internal error during connection to guacd.

org.apache.guacamole.GuacamoleUpstreamTimeoutException: Connection to guacd timed out.

at org.apache.guacamole.io.ReaderGuacamoleReader.read(ReaderGuacamoleReader.java:180) ~[guacamole-common-1.0.0.jar:na]

at org.apache.guacamole.io.ReaderGuacamoleReader.readInstruction(ReaderGuacamoleReader.java:195) ~[guacamole-common-1.0.0.jar:na]

at org.apache.guacamole.protocol.FilteredGuacamoleReader.readInstruction(FilteredGuacamoleReader.java:81) ~[guacamole-common-1.0.0.jar:na]

at org.apache.guacamole.protocol.FilteredGuacamoleReader.readInstruction(FilteredGuacamoleReader.java:81) ~[guacamole-common-1.0.0.jar:na]

at org.apache.guacamole.protocol.FilteredGuacamoleReader.readInstruction(FilteredGuacamoleReader.java:81) ~[guacamole-common-1.0.0.jar:na]

at org.apache.guacamole.protocol.FilteredGuacamoleReader.read(FilteredGuacamoleReader.java:64) ~[guacamole-common-1.0.0.jar:na]

at org.apache.guacamole.websocket.GuacamoleWebSocketTunnelEndpoint$2.run(GuacamoleWebSocketTunnelEndpoint.java:246) ~[guacamole-common-1.0.0.jar:na]

Caused by: java.net.SocketTimeoutException: Read timed out

at java.net.SocketInputStream.socketRead0(Native Method) ~[na:1.8.0_242]

at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) ~[na:1.8.0_242]

at java.net.SocketInputStream.read(SocketInputStream.java:171) ~[na:1.8.0_242]

at java.net.SocketInputStream.read(SocketInputStream.java:141) ~[na:1.8.0_242]

at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) ~[na:1.8.0_242]

at sun.security.ssl.InputRecord.read(InputRecord.java:503) ~[na:1.8.0_242]

at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:975) ~[na:1.8.0_242]

at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:933) ~[na:1.8.0_242]

at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) ~[na:1.8.0_242]

at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284) ~[na:1.8.0_242]

at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326) ~[na:1.8.0_242]

at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) ~[na:1.8.0_242]

at java.io.InputStreamReader.read(InputStreamReader.java:184) ~[na:1.8.0_242]

at org.apache.guacamole.io.ReaderGuacamoleReader.read(ReaderGuacamoleReader.java:169) ~[guacamole-common-1.0.0.jar:na]

... 6 common frames omitted

[PSMGW][10:47:23.459][[Thread-12]][DEBUG][c.c.p.m.t.CAPSMGWFilteredSSLSocket]: Closing socket to guacd.

 

 

1 accepted solution

Accepted Solutions

L2 Linker

Hi everyone, problem was solved!

 

Problem was in HTML5 gateway server, PSMP get encorrect IP from DNS server when doing NSLOOKUP.

 

If you faced with that problem check DNS configuration on PSM Gateway server.

 

Many regards!

View solution in original post

2 REPLIES 2

L7 Applicator

This message also seems pretty self-explanatory. The PSMGW Java app can't connect to guacd. Either permissions, wrong config, or certificate issues. I think that you would learn a lot more about how the solution works and how to maintain it, if you did more troubleshooting yourself.

L2 Linker

Hi everyone, problem was solved!

 

Problem was in HTML5 gateway server, PSMP get encorrect IP from DNS server when doing NSLOOKUP.

 

If you faced with that problem check DNS configuration on PSM Gateway server.

 

Many regards!

  • 1 accepted solution
  • 2004 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!