Skip to content

Error: http://127.0.0.1:11000/get_target_info: Connection Failed: Connect error: connection refused (os error 111) #196

@haohano

Description

@haohano

Hi,
I get an error when I run the docker image on azure VM:
`root@accvm:/home/my_user# docker run -it -e BLINDAI_AZURE_DCS3_PATCH=1 -p 9923:9923 -p 9924:9924 --device /dev/sgx/enclave --device /dev/sgx/provision -v /var/run/aesmd/aesm.socket:/var/run/aesmd/aesm.socket mithrilsecuritysas/blindai-server:latest /root/start.sh

Unable to find image 'mithrilsecuritysas/blindai-server:latest' locally
latest: Pulling from mithrilsecuritysas/blindai-server
06d39c85623a: Pull complete
4f4fb700ef54: Pull complete
8bfb0478a0d5: Pull complete
c7568ce3e661: Pull complete
ebe21cf0c66e: Pull complete
98cce156f4e6: Pull complete
394b33f0ac48: Pull complete
7299b6ef096c: Pull complete
Digest: sha256:d212c41852094111598dfc5f77d837a3b5eebe388b790482e258573f76451d23
Status: Downloaded newer image for mithrilsecuritysas/blindai-server:latest
thread '' panicked at 'called Result::unwrap() on an Err value: AesmCommunication(Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })', remote_attestation_sgx/src/quote_generation.rs:23:63
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

PCCS@1.15.0 start /opt/intel/sgx-dcap-pccs
node pccs_server.js "pm2"

2025-05-18 06:36:29.524 [info]: DB Migration (Ver.0 -> 1) -- Start
2025-05-18 06:36:29.529 [info]: DB Migration -- Done.
2025-05-18 06:36:29.566 [info]: DB Migration (Ver.1 -> 2) -- Start
2025-05-18 06:36:29.572 [info]: DB Migration -- Done.
2025-05-18 06:36:29.612 [info]: DB Migration (Ver.2 -> 3) -- Start
2025-05-18 06:36:29.616 [info]: DB Migration -- Done.
2025-05-18 06:36:29.687 [info]: HTTPS Server is running on: https://localhost:8081
Starting BlindAI server...
BlindAI telemetry is enabled
Error: http://127.0.0.1:11000/get_target_info: Connection Failed: Connect error: connection refused (os error 111)

Caused by:
connection refused (os error 111)

Stack backtrace:
0:
1:
2:
3:
4:
5:
6:
Attaching debugger
Error on exec SGX enclave
Enclave panicked..
`

What's more, I also encountered the same error during local deployment. How can I resolve it?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions