Hello!
I have an issue with CTRL-manager webclient_http.ctl. Sometimes in LogViewer appears the message like:
WCCOActrl (6), 2021.01.19 08:53:10.667, SYS, SEVERE, 141, Connection to client ::ffff:X.X.X.X could not be encrypted:
WCCOActrl (6), 2021.01.19 08:53:17.153, SYS, SEVERE, 141, Connection to client ::ffff:X.X.X.X could not be encrypted: http request
WCCOActrl (6), 2021.01.19 08:53:22.033, SYS, SEVERE, 141, Connection to client ::ffff:X.X.X.X could not be encrypted: http request
SMT (1), 2021.01.19 08:53:52.102, SYS, WARNING, 36/pmon, Blocking Manager WCCOActrl(6) detected. No heartbeat since 30 seconds.
It happens when a user enters into the web-page of Desktop UI. After this message manager starts to block. Network settings of the machines, which run Desktop UI are the same. What can cause the problem?
Thanks in advance!
Desktop UI connection problem
Search
Re: Desktop UI connection problem
Can you please add the information which WinCC OA version + patch level and which operating system is used.
Have you change any settings in your project before the problem occured for the first time?
Is the host name where the Desktop-Ui is running defined with its IP address and name in the hosts file of the operating system?
When the entry is missing you can check if it works when the hosts file is modified.
Best Regards
Leopold Knipp
Senior Support Specialist
Have you change any settings in your project before the problem occured for the first time?
Is the host name where the Desktop-Ui is running defined with its IP address and name in the hosts file of the operating system?
When the entry is missing you can check if it works when the hosts file is modified.
Best Regards
Leopold Knipp
Senior Support Specialist
Re: Desktop UI connection problem
We use 3.15 P027, Windows 10.
Those messages appear on the different machines sometimes. Id like to know, what is the main reason of the message "could not be encrypted"? Where should we look for to find out the reason?
We dont use the definition of host in hosts file and connect with ip-address. The adding of hostname to hosts havent solved the problem.
We have already checked the network settings and havent found anything suspicious. And theres also one interesting moment: if we change the ip address, user can enter the web-page Desktop-UI, but only one time. When user tries to enter after first connection, there are such messages in LogViewer like:
WCCOActrl (6), 2021.02.19 14:17:42.667, SYS, SEVERE, 141, Connection to client ::ffff:X.X.X.X could not be encrypted:
WCCOActrl (6), 2021.02.19 14:18:01.667, SYS, WARNING, 54, Unexpected state, HTTPServer::readMessage ::ffff:X.X.X.X, Connection reset by peer (10054)
Thanks in advance!
Those messages appear on the different machines sometimes. Id like to know, what is the main reason of the message "could not be encrypted"? Where should we look for to find out the reason?
We dont use the definition of host in hosts file and connect with ip-address. The adding of hostname to hosts havent solved the problem.
We have already checked the network settings and havent found anything suspicious. And theres also one interesting moment: if we change the ip address, user can enter the web-page Desktop-UI, but only one time. When user tries to enter after first connection, there are such messages in LogViewer like:
WCCOActrl (6), 2021.02.19 14:17:42.667, SYS, SEVERE, 141, Connection to client ::ffff:X.X.X.X could not be encrypted:
WCCOActrl (6), 2021.02.19 14:18:01.667, SYS, WARNING, 54, Unexpected state, HTTPServer::readMessage ::ffff:X.X.X.X, Connection reset by peer (10054)
Thanks in advance!
-
gschijndel
- Posts: 373
- Joined: Tue Jan 15, 2019 3:12 pm
Re: Desktop UI connection problem
This message can be seen if a HTTP client tries to connect to a HTTPS server.
Re: Desktop UI connection problem
Do you mean the Desktop UI http client?
We use only https..
We use only https..