Connection not open after 1.3.0 installation

[baltcoinh]

SInce I installed v1.3.0, this error:
19/01/2019 07:37:58 [DEBUG] [WS ERROR] Error: connection not open
Is continuously appearing in my detailed debug log. With the same security configuration it didn't appear with the 1.2.1, 1.2.2 and 1.2.3 versions.
Operating in Mainnet over windows10 with native firewall and emsisoft security software.
Salute

[baltcoinh]

Maybe related with windows firewall, after deleting the rule allowing Timenode.exe to connect in private networks, message have dissapeared.

[baltcoinh]

After some hours running, error has reappeared. Main messages in debug.log (attached)
[DEBUG] Invalid log message format: {} is not a string.
[ERROR] Invalid providerUrl! eth_getFilterLogs not enabled.
[WS ERROR] Error: connection not open

timenode.txt

[housemobile]

1.3.0 won't connect with Ubuntu either

[e00dan]

@baltcoinh @housemobile

Do you still experience this problem? It's possible our Quiknode node started to randomly fail.

You could try switching node to other one / local node you use using network selector (click on the Network value in header bar and you will be able to change it).

[baltcoinh]

Yes, Have tried a while ago and I continue reciving these lines in debug log:
21/01/2019 14:20:30 [DEBUG] Attempting WS Reconnect.
21/01/2019 14:20:31 [ERROR] Invalid providerUrl! eth_getFilterLogs not enabled.
21/01/2019 14:20:31 [INFO] Reconnect tries: 20
Edited --> After some time [WS ERROR] Error: connection not open reappeared.
For the node switching, can anyone share a compatible node ip address? I'm not able to find any custom node to add.

[kosecki123]

QuikNode issues have been fixed and node back to normal.

Read more here #968 on the next steps to improve the TimeNode operations.