Installation and usage of the platform

Sandbox mode of the platform: fixing issues

1. Error when starting the container for platform deployment:

2021-02-07 16:26:59,289 INFO [launcher] ./output/configs/nodes/node-0/accounts.conf
2021-02-07 16:27:07,432 INFO [launcher] ./output/configs/nodes/node-1/accounts.conf
2021-02-07 16:27:19,948 INFO [launcher] ./output/configs/nodes/node-2/accounts.conf
2021-02-07 16:27:28,023 INFO [launcher] Creating blockchain section for the node config files
Traceback (most recent call last):
  File "launcher.py", line 304, in <module>
    create_new_network()
  File "launcher.py", line 228, in create_new_network
    create_blockchain(addresses, nodes)
  File "launcher.py", line 106, in create_blockchain
    network_participants.append(ConfigFactory.from_dict({"public-key": addresses.get_keys()[i],
IndexError: list index out of range

Cause: Second start of the container.

Solution: Delete the working directory with the platform files and start over by downloading the docker-compose.yml file.

2. Platform startup error after successful deployment:

ERROR: for node-1 Cannot create container for service node-1: Conflict. The container name "/node-1" is already in use by container "47cfd7a517e160d201ae969b24392ca0bc2b9720c73e7324dac45daaa24814cb". You have to remove (or rename) that conCreating node-2 ... error

ERROR: for node-2 Cannot create container for service node-2: Conflict. The container name "/node-2" is already in use by container "ccd28832f1fb5457186e50d5e5Creating node-0 ... error
tainer to be able to reuse that name.

ERROR: for node-0 Cannot create container for service node-0: Conflict. The conCreating postgres ... error
eb8ac184f88195f1a560ee8ef7ade5c46f899d". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for postgres Cannot create container for service postgres: Conflict. The container name "/postgres" is already in use by container "d4bc6d758faafcc9b2bc352b9cbcc5dc909f2959059b7abf17db0088916506d1". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for node-1 Cannot create container for service node-1: Conflict. The container name "/node-1" is already in use by container "47cfd7a517e160d201ae969b24392ca0bc2b9720c73e7324dac45daaa24814cb". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for node-2 Cannot create container for service node-2: Conflict. The container name "/node-2" is already in use by container "ccd28832f1fb5457186e50d5e58f98ed3b35c944931589a42a0262a205a17393". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for node-0 Cannot create container for service node-0: Conflict. The container name "/node-0" is already in use by container "7ed421ac8c8c5ca91a916970c1eb8ac184f88195f1a560ee8ef7ade5c46f899d". You have to remove (or rename) that container to be able to reuse that name.

ERROR: for postgres Cannot create container for service postgres: Conflict. The container name "/postgres" is already in use by container "d4bc6d758faafcc9b2bc352b9cbcc5dc909f2959059b7abf17db0088916506d1". You have to remove (or rename) that container to be able to reuse that name.
ERROR: Encountered errors while bringing up the project.

Cause: Containers of individual nodes or services are already in use by running containers.

Solution: If you need to rebuild the platform again, stop it with the docker-compose down command. Use the command docker stop [container ID] to stop running containers of nodes and services. You can enter several running container IDs in a row, separated by a space, or stop all containers with the command docker stop $(docker ps -a -q). Then use the command docker rm [container ID] to remove them. The IDs of the containers used are available in error reports like the one above. You can remove multiple containers or all used containers with a single command using a similar syntax.

3. Container startup error:

ERROR: for nginx-proxy Cannot start service nginx-proxy: driver failed programming external connectivity on endpoint nginx-proxy (86add881e45535e666443cb00e6a6cb66f79a906e412d4f78d2db9d81c6d63d7): Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use

ERROR: for nginx-proxy Cannot start service nginx-proxy: driver failed programming external connectivity on endpoint nginx-proxy (86add881e45535e666443cb00e6a6cb66f79a906e412d4f78d2db9d81c6d63d7): Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use
ERROR: Encountered errors while bringing up the project.

Cause: The 80:80 port on your machine is occupied by another application.

Solution: Stop the containers with the docker-compose down command. Then change the ports parameter of the nginx-proxy section in the docker-compose.yml file, selecting a free port:

nginx-proxy:
  image: nginx:latest
  hostname: nginx-proxy
  container_name: nginx-proxy
  ports:
    - "81:80"

After that the client and REST API will be available at 127.0.0.1:81 or localhost:81. The rest of the services will be available at the addresses with their former ports.

4. Error when navigating to 127.0.0.1 or localhost in Mozilla Firefox:

SSL_ERROR_RX_RECORD_TOO_LONG

Reason: By default, the localhost is accessed via HTTPS, but SSL is not provided when deploying the platform in the Sandbox mode.

Solution: Enter the full address using HTTP: http://127.0.0.1 or http://localhost.

Hint

For the list of error codes for the Waves Enterprise blockchain platform, see System errors.

See also

Deploying the platform in the trial mode (Sandbox)

Node monitoring configuration in the Sandbox mode

System errors