Vaultify Wiki ‐ Troubleshooting - Vault-Tek/Vaultify GitHub Wiki

If you encounter issues while using Vaultify, this guide provides solutions to common problems related to installation, self-hosting, encryption, and general usage. If your issue is not listed here, consider checking the GitHub Issues page or the Vaultify community forums for further assistance.

Possible Cause:

• Node.js and npm are not installed or not added to the system path.

Solution:

• Verify Node.js installation:

  node -v
  npm -v

• If not installed, download and install Node.js from nodejs.org.

Possible Cause:

• Insufficient permissions to install dependencies globally or within the Vaultify directory.

Solution:

• Run the command with sudo:

  sudo npm install

• If using Windows, try running PowerShell or Command Prompt as an Administrator.

Possible Cause:

• Another process is already using the configured port.

Solution:

• Identify and kill the process using the port:

  sudo lsof -i :3000
  sudo kill -9 <PID>

• Change the port in .env:

  PORT=4000

Possible Cause:

• MongoDB or SQLite is not running.

Solution:

• Start MongoDB manually:

  sudo systemctl start mongod

• If using SQLite, ensure the database file exists in the correct location.

Possible Cause:

• Corrupted encryption keys or incorrect .env settings.

Solution:

• Verify that your ENCRYPTION_KEY in the .env file matches the one used when the account was created.
• If the key has changed, you will not be able to decrypt previously stored passwords.

Possible Cause:

• Invalid or missing SESSION_SECRET.

Solution:

• Regenerate a secure session key in .env:

  SESSION_SECRET=$(openssl rand -hex 32)

• Restart Vaultify:

  npm restart

Possible Cause:

• Nginx or firewall is blocking access.

Solution:

• Check if Vaultify is running:

  systemctl status vaultify

• Verify Nginx configuration:

  sudo nginx -t
  sudo systemctl restart nginx

• Ensure firewall allows traffic:

  sudo ufw allow 80
  sudo ufw allow 443

Possible Cause:

• Issues with volume bindings or environment variables.

Solution:

• Restart Docker and check logs:

  docker-compose down
  docker-compose up -d
  docker logs vaultify

Possible Cause:

• Caching issues or incorrect configuration files.

Solution:

• Clear the browser cache and reload.
• Restart the Vaultify server:

  npm restart

Possible Cause:

• Missing dependency updates.

Solution:

• Run:

  git pull
  npm install
  npm restart

✅ Run Vaultify in verbose mode for detailed logs:

DEBUG=Vaultify:* npm start

✅ Check the server logs:

tail -f logs/error.log

✅ If all else fails, create a GitHub issue with error logs attached.