Troubleshooting

Common issues, error codes, and diagnostic steps for resolving problems with DepAegis. If your issue isn't listed here, see the diagnostic steps and support options at the bottom of this page.

Common Issues

Error	Cause	Solution
`401 Unauthorized`	Expired, invalid, or missing authentication token	Verify your token is set correctly in `.npmrc`, `nuget.config`, or `~/.docker/config.json`. Generate a new token if it has expired. Check that the `Authorization: Bearer` header is being sent.
`403 Forbidden`	Insufficient permissions for the requested operation	Confirm your token has the correct scope (`read`, `publish`, or `admin`). Check your organization role — you may need `publisher` or `owner` role to publish.
`404 Not Found`	Wrong registry URL, package name, or version	Double-check the registry URL in your config. Verify the package name and scope. For npm scoped packages, ensure the scope matches your DepAegis organization.
`409 Conflict`	Package version already exists	You cannot publish the same version twice. Bump the version in `package.json`or your `.csproj` file before publishing again.
SSL certificate errors	Corporate proxy, VPN, or TLS inspection intercepting traffic	DepAegis endpoints use certificates from a trusted CA, so standard clients work out of the box. If you see SSL errors, check whether a corporate proxy or VPN is intercepting TLS and add it to your system trust store.
Connection refused / timeouts	Wrong registry URL, local network issue, or a service incident	Double-check the registry URL in your client config, verify your network can reach `app.depaegis.com`, then retry. If the problem persists across networks, `contact support` — incidents are rare but do happen.

Package Manager Errors

npm Errors

Error	Cause	Solution
`npm E401`	Authentication failed	Check your `.npmrc` auth token. Ensure the registry URL matches (including `https://` prefix). Regenerate the token if needed.
`npm E403`	Forbidden — token lacks required scope or policy blocked the request	Verify token has `publish`scope. Check if OPA policy is blocking the package (check the DepAegis dashboard for policy violations). Ensure the version doesn't already exist.

NuGet Errors

Error	Cause	Solution
`NU1301`	Unable to resolve the package source	Verify the DepAegis NuGet source URL in your `nuget.config`. Ensure the server is reachable: `curl https://app.depaegis.com/v3/index.json`.
`NU1302`	Package source authentication failed	Run `dotnet nuget update source depaegis --username <user> --password <token>` to refresh credentials. Verify the token hasn't expired.

Docker Errors

Error	Cause	Solution
`unauthorized: authentication required`	Docker login missing or expired	Run `docker login app.depaegis.com` with your DepAegis username and access token (use the token as the password).

Diagnostic Steps

When something isn't working, follow these steps to narrow down the problem:

1. Check Service Health

# Check the registry health endpoint
curl -f https://app.depaegis.com/api/v1/health

Server-side health, container status, and logs are managed by DepAegis — you don't need (and don't have) access to them. If the health endpoint is unreachable, see Platform & Operations and contact support.

2. Verify Network Connectivity

# Test basic connectivity
curl -v https://app.depaegis.com/api/v1/packages

# Test with auth
curl -H "Authorization: Bearer $DEPAEGIS_TOKEN" \
  https://app.depaegis.com/api/v1/packages?limit=1

3. Check DNS Resolution

# From the client machine
nslookup app.depaegis.com

4. Verify Package Manager Configuration

# npm: show effective config
npm config list
npm config get registry

# NuGet: list sources
dotnet nuget list source

# Docker: check auth
cat ~/.docker/config.json | jq '.auths'

5. Collect Client-Side Details

# npm with verbose logging
npm publish --loglevel verbose

# NuGet with detailed output
dotnet nuget push <package.nupkg> --verbosity detailed

Server-side logs are managed by DepAegis. When opening a support ticket, include the exact timestamp (with timezone) and the request IDs or error output from your client — support can correlate them with server-side logs.

Getting More Detail from Clients

Server-side logging is managed by DepAegis. To get more detail on the client side, increase your package manager's log level:

# npm: run with verbose output
npm <command> --loglevel verbose

# NuGet / dotnet: detailed verbosity
dotnet <command> --verbosity detailed

# Docker: debug mode for a single command
docker --debug <command>

Client debug output may include authentication tokens in headers. Always redact tokens and secrets before sharing logs with support.

Getting Support

If you can't resolve your issue using the steps above, the following resources are available:

Documentation — Browse the full documentation for setup guides, configuration, and API reference.
Support Ticket— Paid plans can open support tickets directly from the DepAegis dashboard, with SLA-backed response times on Business and Enterprise plans.
Email — Write to contact@depaegis.com with your log output (redacted of secrets), the steps to reproduce, and your environment details (OS, package manager version).

When reporting an issue, include the following information to help us diagnose it faster:

Your plan and registry URL (see the dashboard)
Package manager and version (npm --version, dotnet --version, docker --version)
Exact timestamp of the failing request (with timezone)
Full error output (including stack trace if available)
Redacted client debug output (verbose log level)

← Previous

REST API