cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to connect 9.1.4

SOLVED
Highlighted
Occasional Contributor

Unable to connect 9.1.4

I have a appliance Pulse Secure 9.1R3. I have make an updgrade on version 9.1R4 but now the connection is impossible. When I use Network Connect, I have a script error with the method « addEventListener « . ». When I use Pulse Secure, I have « Network Error 1115».

At the events logs, I have "Failed to set ACLs for user with NCIP".

 

If I make a rollback in 9.1R3, it’s work. I test the version 9.1R4.1, I have the same problem.

 

 

 

Anybody have the same problem?

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
New Contributor

Re: Unable to connect 9.1.4

5 REPLIES 5
Highlighted
New Contributor

Re: Unable to connect 9.1.4

I have the exact same issue.

/Johan

Highlighted
New Contributor

Re: Unable to connect 9.1.4

There is a KB article that explains the issue:

https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB40872

 

But I have the default ACL:

*:*

already in place. And it this does not work.

Highlighted
New Contributor

Re: Unable to connect 9.1.4

Highlighted
Occasional Contributor

Re: Unable to connect 9.1.4

Thank's, it's work

Highlighted
New Member

Re: Unable to connect 9.1.4

Similar but slightly different:

After we upgraded from 9.0Rx to 9.1R7 we noticed employees reporting 'addEventListener' issues inside the (older) Network Connect client on Windows 10 devices.

To ensure continuity we fixed it as follows, go to:

Configuration -> Security -> Advanced which should bring up the "Custom HTTP Headers" page.

Insert the following:

HTTP Header:

X-UA-Compatible

Header Directive:

IE=Edge

 

The error will then go away (as Internet Explorer is the issue here).

We still have to deal with some other fallout but hopefully this will help someone else.

 

Cheers.

(I'm adding it here because this is the only hit when searching for "addEventListener")