All of a sudden None of the Paperless-NGX services will start

[BrianBonnell]

Just opened a issue case on the Paperless-NGX Github (#11714) not sure if anyone else is seeing this issue today (1/5/2025) but my instance was working up until today, no changes were made to my ProxmoxLXC container.:

When attempting to start any and all services of Paperless-NGX in a baremetal/LXC container in Proxmox. This errors is generated for each service:

root@paperless-ngx:~# systemctl --state=failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● paperless-consumer.service loaded failed failed Paperless consumer
● paperless-scheduler.service loaded failed failed Paperless Celery beat
● paperless-task-queue.service loaded failed failed Paperless Celery Workers
● paperless-webserver.service loaded failed failed Paperless webserver

Jan 05 09:04:25 paperless-ngx systemd[1]: Started paperless-webserver.service - Paperless webserver.
Jan 05 09:04:28 paperless-ngx uv[429]: error: Failed to generate package metadata for zxing-cpp==2.3.0 @ direct+https://github.com/paperless-ngx/builder/releases/download/zxing-2.3.0/zxing_cpp-2.3.0-cp312-cp312-linux_aarch64.whl
Jan 05 09:04:28 paperless-ngx uv[429]: Caused by: Failed to fetch: https://github.com/paperless-ngx/builder/releases/download/zxing-2.3.0/zxing_cpp-2.3.0-cp312-cp312-linux_aarch64.whl
Jan 05 09:04:28 paperless-ngx uv[429]: Caused by: Request failed after 3 retries
Jan 05 09:04:28 paperless-ngx uv[429]: Caused by: error sending request for url (https://release-assets.githubusercontent.com/github-production-release-asset/633903140/dec9c2ff-deea-427d-bc78-050711216680?sp=r&sv=2018-11-09&sr=b&spr=h>
Jan 05 09:04:28 paperless-ngx uv[429]: Caused by: client error (Connect)
Jan 05 09:04:28 paperless-ngx uv[429]: Caused by: received corrupt message of type InvalidContentType
Jan 05 09:04:28 paperless-ngx systemd[1]: paperless-webserver.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Jan 05 09:04:28 paperless-ngx systemd[1]: paperless-webserver.service: Failed with result 'exit-code'.

Changing DNS does not fix the issue and the site (https://release-assets.githubusercontent.com/) is no longer available.

Browser error:
Hmmm… can't reach this page
It looks like release-assets.githubusercontent.com closed the connection.

Attempted these steps to resolve or workaround issue with no success:
This error occurs because the uv package manager is failing to download the pre-built zxing-cpp binary from the Paperless-ngx GitHub repository. This is typically caused by a corrupted local cache or a transient network issue connecting to GitHub's release assets.
To resolve this issue, try the following steps:

Clear the uv Cache
The error InvalidContentType or corrupt message often indicates that uv has cached a partial or broken download.
Run the following command to clear the cache:
bash
uv cache clean
Use code with caution.
If you are running in a CI/Docker environment, you may need to manually remove the cache directory: rm -rf ~/.cache/uv.
2. Update Paperless-ngx
There have been reported bugs regarding SHA256 hash mismatches for zxing-cpp in certain versions of the requirements.txt or uv.lock files.
Ensure you are running the latest version of Paperless-ngx by pulling the latest Docker image or updating your bare-metal installation.
If you are on a bare-metal setup, verify your requirements.txt matches the version released by the Paperless-ngx team.
3. Workaround: Disable Barcode Scanning
If you cannot restore the connection and need the service to start immediately, you can temporarily disable the feature that requires zxing-cpp (barcode scanning):
Set the following environment variable in your configuration:
env
PAPERLESS_CONSUMER_ENABLE_BARCODES=false
Use code with caution.

Check Network Restrictions
If your server is behind a proxy or in a region where GitHub is restricted, uv may fail to fetch release assets.
Verify that your server can reach https://release-assets.githubusercontent.com/.
If you are offline, uv will fail to start by default unless you explicitly set it to offline mode.

Nothing seems to work or provide a workaround for this issue.....for all practical purposes my Paperless-NGX instance is dead. Even restoring the last known good version via PBS end with the services not starting as well. I have checked my own DNS and use public DNS with the same end result. This might be a larger issue than just me so thought I'd post here and get feedback.

[BrianBonnell]

paperless-ngx/paperless-ngx#11716
I think this might be an actual issue....none of the URLS mentioned in the errors are valid URLs, I have attempted to resolve them outside of paperless-ngx instance, and none are appearing to be resolvable or accessible, if the services depend on resolving these URLs they will never start until they become available.