The Firefly Sandbox UI shows that the left column is blank and missing

[cooooo966]

Hello, I'm following the Getting Started tutorial to run firefly. When I open the Firefly Sandbox UI, it doesn't look right. I can't see the left column, which is messages, tokens, and contracts, it's completely blank on the web page. Like this:

When I see ghcr.io/hyperledger/firefly-sandbox:latest mirror container log, it outputs:

> [email protected] start
> node .

UI Served from /app/ui/build
Application listening on port 3001
Error
    at new HttpError (/app/server/node_modules/routing-controllers/cjs/http-error/HttpError.js:17:22)
    at new InternalServerError (/app/server/node_modules/routing-controllers/cjs/http-error/InternalServerError.js:10:9)
    at FireFly.errorHandler (/app/server/dist/src/clients/fireflySDKWrapper.js:14:19)
    at /app/server/node_modules/@hyperledger/firefly-sdk/dist/http.js:64:30
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
2024-12-11T08:00:04.603Z [SimpleWebSocket] Connecting websocket client KoLqajXyX6AHtxF7dksvp
2024-12-11T08:00:04.606Z [SimpleWebSocket] No namespace provided for client KoLqajXyX6AHtxF7dksvp, aborting websocket setup.
Error: Can't set headers after they are sent.
    at SendStream.headersAlreadySent (/app/server/node_modules/send/index.js:386:13)
    at SendStream.send (/app/server/node_modules/send/index.js:613:10)
    at onstat (/app/server/node_modules/send/index.js:725:10)
    at FSReqCallback.oncomplete (node:fs:203:5)

[EnriqueL8]

@cooooo966 thanks for raising this!

Would be interesting to see if the FireFly container was healthy

[cooooo966]

@EnriqueL8 I don't seem to see any other problems with the firefly container. How do I check this?

[cooooo966]

@EnriqueL8

[cooooo966]

And I tried all UI links, only the Sandbox UI can access, but there is a problem of incomplete display, web UI and Swagger API UI can not access, show that the browser can not establish a connection to the server.
When I look at the ff log, the error seems to show up here:

dev_sandbox_0       | > [email protected] start
dev_sandbox_0       | > node .
dev_sandbox_0       | 
dev_sandbox_0       | UI Served from /app/ui/build
dev_sandbox_0       | Application listening on port 3001
dev_sandbox_0       | npm notice 
dev_sandbox_0       | npm notice New major version of npm available! 8.19.4 -> 11.1.0
dev_sandbox_0       | npm notice Changelog: <https://github.com/npm/cli/releases/tag/v11.1.0>
dev_sandbox_0       | npm notice Run `npm install -g [email protected]` to update!
dev_sandbox_0       | npm notice 
dev_sandbox_0       | npm ERR! path /app/server
dev_sandbox_0       | npm ERR! command failed
dev_sandbox_0       | npm ERR! signal SIGTERM
dev_sandbox_0       | npm ERR! command sh -c -- node .
dev_sandbox_0       | 
dev_sandbox_0       | npm ERR! A complete log of this run can be found in:
dev_sandbox_0       | npm ERR!     /home/node/.npm/_logs/2025-02-17T15_42_11_901Z-debug-0.log
dev_sandbox_0       | 
dev_sandbox_0       | > [email protected] start
dev_sandbox_0       | > node .
dev_sandbox_0       | 

The logs for all three sandboxes have the same error.

[cooooo966]

@EnriqueL8 Thank you for your reply! I've solved this problem so far.
After investigation, it was found that the image download was incomplete due to network reasons, and it was often stuck in the "pulling fs layer" step. The above problem was solved by modifying DNS configuration and restarting the docker service.

# modifying DNS configuration
vim /etc/resolv.conf

This change is temporary and the DNS configuration will be restored by restarting the system.

# restarting the docker service
sudo systemctl daemon-reload
sudo systemctl restart docker