WebSocket connection failed - RR_CONNECTION_TIMED_OUT
See original GitHub issueInsight request https://explorer.bitcore.cc/#/BTX/mainnet/address/2aup33vQpXm3TJmNoa3CHXJggf3gxxa9vi
JavaScript browser console output
WebSocket connection to 'wss://explorer.bitcore.cc:53703/' failed: Error in connection establishment: net::ERR_CONNECTION_TIMED_OUT
openConnection @ ion-dev.js?v=3.2.3:102
start @ ion-dev.js?v=3.2.3:18
(anonymous) @ ion-dev.js?v=3.2.3:468
(index):39 GET https://explorer.bitcore.cc:35729/livereload.js?snipver=1 net::ERR_CONNECTION_TIMED_OUT
The insight explorer is running with docker-compose.
Here is my docker-compose.yml
version: '3'
services:
bitcored:
build:
context: ./docker-bitcored
dockerfile: ./Dockerfile
image: bitcored
container_name: bitcored
command:
-whitebind=172.21.0.10:8555
-whitelist=172.21.0.0/24
-whitelist=127.0.0.1
-txindex=1
-maxconnections=100
-rpcbind=172.21.0.10
-rpcallowip=172.21.0.0/24
-rpcallowip=127.0.0.1
-port=8555
-rpcport=8556
-rpcuser=xx
-rpcpassword=xx
restart: always
networks:
insight-net:
ipv4_address: 172.21.0.10
ports:
- 8555:8555
expose:
- 8555
- 8556
volumes:
- /home/bitcore:/data
mongodb:
image: mongo:3.4-jessie
container_name: mongodb
restart: always
networks:
insight-net:
ipv4_address: 172.21.0.11
ports:
- 127.0.0.1:27017:27017
expose:
- 27017
volumes:
- /home/mongodb:/data/db
bitcore-node:
build:
context: .
dockerfile: ./Dockerfile.bitcore-node.btx
image: bitcore-node
container_name: bitcore-node
restart: always
networks:
insight-net:
ipv4_address: 172.21.0.13
ports:
- 127.0.0.1:8100:8100
- 3000:3000
environment:
- "DB_HOST=mongodb"
- "BITCORE_CONFIG_PATH=/bitcore/bitcore.config.json"
depends_on:
- mongodb
- bitcored
insight:
image: insight-previous
build:
context: .
dockerfile: ./Dockerfile.insight-previous.btx
container_name: insight-previous
restart: always
networks:
insight-net:
ipv4_address: 172.21.0.14
ports:
- 8080:8080
environment:
- "ENV=prod"
- "CHAIN=BTX"
- "NETWORK=mainnet"
- "API_PREFIX=https://api.bitcore.cc/api"
depends_on:
- bitcore-node
networks:
insight-net:
driver: bridge
ipam:
driver: default
config:
- subnet: 172.21.0.0/24
Is something still wrong in the config? What are the ports 35729 and 53703 needed for? In which way do I have to configure that?
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
WebSocket connection failed. Error in browser console, since ...
js:544 , started to show in the Chrome console. No change was done to the existing dashboards, all was working great before.
Read more >WebSocket connection failed: Error during ... - Stack Overflow
I am trying to integrate Socket.io with Angular and I'm having difficulties making a connection from the client ...
Read more >websocket connection failed - ROS Answers
I get the following error in the browser console: roslib.min.js:1 WebSocket connection to 'ws://127.0.0.1:9090/' failed: Error in connection ...
Read more >Error with WebSocket - Microsoft Q&A
Hello I get the error: WebSocket connection to 'wss://localhost:54970/Dashboard.Server/' failed: Error in connection establishment: net:: ...
Read more >How to resolve the error: "Could not open websocket connection
log messages fail to show. The issue is seen when WebSocket requests are not passed correctly by a reverse proxy or a load...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is an issue where webpack isn’t resolving the symlinks when building. It’s really annoying. Are you able to install bitcore-lib-btx from npm? If so, I think by running an npm install in that directory, or doing an npm install bitcore-lib-btx
Using lerna and webpack apparently doesn’t work very well.
The websocket issue is resolved. Thank you.