
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
WARN in proxy log as "Error during stream authentication as Server"
Hello all,
My server is up
However, here what I find in my System Proxy logs :
73645 20230606T172430.747+0200 WARN {myservernameinlowercase} System.Proxy.Qlik.Sense.Communication.Communication.Tcp.StreamFactory 121 d6add80f-034f-4393-97c5-c67842b7c59d {myservernameinuppercase}\{myserviceaccount) Error during stream authentication as Server Authentication failed because the remote party has closed the transport stream. at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)↵↓ at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result)↵↓ at Qlik.Sense.Communication.Communication.Tcp.StreamFactory.<>c__DisplayClass10_1.<Negotiate>b__2(IAsyncResult result) d6add80f-034f-4393-97c5-c67842b7c59d
and in my audit proxy logs
187603 20230606T172439.400+0200 WARN {myservernameinlowercase} Audit.Proxy.Proxy.Communication.Streams.AsyncStreamFactory 73 229df28c-0d77-45d3-abb6-d347c20ff1cb {myservernameinuppercase}\{myserviceaccount} Connection negotiation as server failed [someipadress]:443 <-> [anotheripadress]:44470, using: SslNoClientValidation cac7f8abae29573248f6aebe38cff949d61b8dd8
I'm not a big fan of having error messages in log and it doesn't sound good , despite the fact the server is up.
For information : Qlik Sense May 2022 Patch6
Best regards,
Simon
Accepted Solutions


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @simonaubert,
Have a look at Qlik KB article Error during stream authentication as server logged in Qlik Sense Proxy logs.
The message should be reviewed together with a symptom seen by end users, such as a dropped connection or a reconnect. By itself, the message is not an indication of an error.
- If the error will persist in Qlik Sense Proxy logs, it is necessary for an IT or network administrator to verify if any external or internal programs are attempting to do a port or health check on the server (such as running a scan).
- Other root causes could be firewalls or reverse proxies interfering with ports that Qlik Sense needs for communication.
- If the warning correlates with the same time stamp as a port health check scan which utilizes TCP scanning, a potential resolution would be to have the device performing the health check to use URL for monitoring check check as outlined in the support article Qlik Sense Proxy Health Check Endpoint(s).
Best Regards
Help users find answers! Don't forget to mark a solution that worked for you!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The error message "Error during stream authentication as Server" denotes a technical issue with the remote party authentication process carried out by the Qlik Sense proxy server.
It's required to investigate the connection between the remote party and the Qlik Sense proxy server in order to fix this software error. You can follow the instructions listed below:
Check the credentials being used by the remote party to connect to the Qlik Sense proxy server, including the username and password.
Check the TLS version that the remote party is using. Make sure that it complies with the Qlik Sense proxy server's minimum requirement of TLS 1.2 or higher.
Determine and remove any network restrictions or firewalls that may be interfering with the connection between the distant Qlik Sense proxy server and the client.


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @simonaubert,
Have a look at Qlik KB article Error during stream authentication as server logged in Qlik Sense Proxy logs.
The message should be reviewed together with a symptom seen by end users, such as a dropped connection or a reconnect. By itself, the message is not an indication of an error.
- If the error will persist in Qlik Sense Proxy logs, it is necessary for an IT or network administrator to verify if any external or internal programs are attempting to do a port or health check on the server (such as running a scan).
- Other root causes could be firewalls or reverse proxies interfering with ports that Qlik Sense needs for communication.
- If the warning correlates with the same time stamp as a port health check scan which utilizes TCP scanning, a potential resolution would be to have the device performing the health check to use URL for monitoring check check as outlined in the support article Qlik Sense Proxy Health Check Endpoint(s).
Best Regards
Help users find answers! Don't forget to mark a solution that worked for you!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The error message "Error during stream authentication as Server" denotes a technical issue with the remote party authentication process carried out by the Qlik Sense proxy server.
It's required to investigate the connection between the remote party and the Qlik Sense proxy server in order to fix this software error. You can follow the instructions listed below:
Check the credentials being used by the remote party to connect to the Qlik Sense proxy server, including the username and password.
Check the TLS version that the remote party is using. Make sure that it complies with the Qlik Sense proxy server's minimum requirement of TLS 1.2 or higher.
Determine and remove any network restrictions or firewalls that may be interfering with the connection between the distant Qlik Sense proxy server and the client.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @Chip_Matejowsky @shelly23 Thanks. We will investigate.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Chip_Matejowsky We are facing a slightly similar issue on 2 proxy servers, right after installing latest windows patches. While opening the unpublished apps on corresponding URLs, we are getting "No Available Engine Found" error and logs have this "Error during stream authentication as Server" messages continuously. The environment has Central and RIM nodes. This error is visible only for couple of proxy nodes (neither the issue nor error logs generated for other proxy nodes). We are operating on TLS 1.2 and there are no restrictions or firewalls interfering with the communication.
Please suggest on the potential root cause and resolution.
