Connection Server can not connect thingworx cluster: 403 Forbidden

[CZ_9645217]

Hi, 

I have completed the Thingworx cluster install. When I configure the connection server and start it, the log shows that the Thingworx address has been found through zookeeper, but 403 Forbidden. May I ask where I set it incorrectly? Below is my configuration, thanks in advance for your help！

cx-server {
transport.websockets {
    app-key = "05d80a7e-b442-4c29-ab34-c0af84e45e32"
}
discovery {
    connectionString = "XXXXXXX:2181,XXXXXXXX:2181,XXXXXXXXX:2181"
}
platform.transport = "websockets_active_active"
transport.websockets.service-discovery.enabled = true
protocol.port = 8081
protocol.http-server.ssl.enabled = false
transport.websockets.service-discovery {
    tls-enabled = false
service-name = "thingworx-http"
}
}

 Below is my log:

14:08:39.482 [NettyClient-NIO-6] ERROR c.t.s.i.t.netty.NettyChannelHandler - [ClientHandler: 9b8c888a] WebSocket error: Invalid handshake response getStatus: 403 Forbidden, closing connection!
io.netty.handler.codec.http.websocketx.WebSocketHandshakeException: Invalid handshake response getStatus: 403 Forbidden
at io.netty.handler.codec.http.websocketx.WebSocketClientHandshaker13.verify(WebSocketClientHandshaker13.java:274)
at io.netty.handler.codec.http.websocketx.WebSocketClientHandshaker.finishHandshake(WebSocketClientHandshaker.java:302)
at io.netty.handler.codec.http.websocketx.WebSocketClientProtocolHandshakeHandler.channelRead(WebSocketClientProtocolHandshakeHandler.java:83)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
at io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:102)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
at io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:436)
at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:321)
at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:295)
at io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:251)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:714)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at java.lang.Thread.run(Thread.java:748)

[yhan]

Hi @CZ_9645217,

The same exact websocket handshake error is found in article CS336191 although the issue was occurred in twx navigate connected to twx platform. You can check if it can resolve your issue, or you can provide us connection server log, zookeeper log, tomcat logs and thingworx logs and the time the issue happens for further investigation.

Thanks,

/Yoyo

[slangley]

Hi @CZ_9645217

Were you able to solve your issue with the help of the previous post?  If so, please mark that response as the Accepted Solution for the benefit of others with the same issue.

If you have not yet resolved it, please provide the logs previously requested.

Regards.

--Sharon