If your build fails, the first thing you should check is whether you can build your files locally in your development environment.
If building locally is successful, then you should check that the dependencies installed by 4EVERLAND are the same as those used locally. For example, you may need to specify the Node.js version.
If your build fails and the
command is not found, then your dependencies are not installed. To install your dependencies, upload a configuration file for your NodeJS application, such as
package.json, listing all required dependencies.
Sites with large numbers of HTML files often take a lot of time to deploy.
If no file is found, IPFS will search for a file named ipfs-404.html in the path of the request. This file can be used to display 404 errors or redirects.
You need to first check that your site is visible on the "Verify on IPFS" link on the 4EVERLAND dashboard.
Your browser may not natively support parsing ENS domains. Install the MetaMask wallet browser extension to add support for ENS to any browser.
If your build fails with an exit status of 128, this may mean that we no longer have access to your GitHub repository. Make sure your repository is public, or that you grant us access through your GitHub login when you provide the link to the repository.