Registry Troubleshooting

Use this guide when install or update fails while downloading ERP images. Your server does not need Docker Hub credentials — failures are usually entitlement, network, or release selection issues.

Image download denied or authentication failed

Check:

• Is your License valid and is update entitlement active?
• Did the short-lived download authorization expire? Re-run the install or update operation.
• Can the server reach https://registry.soviez.com (or your configured delivery URL)?
• Is outbound HTTPS blocked by firewall or proxy?

Fix: Resolve network or entitlement, then retry the operation. Do not add permanent Docker Hub logins to the host.

Digest or release mismatch

Check:

• Did you specify an exact release with --release <release-id>?
• Are you attempting to pull a floating “latest” tag? Production updates require an exact signed release.

Fix: Use the release ID from your Soviez account or --releases output.

Service temporarily unavailable

Symptom: Download fails with gateway or service errors.

Check:

• Is this a new install/update, or is ERP already running?
• A running ERP should not depend on the delivery service — only new downloads are affected.

Fix: Wait and retry. If the outage persists, contact Soviez support with the operation ID and error message.

Offline update path

Offline updates do not use the connected image delivery service. If you intended an offline update, use a signed offline bundle instead:

soviez.sh --update <production-id> --offline-package /path/to/bundle

See OFFLINE_UPDATES.md.

ERP stopped after a delivery outage

This is unexpected. A delivery service outage should affect new downloads only, not a running Production environment.

Check:

soviez.sh --doctor
soviez.sh --operations --failed

Investigate the actual failure separately from registry connectivity.

Related

• PRIVATE_IMAGE_DELIVERY.md
• REGISTRY_GATEWAY.md
• UPDATES.md
• TROUBLESHOOTING.md