VMware Horizon Community
Sammyant
Contributor
Contributor

Access Point 2.5 Blast Error

Hi,

I have trouble with Access Point 2.5: On Horizon 6.2 or 7 didn't work HTML Blast access (PCOIP or RDP works fine)

When connecting to the Access point  is displayed logon form, but after login-password and click "enter" you recive an error “Failed to connect to the Connection Server.”

Direct connection via Connection Server works fine.

At the same time in events on connection server I find the "Audit success" and "User has logged in"

On AP’s esmanager.log there is such Java NullPointerException

[nioEventLoopGroup-31-2]ERROR proxy.HttpsProxyRequestHandler: Error during request interceptor invocation

java.lang.NullPointerException

at com.vmware.euc.gateway.edgeservice.sdk.session.Session.hasCookie(Session.java:163)

If I using old AP v.2.0 with the same configuration - all protocols works fine (blast, pcoip, rdp) on both version Horizon (6.2,7)

I try install 2.5 in test environment, without any firewall rules and get the same blast error on both Horizon version.

On the Connection Server Blast Gateway, PCOIP Gateway, HTTPs Tunnel unchecked. I disabled ‘origin check’ on Connection Server.

I try changing option, ip - name. but error disappear only if I using AP v.2.0

config for AP 2.5.

    {

      "identifier": "VIEW",

      "enabled": true,

      "proxyDestinationUrl": "https://connectionservername:443",

      "proxyDestinationUrlThumbprints": "sha1= **********",

      "pcoipEnabled": true,

      "pcoipExternalUrl": "ip_accesspoint:4172",

      "blastEnabled": true,

      "blastExternalUrl": "https://vdiname.com:8443",

      "tunnelEnabled": true,

      "tunnelExternalUrl": "https://vdiname.com:443",

      "proxyPattern": "/",

      "gatewayLocation": "External",

      "windowsSSOEnabled": false

    }

Thanks

Denis

Labels (1)
0 Kudos
4 Replies
jeniferslabaugh
Enthusiast
Enthusiast

I had that issue recently after upgrading a 6.2.0 customer to 7.  For me, implementing the fix listed in this KB fixed it: VMware KB: Accessing the Horizon View Administrator page displays a blank error window in Horizon 7

0 Kudos
Sammyant
Contributor
Contributor

Yes, I try disabled ‘origin check’ on Connection Server. Have the same error.

Have you got any ideas?

0 Kudos
bad1
Contributor
Contributor

  • A "Failed to connect to the Connection Server" error occurs when you use HTML Access to connect to a non-EN language Connection Server instance with Access Point 2.5.x integration.
    Workaround: None.

Release Notes for VMware Horizon 7 version 7.0

0 Kudos
massmans
Contributor
Contributor

Denis,

Is your vdiname.com an externally resolved address?   From what I have learned with Access Point, these two entries have to be the external FQDN address that can be externally resolved.     We use F5 load balancers with GTM and have the same FQDN for internal and external access.   But internal traffic is routed to the internal connection servers VIP.   External access goes to the same FQDN but is directed to an external IP that has FQDN registered with AWS. 

      "blastExternalUrl": "https://vdiname.com:8443",

      "tunnelEnabled": true,

      "tunnelExternalUrl": "https://vdiname.com:443",

We also found that this entry has to have the external DMZ IP address. 

pcoipExternalUrl=extIPaddress:4172

0 Kudos