-
Notifications
You must be signed in to change notification settings - Fork 35
Problem during the installation #75
Comments
Would you know what hornet version it is running? |
The last one because I do the git clone now. All the private tangle was created but every times it's tries to create Node1 response with : Error starting userland proxy: listen tcp4 0.0.0.0:15600: bind: address already in use |
For sure, it has to do with something running on port 15600 since the private-tangle node1 uses that specifc port
You can try and shut down the service running that port or try and change the port node1 should run in, within the docker-compose file. In the expose section and in the ports section You can use htop or docker ps to check if any service is using port 15600 |
Hello, I encountered an error while deploying the Private Tangle in Docker. It can't generate the private hornet docker container. The error is: It also shows a warning as: Any assistance. Many thanks |
Hi, I tried to install the private tangle on Macos and Linux but both of them hav some error.
In Macos, after the command ./private-tangle.sh: error: can't decode MINT_ADDRESS: encoding/hex: invalid byte: U+0020 ' '
ERROR: 1
In linux:
Creating spammer ... done
Creating node1 ... error
ERROR: for node1 Cannot start service node: driver failed programming external connectivity on endpoint node1 (6ef7f24ad18c876793d7e37f7501514cff2f6be7d3e8a9868e576fffa4c99b5a): Error starting userland proxy: listen tcp4 0.0.0.0:15600: bind: address already in use
ERROR: for node Cannot start service node: driver failed programming external connectivity on endpoint node1 (6ef7f24ad18c876793d7e37f7501514cff2f6be7d3e8a9868e576fffa4c99b5a): Error starting userland proxy: listen tcp4 0.0.0.0:15600: bind: address already in use
ERROR: Encountered errors while bringing up the project.
How can I resolve it ?
The text was updated successfully, but these errors were encountered: