Answers to frequently asked questions.

Warning about next-auth version

After npm install or npm ci you can have this warn :

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'next-auth@4.14.0',
npm WARN EBADENGINE   required: { node: '^12.19.0 || ^14.15.0 || ^16.13.0' },
npm WARN EBADENGINE   current: { node: 'v18.12.1', npm: '8.19.2' }

The version required by next-auth is 18.12. In any case, the NodeJS version doesn’t really matter for the next-auth library and you can ignore this warning or upgrade your NodeJS.

Change default hostname or port for application

By default the application starts a server on and your application will therefore be accessible on any IP available on your host at port 3000.

If you want to make your application accessible only on localhost:3000 (for use with a proxy for example), edit the package.json file and modify this line :

"start": "next start",

To :

"start": "next start -H localhost",

And, if you want to change the default port (for example 4000), you can change this line like this :

"start": "next start -H localhost -p 4000",

Thank you to Philipp Rintz for its contribution to the reflection on this issue.

Does BorgWarehouse have to be installed on the same server as borgbackup ?

Yes. I am not saying that it is impossible to run BorgWarehouse on a server that would run the shells on another. However, the application is now thought and designed to run on the server that will store the repositories and run the server part of borgbackup.

Thank you to Pierrick Brun for its contribution.

What is the NEXT_TELEMETRY_DISABLED environment variable ?

Next.JS is the amazing open-source web development framework used to build BorgWarehouse. Next.JS can collect completely anonymous telemetry regarding usage. This information is used to shape Next.js’ roadmap and prioritize features.

If you want to help Next.JS by sharing anonymous telemetry, remove this environment variable.

Full documentation about nextJS telemetry is here : https://nextjs.org/telemetry

I lose the repo.json file

Since v2.0, each time the user modifies the repositories (adding, deleting, modifying) the repo.json file is logged. You can find the logs in the config/versions folder.

If you have lost your repo.json file, you can retrieve its contents from the logs to restore it.

I can’t login to BorgWarehouse after installation.

You can login after installation with the admin user and the admin password. You can change the password of this user in the settings.

If you can’t login to BorgWarehouse after installation, it’s probably because you have a bad configuration of NEXTAUTH_URL in your .env.local file. Check this file and make sure that the URL is correct, and in particular don’t forget the http:// or https:// part. Enter an https URL if you have configured BorgWarehouse to use http will not work.

I don’t see the status or storage updates.

Please, check if you have set up your cron before opening an issue.

Contact the creator ?

You can contact me on borgwarehouse @ r4ven.fr