Blockchain crash receiving *Pong frame*

Bug Report

Blockchain crash, cannot use its websocket

Summary

Run embark blockchain and embark run dev on 2 separate terminals, along with my app backend(python) & frontend(js), and they both use web3 to connect with the blockchain. And the blockchain just crash receiving pong frame

Current behavior

screenshot

How to reproduce

Expected behavior

No crashing

If you encounter an error, please create a logfile using the following command and post the output here

$ embark run --nodashboard --logfile log.txt --loglevel trace

[2019-05-03 18:15:30:179] [info]:  Previous token has now been used.
[2019-05-03 18:15:30:183] [info]:  Enter the Cockpit with the following url: http://localhost:55555?token=275a8a0b-0d6b-4b33-9ea8-de72bbfff8cd
[2019-05-03 18:15:45:393] [error]:  Error: Pong frame received
    at WsParser.getHeader (/Users/vumacbook/Documents/employment/tomochain/relayerms/node_modules/simples/lib/parsers/ws.js:209:23)
    at WsParser._write (/Users/vumacbook/Documents/employment/tomochain/relayerms/node_modules/simples/lib/parsers/ws.js:51:8)
    at doWrite (_stream_writable.js:410:12)
    at writeOrBuffer (_stream_writable.js:394:5)
    at WsParser.Writable.write (_stream_writable.js:294:11)
    at Duplex.write [as _write] (/Users/vumacbook/Documents/employment/tomochain/relayerms/node_modules/embark/dist/lib/modules/blockchain_process/proxy.js:233:20)
    at doWrite (_stream_writable.js:410:12)
    at writeOrBuffer (_stream_writable.js:394:5)
    at Duplex.Writable.write (_stream_writable.js:294:11)
    at Socket.ondata (_stream_readable.js:666:20)
    at Socket.emit (events.js:182:13)
    at addChunk (_stream_readable.js:283:12)
    at readableAddChunk (_stream_readable.js:264:11)
    at Socket.Readable.push (_stream_readable.js:219:10)
    at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)

Please provide additional information about your system

OS: MacOS Embark Version: 4.0.2 Node Version: 10.13 NPM Version:6.7

Sometimes issues are related to Embark’s installation. Can you provide information on how Embark was installed?

npm install -D embark npm i -G embark

[jrainville]

Maybe your setup has a problem with using the blockchain proxy. You can disable it in config/blockhain.js but putting proxy: false.

The proxy is not vital for Embark to work. It’s mostly there for things like showing details on transactions and passing additional accounts to the Dapp.

[jrainville]

Great!

As for the documentation, the proxy is already explained a bit here: https://embark.status.im/docs/blockchain_configuration.html#Parameter-descriptions and you’re the only person to ever have had that issue, so I’d leave the docs like that for now. If other users have the same problem, hopefully they find this GH issue and see the answer.