Troubleshooting

Git Web Manager

Fix common deployment and build issues.

Use Cases Overview

Static Assets or Cache Stale

If the UI looks stale after an update, open /recovery while authenticated and use Repair Published Assets.

  • /recovery is a maintenance page and can be opened even when the UI is healthy.
  • /rebuild clears Laravel caches and republishes bundled assets.
  • The repair action does not run npm, does not need node_modules, and does not create a Vite manifest.

Git Authentication Failed

Confirm GITHUB_TOKEN is set and the Git binary is reachable. For custom binaries, set GWM_GIT_BINARY.

GitHub SSL Certificate Error

If you see cURL error 60: SSL certificate problem when syncing Dependabot alerts, your system is missing trusted CA certificates.

  • Preferred: install/update your OS CA bundle.
  • Temporary: set GITHUB_SSL_VERIFY=false in .env to bypass SSL verification (not recommended for production).

Git Permission Errors

If you see errors like insufficient permission for adding an object to repository database or could not write index, the web user cannot write to .git. Run PHP-FPM as the same user that owns the repo, or use a dedicated pool per user.

chown -R user:group /home/user/your-app/.git

Self Update Fallback URLs

If the UI is unavailable after a Self Update, you can trigger updates manually using authenticated fallback URLs:

  • /update runs a standard self-update.
  • /rollback reverts to the previous update’s from_hash.
  • /rollback?hash=<commit> reverts to a specific commit.

These endpoints require authentication. If no rollback target exists, use /update instead.

Deploy Stuck

Ensure the queue worker is running and check job logs in the Debug tab.

Container Component Not Found

If you see errors like Unable to find component: [git-manager-enterprise.livewire.infrastructure.containers], the Enterprise package is missing or not autoloaded.

  • Confirm composer install can resolve wallabydesigns/gitmanager-enterprise.
  • Verify your Composer repository source (path repo or private registry).
  • Run php artisan optimize:clear after package install/update.
  • Confirm the Enterprise package includes its packaged static CSS file under style/gitmanager-enterprise.css; installs no longer rely on an ignored dist folder.