Troubleshooting and Support
Common Issues
If you encounter issues:
- Ensure all dependencies are correctly installed.
- Check that the required ports (8005-8008, 8010-8100) are not in use.
- Verify that symbolic links to
tlsn
andMP-SPDZ
exist in the expected locations (../tlsn
and../MP-SPDZ
relative to the repository root). - For
MP-SPDZ
issues, ensure that:- you've added
MOD = -DGFP_MOD_SZ=5
toMP-SPDZ/CONFIG.mine
at the repository root. - you've generated certificates for computation parties. If not, run
Scripts/setup-ssl.sh
underMP-SPDZ
directory at the repository root. - you've rebuilt the VM. If not, run
make replicated-ring-party.x
underMP-SPDZ
directory at the repository root.
- you've added
- If you run into Docker-related issues, try these commands to clean up your environment:
docker system prune -a --volumes
docker rm -f $(docker ps -aq)
docker volume prune -a -f
docker image prune -f - If you are trying single-server local configuration and getting
UnknownCA
error frombinance_prover
, make sure you don't have thebinance_prover
in the repository root directory. - If you get an error like 'P0.pem' is empty, try running
./Scripts/setup-ssl.sh 3
underMP-SPDZ
directory at the repository root. - If Notary Server's SSL certificate has expired, you can generate a new one by running the following commands from the repository root:
cd tlsn/notary/server/fixture/tls
openssl genpkey -algorithm RSA -out notary.key -pkeyopt rsa_keygen_bits:2048 \
&& openssl req -new -key notary.key -out request.csr -subj "/C=US/ST=State/L=City/O=Organization/OU=Department/CN=127.0.0.1" \
&& openssl x509 -req -in request.csr -signkey notary.key -out notary.crt -days 365 -extfile openssl.cnf -extensions v3_req - If you're asked to install
python3.xx-venv
package while running./setup_env.sh
, removevenv
directory under the repository root, install the package, and try again.
Getting Help
If you encounter any issues during installation, feel free to open an issue in our GitHub repository.