MyCrypto: Can't connect with a Parity local node over WS

If you’ve experienced a bug, please provide the following information:

Description of the Issue

Hey guys, Thibaut from Parity here. Using the Dektop App on linux Mint with linux-x86-64_1.2.1_MyCrypto.AppImage I can’t manage to connect it to my local node by HTTP and the App is behaving weirdly depending on the configuration.

Steps to Reproduce

Run a parity node using parity --chain kovan --jsonrpc-cors all --ws-origins all -l rpc to allow to access both HTTP and WS server from any origin and log the rpc calls and answers made to the node.

Websockets custom node without luck

• Set a custom node with http://127.0.0.1:8546 (the default WS port).

–> The node does not get any rpc request and MyCrypto JS console shows:

HTTP node actually connecting to 8546 (while I specified 8545)

• Set a custom node with http://127.0.0.1:8545 (the default HTTP port). –> The node does get requests and answers. The Desktop App is happy and “works”. However, the requests are actually made on 8546

My questions :

• Can you explain the above mentioned behaviours?

Description of Your Machine

Ubuntu based linux Running linux-x86-64_1.2.1_MyCrypto.AppImage