Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I am getting below error in logs while Publishing to QS. Please suggest a solution.
target:
WebSocket {
_events:
[Object: null prototype] {
open: [Function],
close: [Function],
error: [Function],
message: [Function] },
_eventsCount: 4,
_maxListeners: undefined,
readyState: 3,
protocol: '',
_binaryType: 'nodebuffer',
_closeFrameReceived: false,
_closeFrameSent: false,
_closeMessage: '',
_closeTimer: null,
_closeCode: 1006,
_extensions: {},
_isServer: false,
_receiver: null,
_sender: null,
_socket: null,
url:
'wss://<has my server name>:4747/app/4cb2c5d0-b4d8-4805-8696-TFN4xlADiU6H',
_req: null },
type: 'error',
message: 'connect ETIMEDOUT <has my server name>:4747',
error:
{ Error: connect ETIMEDOUT <has my server name>:4747
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1107:14)
errno: 'ETIMEDOUT',
code: 'ETIMEDOUT',
syscall: 'connect',
address: '<has my server name>',
port: 4747 } }
- ERROR:
2020-06-30 02:10:26.607: Publish to Qlik application FAILED
Hi.
Did you add the QS Server Name to the /etc/hosts on your QDC Box?
Just my 2 cents.
Hi @qliktechie15 ,
From this I would check port 4747 on the Qlik Sense side , and ensure that the port is open and available. The error your seeing is most commonly written when the engine hostname is wrong or the port number is locked down, and the firewall needs to allow it.
Hope that helps.
David
Thanks @DaveHowland for the reply !
The post 4747 is open and LISTENING at the Qlik Sense side- TCP [::]:4747 [::]:0 LISTENING.
The engine hostname (QS server address) is also set correctly in the core.env properties.
Do I need to change anything in the CreateQlikApp.js file as well (as the error message points to that file) ?
Thank you !
Hi.
Did you add the QS Server Name to the /etc/hosts on your QDC Box?
Just my 2 cents.