Failed to fetch updates #1103

New issue

Closed

opened 2026-02-20 10:07:20 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-20 10:07:20 -05:00

Owner

Originally created by @tifo71 on GitHub (Oct 17, 2024).

Is there an existing issue for this?

I have searched the existing open and closed issues

Current Behavior

dans la partie mise a jour. Il y a le message Failed to fletch updates

et dans la partie event

Expected Behavior

solve this bug

Steps To Reproduce

No response

Environment

- OS: windows 11 24h2
- Prowlarr:1.24.3.4754
- Docker Install: yes
- Using Reverse Proxy: non
- Browser: vivaldi 6.9.3447.54 (Stable channel) (64 bits)

What branch are you running?

Master

Trace Logs?

2024-10-17 23:20:10.8|Trace|Http|Req: 79 [GET] /api/v1/health (from 192.168.1.64 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36)
2024-10-17 23:20:10.8|Trace|Http|Req: 80 [GET] /api/v1/system/status (from 192.168.1.64 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36)
2024-10-17 23:20:10.8|Debug|Prowlarr.Http.Authentication.ApiKeyAuthenticationHandler|AuthenticationScheme: API was successfully authenticated.
2024-10-17 23:20:10.8|Debug|Prowlarr.Http.Authentication.ApiKeyAuthenticationHandler|AuthenticationScheme: API was successfully authenticated.
2024-10-17 23:20:10.8|Trace|Http|Res: 79 [GET] /api/v1/health: 200.OK (3 ms)
2024-10-17 23:20:10.8|Debug|Api|[GET] /api/v1/health: 200.OK (3 ms)
2024-10-17 23:20:10.8|Trace|Http|Res: 80 [GET] /api/v1/system/status: 200.OK (5 ms)
2024-10-17 23:20:10.8|Debug|Api|[GET] /api/v1/system/status: 200.OK (5 ms)
2024-10-17 23:20:12.5|Trace|Http|Req: 81 [GET] /api/v1/log/file (from 192.168.1.64 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36)
2024-10-17 23:20:12.5|Debug|Prowlarr.Http.Authentication.ApiKeyAuthenticationHandler|AuthenticationScheme: API was successfully authenticated.
2024-10-17 23:20:12.5|Trace|Http|Res: 81 [GET] /api/v1/log/file: 200.OK (2 ms)
2024-10-17 23:20:12.5|Debug|Api|[GET] /api/v1/log/file: 200.OK (2 ms)
2024-10-17 23:20:17.4|Trace|Http|Req: 82 [GET] /logfile/prowlarr.trace.txt (from 192.168.1.64 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36)
2024-10-17 23:20:17.4|Debug|Prowlarr.Http.Authentication.BasicAuthenticationHandler|AuthenticationScheme: Basic was successfully authenticated.

Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided.

I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue.

Originally created by @tifo71 on GitHub (Oct 17, 2024). ### Is there an existing issue for this? - [X] I have searched the existing open and closed issues ### Current Behavior dans la partie mise a jour. Il y a le message Failed to fletch updates ![image](https://github.com/user-attachments/assets/f0d935d1-3f5b-47f3-866c-21ca220e269f) et dans la partie event ![image](https://github.com/user-attachments/assets/e520e8b5-5cc9-48bf-968a-219fd2ab6c36) ### Expected Behavior solve this bug ### Steps To Reproduce _No response_ ### Environment ```markdown - OS: windows 11 24h2 - Prowlarr:1.24.3.4754 - Docker Install: yes - Using Reverse Proxy: non - Browser: vivaldi 6.9.3447.54 (Stable channel) (64 bits) ``` ### What branch are you running? Master ### Trace Logs? 2024-10-17 23:20:04.7|Trace|EventAggregator|ConfigFileSavedEvent <~ ReconfigureLogging 2024-10-17 23:20:04.7|Trace|EventAggregator|ConfigSavedEvent ~> TaskManager 2024-10-17 23:20:04.7|Trace|ConfigService|Using default config value for 'proxyenabled' defaultValue:'False' 2024-10-17 23:20:04.7|Trace|ConfigService|Using default config value for 'proxytype' defaultValue:'Http' 2024-10-17 23:20:04.7|Trace|ConfigService|Using default config value for 'proxyhostname' defaultValue:'' 2024-10-17 23:20:04.7|Trace|ConfigService|Using default config value for 'proxyport' defaultValue:'8080' 2024-10-17 23:20:04.7|Trace|ConfigService|Using default config value for 'proxyusername' defaultValue:'' 2024-10-17 23:20:04.7|Trace|ConfigService|Using default config value for 'backupinterval' defaultValue:'7' 2024-10-17 23:20:04.7|Trace|ConfigService|Using default config value for 'proxypassword' defaultValue:'' 2024-10-17 23:20:04.7|Trace|ConfigService|Using default config value for 'proxybypassfilter' defaultValue:'' 2024-10-17 23:20:04.7|Trace|ConfigService|Using default config value for 'proxybypasslocaladdresses' defaultValue:'True' 2024-10-17 23:20:04.7|Trace|ConfigService|Using default config value for 'certificatevalidation' defaultValue:'Enabled' 2024-10-17 23:20:04.7|Trace|ConfigService|Using default config value for 'backupfolder' defaultValue:'Backups' 2024-10-17 23:20:04.7|Trace|ConfigService|Using default config value for 'backupinterval' defaultValue:'7' 2024-10-17 23:20:04.7|Trace|ConfigService|Using default config value for 'backupretention' defaultValue:'28' 2024-10-17 23:20:04.7|Trace|ConfigService|Using default config value for 'applicationurl' defaultValue:'' 2024-10-17 23:20:04.7|Trace|ConfigService|Using default config value for 'historycleanupdays' defaultValue:'30' 2024-10-17 23:20:04.7|Trace|Http|Res: 78 [PUT] /api/v1/config/host: 202.Accepted (19 ms) 2024-10-17 23:20:04.7|Debug|Api|[PUT] /api/v1/config/host: 202.Accepted (19 ms) 2024-10-17 23:20:04.7|Trace|EventAggregator|ConfigSavedEvent <~ TaskManager 2024-10-17 23:20:09.7|Trace|HealthCheckService|Check health -> UpdateCheck 2024-10-17 23:20:09.7|Trace|HttpClient|Req: [GET] https://prowlarr.servarr.com/v1/update/master?version=1.24.3.4754&os=linuxmusl&arch=X64&runtime=netcore&runtimeVer=6.0.32&dbType=SQLite&active=true 2024-10-17 23:20:09.7|Trace|ConfigService|Using default config value for 'proxyenabled' defaultValue:'False' 2024-10-17 23:20:10.0|Trace|HttpClient|Res: HTTP/2.0 [GET] https://prowlarr.servarr.com/v1/update/master?version=1.24.3.4754&os=linuxmusl&arch=X64&runtime=netcore&runtimeVer=6.0.32&dbType=SQLite&active=true: 404.NotFound (19 bytes) 404 page not found (339 ms) 2024-10-17 23:20:10.0|Warn|HttpClient|HTTP Error - Res: HTTP/2.0 [GET] https://prowlarr.servarr.com/v1/update/master?version=1.24.3.4754&os=linuxmusl&arch=X64&runtime=netcore&runtimeVer=6.0.32&dbType=SQLite&active=true: 404.NotFound (19 bytes) 404 page not found 2024-10-17 23:20:10.8|Trace|Http|Req: 79 [GET] /api/v1/health (from 192.168.1.64 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36) 2024-10-17 23:20:10.8|Trace|Http|Req: 80 [GET] /api/v1/system/status (from 192.168.1.64 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36) 2024-10-17 23:20:10.8|Debug|Prowlarr.Http.Authentication.ApiKeyAuthenticationHandler|AuthenticationScheme: API was successfully authenticated. 2024-10-17 23:20:10.8|Debug|Prowlarr.Http.Authentication.ApiKeyAuthenticationHandler|AuthenticationScheme: API was successfully authenticated. 2024-10-17 23:20:10.8|Trace|Http|Res: 79 [GET] /api/v1/health: 200.OK (3 ms) 2024-10-17 23:20:10.8|Debug|Api|[GET] /api/v1/health: 200.OK (3 ms) 2024-10-17 23:20:10.8|Trace|Http|Res: 80 [GET] /api/v1/system/status: 200.OK (5 ms) 2024-10-17 23:20:10.8|Debug|Api|[GET] /api/v1/system/status: 200.OK (5 ms) 2024-10-17 23:20:12.5|Trace|Http|Req: 81 [GET] /api/v1/log/file (from 192.168.1.64 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36) 2024-10-17 23:20:12.5|Debug|Prowlarr.Http.Authentication.ApiKeyAuthenticationHandler|AuthenticationScheme: API was successfully authenticated. 2024-10-17 23:20:12.5|Trace|Http|Res: 81 [GET] /api/v1/log/file: 200.OK (2 ms) 2024-10-17 23:20:12.5|Debug|Api|[GET] /api/v1/log/file: 200.OK (2 ms) 2024-10-17 23:20:17.4|Trace|Http|Req: 82 [GET] /logfile/prowlarr.trace.txt (from 192.168.1.64 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36) 2024-10-17 23:20:17.4|Debug|Prowlarr.Http.Authentication.BasicAuthenticationHandler|AuthenticationScheme: Basic was successfully authenticated. ### Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided. - [X] I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain `trace` - that are relevant and show this issue.

deekerman

2026-02-20 10:07:20 -05:00

closed this issue
added the
Type: External Bug

Area: Metadata API
labels

deekerman commented

2026-02-20 10:07:22 -05:00

Author

Owner

@d0lf99 commented on GitHub (Oct 17, 2024):

Kind of same problem, cannot download prowlarr as http://prowlarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64 seems to 404

@d0lf99 commented on GitHub (Oct 17, 2024): Kind of same problem, cannot download prowlarr as http://prowlarr.servarr.com/v1/update/master/updatefile?os=linux&runtime=netcore&arch=x64 seems to 404

deekerman commented

2026-02-20 10:07:23 -05:00

Author

Owner

@tifo71 commented on GitHub (Oct 17, 2024):

Yes prowlarr work very well but update server is down.

@tifo71 commented on GitHub (Oct 17, 2024): Yes prowlarr work very well but update server is down.

deekerman commented

2026-02-20 10:07:23 -05:00

Author

Owner

@mynameisbogdan commented on GitHub (Oct 18, 2024):