Connecting from Server over WebSockets "Failed to connect" PC=0 Error?

P Paul Stringer 3 years 7 months ago
350 3 0

Hi,
 
I'm attempting to connect to a ZD500 running LinkOS over WebSockets. We've followed the Configuring a WebSocket End Point Guide.
 
We've successfully now have the printer  performing the initial handshake over WebSockets with the Server. At the point of Switching Protocols we see this error.
 
[10-07-2016 00:40:28.802][Info][00001012][conn1.1] HTTP/1.1 101 Switching Protocols
[10-07-2016 00:40:28.805][Info][00010007][conn1.1] Content Length is 0
[10-07-2016 00:40:28.811][Error][800C000F][conn1.1] Failed to connect (SP = 1, CU = 1, UW = 1, AC = 1, PC = 0)
 
The documentation hints this is a web server configuration error but does not describe what the meaning of each of the fields in this error is. The failing result is PC = 0.
 
Does anybody know what the "PC" stands for so that we can narrow down where the issue is?
 
Here are the results of the getvar weblink
 
weblink.
weblink.enable : on
weblink.printer_reset_required : no
weblink.restore_defaults
weblink.logging.
weblink.logging.entries : ...
weblink.logging.max_entries : 100 , Choices: 0-10000
weblink.logging.clear
weblink.ip.
weblink.ip.conn1.
weblink.ip.conn1.location : https://xxx.xxx.xxx/xxx
weblink.ip.conn1.retry_interval : 10 , Choices: 1-600
weblink.ip.conn1.proxy : 
weblink.ip.conn1.maximum_simultaneous_connections : 10 , Choices: 1-100
weblink.ip.conn1.authentication.
weblink.ip.conn1.authentication.add
weblink.ip.conn1.authentication.remove
weblink.ip.conn1.authentication.entries : 
weblink.ip.conn1.test.
weblink.ip.conn1.test.location : http://www.zebra.com/apps/linktest
weblink.ip.conn1.test.test_on : failure , Choices: off,failure,interval,both
weblink.ip.conn1.test.retry_interval : 900 , Choices: 1-1800
weblink.ip.conn1.num_connections : 0
weblink.ip.conn2.
weblink.ip.conn2.location : 
weblink.ip.conn2.retry_interval : 10 , Choices: 1-600
weblink.ip.conn2.proxy : 
weblink.ip.conn2.maximum_simultaneous_connections : 10 , Choices: 1-100
weblink.ip.conn2.authentication.
weblink.ip.conn2.authentication.add
weblink.ip.conn2.authentication.remove
weblink.ip.conn2.authentication.entries : 
weblink.ip.conn2.test.
weblink.ip.conn2.test.location : http://www.zebra.com/apps/linktest
weblink.ip.conn2.test.test_on : failure , Choices: off,failure,interval,both
weblink.ip.conn2.test.retry_interval : 900 , Choices: 1-1800
weblink.ip.conn2.num_connections : 0
weblink.cloud_connect.
weblink.cloud_connect.enable : on , Choices: on,off
weblink.cloud_connect.connect
weblink.cloud_connect.status : NOT ACTIVE
weblink.cloud_connect.connection_key : 0000000000
weblink.cloud_connect.configuration_key : 0000000000
weblink.cloud_connect.configuration_confirmation : none , Choices: none,accept,reject,complete
weblink.zebra_connector.
weblink.zebra_connector.version : 0.04
weblink.zebra_connector.enable : on , Choices: on,off
weblink.zebra_connector.proxy : 
weblink.zebra_connector.authentication.
weblink.zebra_connector.authentication.add
weblink.zebra_connector.authentication.remove
weblink.zebra_connector.authentication.entries : 
 
===END===
 

Please Register or Login to post a reply

3 Replies

T Tobia Scapin

Thanks to zebra help desk I discovered that PC=0 means that the protocol header is not correctly set in the websocket handshake.
In my case I have missed "Sec-WebSocket-Protocol" header with "v1.weblink.zebra.com" (or the same value of the request)

T Tobia Scapin

I have the same problem, do we know how PC=0 means? Thank you.

J Josh Wilson

Hi Paul,
Did you ever get this answered? I am have the same issue and was wonder if you could share any knowledge with me specifically around the PC=0 error.

CONTACT
Can’t find what you’re looking for?