Contents


Before you read the build FAQ below, check if you have the proper build settings for your site first. Learn more about Common Build Settings.



Runtime Selection

If you are going to deploy a static website, use Static Site as the Runtime for your site. This environment has Node, Python, Go, and Ruby pre-installed..

If you are going to deploy web services, for example, Django, or rails apps, use Python or Ruby runtime. It has the necessary libs pre-installed for you.

If you are going to deploy a mix, with both frontend and backend, for example, in Next.js (you can choose Static Site Generation (“SSR”) or Server-Side Rendering (“SSG”)), use the backend runtime. So use the Node runtime for Next.js for “SSR”.



1. Unknown system error -122 …

Because the project you deploy is larger than the runtime environment you purchased. You can contact customer service to upgrade your spec to get a higher cloud disk to complete the build and deployment. 

...
2021-03-16 01:47:26 error An unexpected error occurred: "Unknown system error -122: Unknown system error -122, copyfile ....".
...



2. [INFO] Worker exiting

Each build is time-limited; if it exceeds, your build will automatically shut down. 

2021-03-13 21:59:00 ==> 😞 Build failed
[2021-03-13 21:59:00 +0800] [12] [INFO] Worker exiting (pid: 12)
[2021-03-13 21:59:01 +0800] [9] [INFO] Shutting down: Master



3. There appears to be trouble with your network connection

It may be that the project uses dependencies (CSS, JS, photos, etc.), and the build cannot access these resources during the build process. 

...
2021-02-08 19:46:51 info There appears to be trouble with your network connection. Retrying...
...



4. ERROR: Could not install packages due to an OSError: [Errno 28] No space left on device

Because the project you deploy is larger than the runtime environment you purchased. You can contact customer service to upgrade your spec to get a higher cloud disk to complete the build and deployment. 

...
2021-04-02 01:36:44 ERROR: Could not install packages due to an OSError: [Errno 28] No space left on device
...



5. The build was successful, but “upload failed”

...
2021-06-21 22:29:42 ==> Upload the build folder 'web/dist' to CDN...
2021-06-21 22:37:42 ==> Upload failed
2021-06-21 22:37:42 ==> 😞 Build failed
[2021-06-21 22:37:42 +0800] [9] [INFO] Handling signal: term
[2021-06-21 22:37:42 +0800] [12] [INFO] Worker exiting (pid: 12)
[2021-06-21 22:37:42 +0800] [9] [INFO] Shutting down: Master


If the above situation occurs in the builder location in Hong Kong, and the site is deployed to Mainland China, then this is caused by the busy cross-border networks at night (China Time around 8:30 pm - 1:00 am GMT +8).

You can try again in the morning or afternoon in China time or contact us to upgrade to use dedicated network lines to improve your deployment’s performance.



6. npm ERR! nospc ENOSPC: no space left on device

...
2021-05-25 21:38:20 npm ERR! code ENOSPC
2021-05-25 21:38:20 npm ERR! syscall write
2021-05-25 21:38:20 npm ERR! errno -28
2021-05-25 21:38:20 npm ERR! nospc ENOSPC: no space left on device, write
2021-05-25 21:38:20 npm ERR! nospc There appears to be insufficient space on your system to finish.
2021-05-25 21:38:20 npm ERR! nospc Clear up some disk space and try again.
2021-05-25 21:38:20 npm ERR! code ENOSPC
...


Because the project you deploy exceeds the storage size in the 21YunBox standard operating environment, you can contact customer service to upgrade or purchase a high-performance builder to solve this problem.



7. I’m moving my Github Pages to 21YunBox, but I can’t get it to work.

Because your code and related assets, including HTML, JS, CSS, and images, are built and stored on your Github Pages repo, for example, https://github.com/<GITHUB_USER_ID>/<GITHUB_USER_ID>.github.io, so you don’t need to build again on 21YunBox.

Follow the below settings to build your site:

Github Pages build setting for 21YunBox
Github Pages build setting for 21YunBox



Others?

If you need more help, email us by explaining what you do (or are trying to do), and we’re happy to help.



Ready to try 21YunBox?

Get Started