Blocklet Server Troubleshooting Checklist for Self-inspection

Introduction#

When the Blocklet Server is started and running, it may encounter some common issues. It could be that the application cannot be accessed due to developer environment proxy, or it could be a domain resolution error caused by the Blocklet Server update mechanism.

After the network switch, the Blocklet Server did not restart, resulting in the domain name resolution records not being updated in time, which in turn caused the application to be inaccessible and so on.

To help developers troubleshoot these common issues, a self-checklist is specially written to help developers quickly pinpoint and solve some common problems.

Reading object.#

This article is aimed at developers with certain development experience.

Scope of application#

This checklist is for reference on how to self-diagnose and resolve when the Server cannot start normally and the application cannot be accessed after

Checklist#

• Make sure the server is completely shut down: If the local server cannot start, before executing blocklet server start, please execute blocklet server stop -f, and then check if the issue is resolved
• Check network proxy: The Blocklet Server and Blocklet are both running locally. When accessing the Server and Blocklet on the local machine, the global proxy should not be enabled. You can try disabling the global proxy, and then check if the issue is resolved.
• Check domain resolution: Both the Blocklet Server and Blocklet run locally, so should their DNS be resolved to the local machine IP? Please use commands like dig to check if the DNS resolution is correct. If incorrect, you need to see if your router has any special configurations.
• Check network changes: Given the previous two, if the local network has been switched, it is necessary to perform blocklet server start, and after restarting, the problem will most likely disappear.
• Check Blocklet Server version: If the server is not the latest beta version, use npm install -g @blocklet/cli@beta to upgrade, then restart the server. Does the issue disappear?
• Check the Node.js installation method: If Node.js is installed using fnm, it is recommended to try installing Node.js using nvm.
• Check Node.js version: In particular, there may be issues under v22.5.x, and it is recommended to use versions 21.6.0~22.4.x. Have the issues been resolved after switching Node.js?
• Check the package manager of blocklet cli: If @blocklet/cli is not installed using npm, it is recommended to uninstall @blocklet/cli, install it globally using npm, then restart the server and see if the issue is resolved?

Get help.#

If the above solution still cannot solve your problem, please go to our social forum https://community.arcblock.io/ for help.