blockchain-components icon indicating copy to clipboard operation
blockchain-components copied to clipboard
verified publisher icon Shopify

Indexers connection stability issues - time outs

Open dependabot[bot] opened this issue 1 year ago • 39 comments

Bumps the npm_and_yarn group with 13 updates in the / directory:

Package From To
postcss 8.4.23 8.4.31
vite 4.3.9 4.5.3
next 13.2.3 13.5.0
@adobe/css-tools 4.2.0 4.3.3
@solana/web3.js 1.75.0 1.91.7
browserify-sign 4.2.1 4.2.3
ejs 3.1.9 3.1.10
express 4.18.2 4.19.2
follow-redirects 1.15.2 1.15.6
get-func-name 2.0.0 2.0.2
ip 1.1.8 1.1.9
tar 6.1.14 6.2.1
webpack-dev-middleware 5.3.3 5.3.4

Bumps the npm_and_yarn group with 1 update in the /examples/nextjs directory: next.

Updates postcss from 8.4.23 to 8.4.31

Release notes

Sourced from postcss's releases.

8.4.31

  • Fixed \r parsing to fix CVE-2023-44270.

8.4.30

8.4.29

8.4.28

  • Fixed Root.source.end for better source map (by @​romainmenke).
  • Fixed Result.root types when process() has no parser.

8.4.27

  • Fixed Container clone methods types.

8.4.26

  • Fixed clone methods types.

8.4.25

8.4.24

  • Fixed Plugin types.
Changelog

Sourced from postcss's changelog.

8.4.31

  • Fixed \r parsing to fix CVE-2023-44270.

8.4.30

  • Improved source map performance (by Romain Menke).

8.4.29

  • Fixed Node#source.offset (by Ido Rosenthal).
  • Fixed docs (by Christian Oliff).

8.4.28

  • Fixed Root.source.end for better source map (by Romain Menke).
  • Fixed Result.root types when process() has no parser.

8.4.27

  • Fixed Container clone methods types.

8.4.26

  • Fixed clone methods types.

8.4.25

8.4.24

  • Fixed Plugin types.
Commits

Updates vite from 4.3.9 to 4.5.3

Changelog

Sourced from vite's changelog.

4.5.3 (2024-03-24)

4.5.2 (2024-01-19)

4.5.1 (2023-12-04)

4.5.0 (2023-10-18)

4.4.11 (2023-10-05)

  • revert: "fix: use string manipulation instead of regex to inject esbuild helpers (54e1275), closes #14094

4.4.10 (2023-10-03)

... (truncated)

Commits

Updates next from 13.2.3 to 13.5.0

Commits

Updates @adobe/css-tools from 4.2.0 to 4.3.3

Changelog

Sourced from @​adobe/css-tools's changelog.

4.3.3 / 2024-01-24

  • Update export property #271

4.3.2 / 2023-11-28

  • Fix redos vulnerability with specific crafted css string - CVE-2023-48631
  • Fix Problem parsing with :is() and nested :nth-child() #211

4.3.1 / 2023-03-14

  • Fix redos vulnerability with specific crafted css string - CVE-2023-26364

4.3.0 / 2023-03-07

  • Update build tools
  • Update exports path and files
Commits

Updates @solana/web3.js from 1.75.0 to 1.91.7

Release notes

Sourced from @​solana/web3.js's releases.

v1.91.7

1.91.7 (2024-04-19)

Bug Fixes

  • update @solana/spl-token to 0.4.5 in tests (#2529) (da22d0b)

v1.91.6

1.91.6 (2024-04-17)

Bug Fixes

  • revert use of internal fast-stable-stringify in legacy library (#2509) (7d3adbb)

v1.91.5

1.91.5 (2024-04-17)

Bug Fixes

  • use our version of fast-stable-stringify everywhere (#2504) (18d6b56)

v1.91.4

1.91.4 (2024-04-03)

Bug Fixes

  • downshift preflightCommitment to processed when bypassing preflight checks (#2415) (c801637)

v1.91.3

1.91.3 (2024-04-01)

Bug Fixes

v1.91.2

1.91.2 (2024-03-26)

Reverts

v1.91.1

1.91.1 (2024-03-13)

... (truncated)

Commits
  • da22d0b fix: update @solana/spl-token to 0.4.5 in tests (#2529)
  • df3c618 chore: bump semantic-release from 21.0.7 to 23.0.8 (#2525)
  • 5b1c858 chore: bump @​noble/curves from 1.2.0 to 1.4.0 (#2524)
  • b8f006d Delete lots of transactions code! (#2494)
  • efe04f4 Replace uses of SerializedMessageBytesBase64 and TransactionVersion (#2493)
  • 9d82220 Remove now unused exports from Transactions library (#2492)
  • 311c96a Refactor send-transaction to use NewTransaction (#2487)
  • f5cfd89 add TransactionWithXLifetime types (#2486)
  • 1344fa7 Refactor transaction-confirmation to use new transaction lifetimes (#2485)
  • 028bdcc Add glyphs to fix Hash collision with bigint and string (#2512)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by lorisleiva, a new releaser for @​solana/web3.js since your current version.


Updates browserify-sign from 4.2.1 to 4.2.3

Changelog

Sourced from browserify-sign's changelog.

v4.2.3 - 2024-03-05

Commits

v4.2.2 - 2023-10-25

Fixed

Commits

  • Only apps should have lockfiles 09a8995
  • [eslint] switch to eslint 83fe463
  • [meta] add npmignore and auto-changelog 4418183
  • [meta] fix package.json indentation 9ac5a5e
  • [Tests] migrate from travis to github actions d845d85
  • [Fix] sign: throw on unsupported padding scheme 8767739
  • [Fix] properly check the upper bound for DSA signatures 85994cd
  • [Tests] handle openSSL not supporting a scheme f5f17c2
  • [Deps] update bn.js, browserify-rsa, elliptic, parse-asn1, readable-stream, safe-buffer a67d0eb
  • [Dev Deps] update nyc, standard, tape cc5350b
  • [Tests] always run coverage; downgrade nyc 75ce1d5
  • [meta] add safe-publish-latest dcf49ce
  • [Tests] add npm run posttest 75dd8fd
  • [Dev Deps] update tape 3aec038
  • [Tests] skip unsupported schemes 703c83e
  • [Tests] node < 6 lacks array includes 3aa43cf
  • [Dev Deps] fix eslint range 98d4e0d
Commits
  • bf2c3ec v4.2.3
  • 9247adf [patch] widen support to 0.12
  • f427270 [Deps] update `parse-asn1
  • 87f3a35 [Dev Deps] update aud, npmignore, tape
  • fb261ce [Deps] update elliptic
  • 4d0ee49 [patch] drop minimum node support to v1
  • 9e2bf12 [Deps] pin hash-base to ~3.0, due to a breaking change
  • 168e16f [Deps] pin elliptic due to a breaking change
  • 37a4758 [actions] remove redundant finisher
  • 4af5a90 v4.2.2
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by ljharb, a new releaser for browserify-sign since your current version.


Updates ejs from 3.1.9 to 3.1.10

Release notes

Sourced from ejs's releases.

v3.1.10

Version 3.1.10

Commits

Updates express from 4.18.2 to 4.19.2

Release notes

Sourced from express's releases.

4.19.2

What's Changed

Full Changelog: https://github.com/expressjs/express/compare/4.19.1...4.19.2

4.19.1

What's Changed

Full Changelog: https://github.com/expressjs/express/compare/4.19.0...4.19.1

4.19.0

What's Changed

New Contributors

Full Changelog: https://github.com/expressjs/express/compare/4.18.3...4.19.0

4.18.3

Main Changes

Other Changes

... (truncated)

Changelog

Sourced from express's changelog.

4.19.2 / 2024-03-25

  • Improved fix for open redirect allow list bypass

4.19.1 / 2024-03-20

  • Allow passing non-strings to res.location with new encoding handling checks

4.19.0 / 2024-03-20

4.18.3 / 2024-02-29

Commits
  • 04bc627 4.19.2
  • da4d763 Improved fix for open redirect allow list bypass
  • 4f0f6cc 4.19.1
  • a003cfa Allow passing non-strings to res.location with new encoding handling checks f...
  • a1fa90f fixed un-edited version in history.md for 4.19.0
  • 11f2b1d build: fix build due to inconsistent supertest behavior in older versions
  • 084e365 4.19.0
  • 0867302 Prevent open redirect allow list bypass due to encodeurl
  • 567c9c6 Add note on how to update docs for new release (#5541)
  • 69a4cf2 deps: [email protected]
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by wesleytodd, a new releaser for express since your current version.


Updates follow-redirects from 1.15.2 to 1.15.6

Commits
  • 35a517c Release version 1.15.6 of the npm package.
  • c4f847f Drop Proxy-Authorization across hosts.
  • 8526b4a Use GitHub for disclosure.
  • b1677ce Release version 1.15.5 of the npm package.
  • d8914f7 Preserve fragment in responseUrl.
  • 6585820 Release version 1.15.4 of the npm package.
  • 7a6567e Disallow bracketed hostnames.
  • 05629af Prefer native URL instead of deprecated url.parse.
  • 1cba8e8 Prefer native URL instead of legacy url.resolve.
  • 72bc2a4 Simplify _processResponse error handling.
  • Additional commits viewable in compare view

Updates get-func-name from 2.0.0 to 2.0.2

Release notes

Sourced from get-func-name's releases.

v2.0.2

What's Changed

Revert previous changes that shipped this as an ES module.

Full Changelog: https://github.com/chaijs/get-func-name/commits/v2.0.2

v2.0.1

What's Changed

Fix https://github.com/chaijs/get-func-name/security/advisories/GHSA-4q6p-r6v2-jvc5

Full Changelog: https://github.com/chaijs/get-func-name/commits/v2.0.1

Commits
Maintainer changes

This version was pushed to npm by keithamus, a new releaser for get-func-name since your current version.


Updates ip from 1.1.8 to 1.1.9

Commits

Updates tar from 6.1.14 to 6.2.1

Changelog

Sourced from tar's changelog.

Changelog

7.0

  • Rewrite in TypeScript, provide ESM and CommonJS hybrid interface
  • Add tree-shake friendly exports, like import('tar/create') and import('tar/read-entry') to get individual functions or classes.
  • Add chmod option that defaults to false, and deprecate noChmod. That is, reverse the default option regarding explicitly setting file system modes to match tar entry settings.
  • Add processUmask option to avoid having to call process.umask() when chmod: true (or noChmod: false) is set.

6.2

  • Add support for brotli compression
  • Add maxDepth option to prevent extraction into excessively deep folders.

6.1

6.0

  • Drop support for node 6 and 8
  • fix symlinks and hardlinks on windows being packed with \-style path targets

5.0

  • Address unpack race conditions using path reservations
  • Change large-numbers errors from TypeError to Error
  • Add TAR_* error codes
  • Raise TAR_BAD_ARCHIVE warning/error when there are no valid entries found in an archive
  • do not treat ignored entries as an invalid archive
  • drop support for node v4
  • unpack: conditionally use a file mapping to write files on Windows
  • Set more portable 'mode' value in portable mode
  • Set portable gzip option in portable mode

... (truncated)

Commits

Updates webpack-dev-middleware from 5.3.3 to 5.3.4

Release notes

Sourced from webpack-dev-middleware's releases.

v5.3.4

5.3.4 (2024-03-20)

Bug Fixes

  • security: do not allow to read files above (#1779) (189c4ac)
Changelog

Sourced from webpack-dev-middleware's changelog.

5.3.4 (2024-03-20)

Bug Fixes

  • security: do not allow to read files above (#1779) (189c4ac)
Commits

Updates next from 13.2.3 to 13.5.1

Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions You can disable automated security fix PRs for this repo from the Security Alerts page.

dependabot[bot] avatar May 02 '24 09:05 dependabot[bot]

Restarting Prowlarr and clicking on test all indexers fixes this?

mynameisbogdan avatar Jan 20 '24 12:01 mynameisbogdan

I even restarted host PC couple times but no

dukobpa3 avatar Jan 20 '24 12:01 dukobpa3

So if you "restart" Prowlarr and the issue is still there, then it's not what I was expecting to be.

Anything special about your setup? VPN, proxies?

mynameisbogdan avatar Jan 20 '24 12:01 mynameisbogdan

Strange but now restarting service helped. Now all indexer available again.

I've restarted only service, not whole PC

dukobpa3 avatar Jan 20 '24 12:01 dukobpa3

Or is this similar to the oddness of what you're seeing @mynameisbogdan on your setup

bakerboy448 avatar Jan 20 '24 12:01 bakerboy448

But anyway something not good

Here is log started from exit:

2024-01-20 14:55:37.8|Info|Bootstrap|Starting Prowlarr - C:\ProgramData\Prowlarr\bin\Prowlarr.Console.exe - Version 1.12.2.4211
2024-01-20 14:55:39.7|Info|MigrationController|*** Migrating data source=C:\ProgramData\Prowlarr\prowlarr.db;cache size=-20000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3;busytimeout=100 ***
2024-01-20 14:55:40.2|Warn|DiskProvider|Couldn't set permission for C:\ProgramData\Prowlarr. account:WorldSid rights:Modify accessControlType:Allow

[v1.12.2.4211] System.UnauthorizedAccessException: Attempted to perform an unauthorized operation.
   at System.Security.AccessControl.Win32.SetSecurityInfo(ResourceType type, String name, SafeHandle handle, SecurityInfos securityInformation, SecurityIdentifier owner, SecurityIdentifier group, GenericAcl sacl, GenericAcl dacl)
   at System.Security.AccessControl.NativeObjectSecurity.Persist(String name, SafeHandle handle, AccessControlSections includeSections, Object exceptionContext)
   at System.Security.AccessControl.NativeObjectSecurity.Persist(String name, AccessControlSections includeSections, Object exceptionContext)
   at System.Security.AccessControl.NativeObjectSecurity.Persist(String name, AccessControlSections includeSections)
   at System.Security.AccessControl.FileSystemSecurity.Persist(String fullPath)
   at System.IO.FileSystemAclExtensions.SetAccessControl(DirectoryInfo directoryInfo, DirectorySecurity directorySecurity)
   at NzbDrone.Windows.Disk.DiskProvider.SetEveryonePermissions(String filename) in ./Prowlarr.Windows/Disk/DiskProvider.cs:line 99


2024-01-20 14:55:40.3|Warn|AppFolderFactory|Coudn't set app folder permission

[v1.12.2.4211] System.UnauthorizedAccessException: Attempted to perform an unauthorized operation.
   at System.Security.AccessControl.Win32.SetSecurityInfo(ResourceType type, String name, SafeHandle handle, SecurityInfos securityInformation, SecurityIdentifier owner, SecurityIdentifier group, GenericAcl sacl, GenericAcl dacl)
   at System.Security.AccessControl.NativeObjectSecurity.Persist(String name, SafeHandle handle, AccessControlSections includeSections, Object exceptionContext)
   at System.Security.AccessControl.NativeObjectSecurity.Persist(String name, AccessControlSections includeSections, Object exceptionContext)
   at System.Security.AccessControl.NativeObjectSecurity.Persist(String name, AccessControlSections includeSections)
   at System.Security.AccessControl.FileSystemSecurity.Persist(String fullPath)
   at System.IO.FileSystemAclExtensions.SetAccessControl(DirectoryInfo directoryInfo, DirectorySecurity directorySecurity)
   at NzbDrone.Windows.Disk.DiskProvider.SetEveryonePermissions(String filename) in ./Prowlarr.Windows/Disk/DiskProvider.cs:line 99
   at NzbDrone.Common.EnvironmentInfo.AppFolderFactory.SetPermissions() in ./Prowlarr.Common/EnvironmentInfo/AppFolderFactory.cs:line 66


2024-01-20 14:55:40.3|Info|MigrationController|*** Migrating data source=C:\ProgramData\Prowlarr\logs.db;cache size=-20000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3;busytimeout=100 ***
2024-01-20 14:55:40.7|Info|Microsoft.Hosting.Lifetime|Now listening on: http://[::]:9696
2024-01-20 14:55:40.9|Info|CommandExecutor|Starting 3 threads for tasks.
2024-01-20 14:55:42.3|Info|Microsoft.Hosting.Lifetime|Application started. Hosting environment: Production; Content root path: C:\ProgramData\Prowlarr\bin\
2024-01-20 14:55:45.6|Info|Prowlarr.Http.Authentication.BasicAuthenticationHandler|Basic was not authenticated. Failure message: Authorization header missing.
2024-01-20 14:55:45.9|Info|Prowlarr.Http.Authentication.BasicAuthenticationHandler|Basic was not authenticated. Failure message: Authorization header missing.
2024-01-20 14:59:16.8|Info|Prowlarr.Http.Authentication.BasicAuthenticationHandler|Basic was not authenticated. Failure message: Authorization header missing.
2024-01-20 14:59:28.3|Info|Prowlarr.Http.Authentication.BasicAuthenticationHandler|Basic was not authenticated. Failure message: Authorization header missing.```

dukobpa3 avatar Jan 20 '24 13:01 dukobpa3

Or is this similar to the oddness of what you're seeing on your setup

Yes, sounds very similar to my issue.

[v1.12.2.4211] System.UnauthorizedAccessException: Attempted to perform an unauthorized operation.

That's not related, and it's a support thing so you can hop on discord for that.

mynameisbogdan avatar Jan 20 '24 13:01 mynameisbogdan

Anything special about your setup? VPN, proxies?

I think no I have Radarr/Sonarr/Prowlarr/Plex/qBittorrent/Transmission installed on one win10 server (Transmission there temporary because I've just migrated to qBit and still use Transmission until it complete couple dowloads)

I also have Jacket installed on another server.

Nothing special like proxies or vpn or even domain names

dukobpa3 avatar Jan 20 '24 13:01 dukobpa3

So if you "restart" Prowlarr and the issue is still there, then it's not what I was expecting to be.

Anything special about your setup? VPN, proxies?

I have the same issue. Restart didn't help

Unable to connect to indexer, check the log above the ValidationFailure for more details. HTTP request failed: [403:Forbidden] [GET] at [https://mircrew-releases.org/ucp.php?mode=login]

2024-01-29 13:03:43.6|Warn|ProwlarrErrorPipeline|Invalid request Validation failed: -- : Unable to connect to indexer, indexer's server is unavailable. Try again later. HTTP request failed: [504:GatewayTimeout] [GET] at [https://ilcorsaronero.link/browse/0] 2024-01-29 13:04:45.0|Info|Microsoft.Hosting.Lifetime|Application is shutting down... 2024-01-29 13:04:45.1|Info|ConsoleApp|Exiting main. 2024-01-29 13:04:50.7|Info|Bootstrap|Starting Prowlarr - /app/prowlarr/bin/Prowlarr - Version 1.13.2.4245 2024-01-29 13:04:50.9|Info|AppFolderInfo|Data directory is being overridden to [/config] 2024-01-29 13:04:50.9|Info|AppFolderInfo|Data directory is being overridden to [/config] 2024-01-29 13:04:51.4|Info|AppFolderInfo|Data directory is being overridden to [/config] 2024-01-29 13:04:51.6|Info|MigrationController|*** Migrating data source=/config/prowlarr.db;cache size=-20000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3;busytimeout=100 *** 2024-01-29 13:04:52.0|Info|MigrationController|*** Migrating data source=/config/logs.db;cache size=-20000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3;busytimeout=100 *** 2024-01-29 13:04:52.4|Info|Microsoft.Hosting.Lifetime|Now listening on: http://[::]:9696 2024-01-29 13:04:52.6|Info|CommandExecutor|Starting 3 threads for tasks. 2024-01-29 13:04:53.3|Info|Microsoft.Hosting.Lifetime|Application started. Press Ctrl+C to shut down. 2024-01-29 13:04:53.3|Info|Microsoft.Hosting.Lifetime|Hosting environment: Production 2024-01-29 13:04:53.3|Info|Microsoft.Hosting.Lifetime|Content root path: /app/prowlarr/bin 2024-01-29 13:06:28.3|Info|ReleaseSearchService|Searching indexer(s): [kickasstorrents.ws] for Term: [] for Season / Episode:[], Offset: 0, Limit: 100, Categories: [5000] 2024-01-29 13:06:28.3|Info|ReleaseSearchService|Searching indexer(s): [TorrentGalaxy] for Term: [] for Season / Episode:[], Offset: 0, Limit: 100, Categories: [5000, 5070, 5040, 5030, 5045, 5050] 2024-01-29 13:06:28.3|Info|ReleaseSearchService|Searching indexer(s): [BitSearch] for Term: [] for Season / Episode:[], Offset: 0, Limit: 100, Categories: [5000] 2024-01-29 13:06:28.3|Info|ReleaseSearchService|Searching indexer(s): [LimeTorrents] for Term: [] for Season / Episode:[], Offset: 0, Limit: 100, Categories: [5000, 5070] 2024-01-29 13:06:28.3|Info|ReleaseSearchService|Searching indexer(s): [ExtraTorrent.st] for Term: [] for Season / Episode:[], Offset: 0, Limit: 100, Categories: [5000, 5070] 2024-01-29 13:06:28.3|Info|ReleaseSearchService|Searching indexer(s): [The Pirate Bay] for Term: [] for Season / Episode:[], Offset: 0, Limit: 100, Categories: [5000, 5050, 5040, 5045] 2024-01-29 13:06:28.3|Info|ReleaseSearchService|Searching indexer(s): [showRSS] for Term: [] for Season / Episode:[], Offset: 0, Limit: 100, Categories: [5000, 5030, 5040] 2024-01-29 13:06:28.3|Info|ReleaseSearchService|Searching indexer(s): [Torlock] for Term: [] for Season / Episode:[], Offset: 0, Limit: 100, Categories: [5000, 5070] 2024-01-29 13:06:28.3|Info|ReleaseSearchService|Searching indexer(s): [Solid Torrents] for Term: [] for Season / Episode:[], Offset: 0, Limit: 100, Categories: [5000] 2024-01-29 13:06:28.3|Info|ReleaseSearchService|Searching indexer(s): [LimeTorrents clone] for Term: [] for Season / Episode:[], Offset: 0, Limit: 100, Categories: [5000, 5070] 2024-01-29 13:06:28.3|Info|ReleaseSearchService|Searching indexer(s): [EZTV] for Term: [] for Season / Episode:[], Offset: 0, Limit: 100, Categories: [5000] 2024-01-29 13:06:33.4|Warn|Cardigann|HTTP Error - Res: HTTP/2.0 [GET] https://ilcorsaronero.link/browse/0: 504.GatewayTimeout (15 bytes) error code: 504 2024-01-29 13:06:33.4|Warn|Cardigann|Unable to connect to indexer

[v1.13.2.4245] NzbDrone.Common.Http.HttpException: HTTP request failed: [504:GatewayTimeout] [GET] at [https://ilcorsaronero.link/browse/0] at NzbDrone.Core.Indexers.HttpIndexerBase1.FetchIndexerResponse(IndexerRequest request) in ./Prowlarr.Core/Indexers/HttpIndexerBase.cs:line 608 at NzbDrone.Core.Indexers.HttpIndexerBase1.FetchPage(IndexerRequest request, IParseIndexerResponse parser) in ./Prowlarr.Core/Indexers/HttpIndexerBase.cs:line 491 at NzbDrone.Core.Indexers.HttpIndexerBase`1.TestConnection() in ./Prowlarr.Core/Indexers/HttpIndexerBase.cs:line 671 error code: 504

2024-01-29 13:06:33.5|Warn|ProwlarrErrorPipeline|Invalid request Validation failed: -- : Unable to connect to indexer, indexer's server is unavailable. Try again later. HTTP request failed: [504:GatewayTimeout] [GET] at [https://ilcorsaronero.link/browse/0] 2024-01-29 13:07:40.6|Warn|IndexerHttpClient|HTTP Error - Res: HTTP/2.0 [GET] https://mircrew-releases.org/ucp.php?mode=login: 403.Forbidden (162 bytes)

403 Forbidden

403 Forbidden

nginx

2024-01-29 13:07:40.6|Warn|Cardigann|Unable to connect to indexer

[v1.13.2.4245] NzbDrone.Common.Http.HttpException: HTTP request failed: [403:Forbidden] [GET] at [https://mircrew-releases.org/ucp.php?mode=login] at NzbDrone.Common.Http.HttpClient.ExecuteAsync(HttpRequest request) in ./Prowlarr.Common/Http/HttpClient.cs:line 128 at NzbDrone.Core.Indexers.IndexerHttpClient.ExecuteProxiedAsync(HttpRequest request, ProviderDefinition definition) in ./Prowlarr.Core/Indexers/IndexerHttpClient.cs:line 41 at NzbDrone.Core.Indexers.Definitions.Cardigann.CardigannRequestGenerator.GetConfigurationForSetup(Boolean automaticLogin) in ./Prowlarr.Core/Indexers/Definitions/Cardigann/CardigannRequestGenerator.cs:line 659 at NzbDrone.Core.Indexers.Definitions.Cardigann.CardigannRequestGenerator.DoLogin() in ./Prowlarr.Core/Indexers/Definitions/Cardigann/CardigannRequestGenerator.cs:line 266 at NzbDrone.Core.Indexers.Definitions.Cardigann.Cardigann.DoLogin() in ./Prowlarr.Core/Indexers/Definitions/Cardigann/Cardigann.cs:line 191 at NzbDrone.Core.Indexers.HttpIndexerBase1.FetchIndexerResponse(IndexerRequest request) in ./Prowlarr.Core/Indexers/HttpIndexerBase.cs:line 580 at NzbDrone.Core.Indexers.HttpIndexerBase1.FetchPage(IndexerRequest request, IParseIndexerResponse parser) in ./Prowlarr.Core/Indexers/HttpIndexerBase.cs:line 491 at NzbDrone.Core.Indexers.HttpIndexerBase`1.TestConnection() in ./Prowlarr.Core/Indexers/HttpIndexerBase.cs:line 671

403 Forbidden

403 Forbidden

nginx

2024-01-29 13:07:40.7|Warn|ProwlarrErrorPipeline|Invalid request Validation failed: -- : Unable to connect to indexer, check the log above the ValidationFailure for more details. HTTP request failed: [403:Forbidden] [GET] at [https://mircrew-releases.org/ucp.php?mode=login]

pbarone avatar Jan 29 '24 18:01 pbarone

@pbarone your issue is not related this one, so you're looking for https://github.com/Prowlarr/Indexers/issues/401

mynameisbogdan avatar Jan 29 '24 19:01 mynameisbogdan

My issue was fixed by switching from ipvlan to macvlan, but you said you don't use docker.

Still unknown on why it happens on bare installations on Windows.

mynameisbogdan avatar Feb 17 '24 14:02 mynameisbogdan

wasn't reproduced for me for a long time also

dukobpa3 avatar Feb 22 '24 01:02 dukobpa3

So if you "restart" Prowlarr and the issue is still there, then it's not what I was expecting to be.

Anything special about your setup? VPN, proxies?

I'm facing this issue now as well. But restarting the app then manually testing it, solves it immediately. @mynameisbogdan what was the issue you were thinking of?

Ahim13 avatar Mar 17 '24 21:03 Ahim13

Something with DNS and .NET's networking stack.

mynameisbogdan avatar Mar 17 '24 21:03 mynameisbogdan

I have been having this issue too.

Am on unraid using hotio template and its happening with or without vpn (both expressvpn and proton) and with or without prixocy and have reinstalled prowlarr in the last 24 hours. They just intermittently drop out and reconnect. Have also moved my vpn from proton DNS to cloudflare/google

trace: https://logs.notifiarr.com/?e67fce7dc79cdb8b#BFuB59HgSAe3CAVyZ1Gnn6xawz3iHkgHSguHe72pdte7

Sebbyyy avatar Mar 20 '24 02:03 Sebbyyy

@Sebbyyy your issue is not related to this bug report, and looking at the logs yours seems like a misconfiguration. you can use discord to ask for support.

mynameisbogdan avatar Mar 25 '24 13:03 mynameisbogdan

I would ask those with the http request timeout issue to test disabling IPv6 by using export DOTNET_SYSTEM_NET_DISABLEIPV6=1.

mynameisbogdan avatar Mar 25 '24 13:03 mynameisbogdan

I've added DOTNET_SYSTEM_NET_DISABLEIPV6=1 to my env variables, but I'm still getting frequent indexer health issues that don't go away until I restart the Prowlarr docker container. Checking the sites in a browser, they seem fine. Re-testing the indexer in Prowlarr doesn't work until I restart the container. On version 1.16.2.4435.

Message:

Unable to connect to indexer.: Http request timed out

Exception:

System.Net.WebException: Http request timed out
   at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponseAsync(HttpRequest request, CookieContainer cookies) in ./Prowlarr.Common/Http/Dispatchers/ManagedHttpDispatcher.cs:line 170
   at NzbDrone.Common.Http.HttpClient.ExecuteRequestAsync(HttpRequest request, CookieContainer cookieContainer) in ./Prowlarr.Common/Http/HttpClient.cs:line 171
   at NzbDrone.Common.Http.HttpClient.ExecuteAsync(HttpRequest request) in ./Prowlarr.Common/Http/HttpClient.cs:line 70
   at NzbDrone.Core.Indexers.IndexerHttpClient.ExecuteProxiedAsync(HttpRequest request, ProviderDefinition definition) in ./Prowlarr.Core/Indexers/IndexerHttpClient.cs:line 44
   at NzbDrone.Core.Indexers.HttpIndexerBase`1.<>c.<<FetchIndexerResponse>b__56_0>d.MoveNext() in ./Prowlarr.Core/Indexers/HttpIndexerBase.cs:line 628
--- End of stack trace from previous location ---
   at Polly.ResiliencePipeline.<>c__9`2.<<ExecuteAsync>b__9_0>d.MoveNext()
--- End of stack trace from previous location ---
   at Polly.Outcome`1.GetResultOrRethrow()
   at Polly.ResiliencePipeline.ExecuteAsync[TResult,TState](Func`3 callback, TState state, CancellationToken cancellationToken)
   at NzbDrone.Core.Indexers.HttpIndexerBase`1.FetchIndexerResponse(IndexerRequest request) in ./Prowlarr.Core/Indexers/HttpIndexerBase.cs:line 627
   at NzbDrone.Core.Indexers.HttpIndexerBase`1.FetchPage(IndexerRequest request, IParseIndexerResponse parser) in ./Prowlarr.Core/Indexers/HttpIndexerBase.cs:line 568
   at NzbDrone.Core.Indexers.HttpIndexerBase`1.TestConnection() in ./Prowlarr.Core/Indexers/HttpIndexerBase.cs:line 813

Docker Compose:

version: "3.0"
services:
prowlarr:
 image: ghcr.io/linuxserver/prowlarr:version-1.16.2.4435
 container_name: prowlarr
 networks:
   - arrs
 environment:
   - PUID=1337
   - PGID=666
   - TZ=America/Los_Angeles 
   - DOTNET_SYSTEM_NET_DISABLEIPV6=1
 volumes:
   - /mypath:/config
 ports:
   - 127.0.0.1:9929:9696
 restart: unless-stopped

networks:
arrs:
 external: true

Inspect Docker network "arrs":

$ docker inspect arrs
[
    {
        "Name": "arrs",
        "Id": "c1a6a06b2e7195ece12684c0e222b82c3207450e6d2f760376f83a3535625db2",
        "Created": "2023-11-07T01:53:19.857195779-08:00",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "172.16.2.0/24",
                    "IPRange": "172.16.2.0/24",
                    "Gateway": "172.16.2.1"
                }
            ]
        },
        "Internal": false,
        "Attachable": true,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {
            "17ce4e59468a44b79586e1c0599c6e372132e7594d289dd4105bf5d65ed21131": {
                "Name": "prowlarr",
                "EndpointID": "9b7703fb4a4253efac59f07078b793b3876453700acff71c9cb6ab8f41c23098",
                "MacAddress": "02:42:ac:10:02:07",
                "IPv4Address": "172.16.2.7/24",
                "IPv6Address": ""
            }  
        },
        "Options": {},
        "Labels": {}
    }
]

nopoz avatar Apr 25 '24 21:04 nopoz

Not sure if the process listening on IPV6 "any" (ie :::) is expected? The docker network is IPV4 and has IPV6 disabled. If I interact with the container and look for the Prowlarr listening port, it's listening on IPV6. Not sure if that's normal and/or desired. Doing a translation internally from IPV6 to IPV4 seems redundant and a possible area where networking could get mangled.

# docker exec -t -i prowlarr /bin/bash
root@17ce4e59468a:/# netstat -nap | grep LISTEN | grep 9696
tcp        0      0 :::9696                 :::*                    LISTEN      -

nopoz avatar Apr 25 '24 21:04 nopoz

I tried a bunch of stuff but found that the only way to get prowlarr to listen on ipv4 only is to stop the container and edit the config file to bind to 0.0.0.0 instead of *:

config.xml:

  <BindAddress>0.0.0.0</BindAddress>

Note that this can only be done by manually editing the config file. If you try to change it in the UI, it will throw an error telling you to use * instead.

I'm going see how this goes and if the timeouts come back.

netstat output after the config change:

root@7ee3286f7154:/# netstat -nap | grep LISTEN | grep 9696
tcp        0      0 0.0.0.0:9696            0.0.0.0:*               LISTEN      -

nopoz avatar Apr 25 '24 23:04 nopoz

I am also having this issue with XSpeeds. It appears the latest update has altered something with IPv6 as this had not been happening prior to this update. The difference in my scenario from what i have read here is that if i get an email notification that the tracker is down, if i go into prowlarr and test it comes back immediately. I am getting the same type of timeout errors though:

2024-05-01 01:56:18.0|Warn|Cardigann|Unable to connect to indexer, please check your DNS settings and ensure IPv6 is working or disabled. https://apibay.org/precompiled/data_top100_recent.json

[v1.16.2.4435] System.Net.Http.HttpRequestException: An error occurred while sending the request.
 ---> System.IO.IOException: The request was aborted.
 ---> System.IO.IOException: The response ended prematurely while waiting for the next frame from the server.
   at System.Net.Http.Http2Connection.<ReadFrameAsync>g__ThrowMissingFrame|58_1()
   at System.Net.Http.Http2Connection.ReadFrameAsync(Boolean initialFrame)
   at System.Net.Http.Http2Connection.ProcessIncomingFramesAsync()
   --- End of inner exception stack trace ---
   at System.Net.Http.Http2Connection.ThrowRequestAborted(Exception innerException)
   at System.Net.Http.Http2Connection.Http2Stream.CheckResponseBodyState()
   at System.Net.Http.Http2Connection.Http2Stream.TryEnsureHeaders()
   at System.Net.Http.Http2Connection.Http2Stream.ReadResponseHeadersAsync(CancellationToken cancellationToken)
   at System.Net.Http.Http2Connection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at System.Net.Http.Http2Connection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
   at System.Net.Http.AuthenticationHelper.SendWithAuthAsync(HttpRequestMessage request, Uri authUri, Boolean async, ICredentials credentials, Boolean preAuthenticate, Boolean isProxyAuth, Boolean doRequestAuth, HttpConnectionPool pool, CancellationToken cancellationToken)
   at System.Net.Http.DiagnosticsHandler.SendAsyncCore(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.DecompressionHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
   at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponseAsync(HttpRequest request, CookieContainer cookies) in ./Prowlarr.Common/Http/Dispatchers/ManagedHttpDispatcher.cs:line 120
   at NzbDrone.Common.Http.HttpClient.ExecuteRequestAsync(HttpRequest request, CookieContainer cookieContainer) in ./Prowlarr.Common/Http/HttpClient.cs:line 171
   at NzbDrone.Common.Http.HttpClient.ExecuteAsync(HttpRequest request) in ./Prowlarr.Common/Http/HttpClient.cs:line 70
   at NzbDrone.Core.Indexers.IndexerHttpClient.ExecuteProxiedAsync(HttpRequest request, ProviderDefinition definition) in ./Prowlarr.Core/Indexers/IndexerHttpClient.cs:line 44
   at NzbDrone.Core.Indexers.HttpIndexerBase`1.<>c.<<FetchIndexerResponse>b__56_0>d.MoveNext() in ./Prowlarr.Core/Indexers/HttpIndexerBase.cs:line 628
--- End of stack trace from previous location ---
   at Polly.ResiliencePipeline.<>c__9`2.<<ExecuteAsync>b__9_0>d.MoveNext()
--- End of stack trace from previous location ---
   at Polly.Outcome`1.GetResultOrRethrow()
   at Polly.ResiliencePipeline.ExecuteAsync[TResult,TState](Func`3 callback, TState state, CancellationToken cancellationToken)
   at NzbDrone.Core.Indexers.HttpIndexerBase`1.FetchIndexerResponse(IndexerRequest request) in ./Prowlarr.Core/Indexers/HttpIndexerBase.cs:line 627
   at NzbDrone.Core.Indexers.HttpIndexerBase`1.FetchPage(IndexerRequest request, IParseIndexerResponse parser) in ./Prowlarr.Core/Indexers/HttpIndexerBase.cs:line 568
   at NzbDrone.Core.Indexers.HttpIndexerBase`1.FetchReleases(Func`2 pageableRequestChainSelector, SearchCriteriaBase searchCriteria, Boolean isRecent) in ./Prowlarr.Core/Indexers/HttpIndexerBase.cs:line 386


2024-05-01 01:56:18.0|Warn|XSpeeds|Unable to connect to indexer, please check your DNS settings and ensure IPv6 is working or disabled. https://www.xspeeds.eu/browse.php?category=0&include_dead_torrents=yes&sort=added&order=desc

[v1.16.2.4435] System.Net.Http.HttpRequestException: An error occurred while sending the request.
 ---> System.IO.IOException: The request was aborted.
 ---> System.IO.IOException: The response ended prematurely while waiting for the next frame from the server.
   at System.Net.Http.Http2Connection.<ReadFrameAsync>g__ThrowMissingFrame|58_1()
   at System.Net.Http.Http2Connection.ReadFrameAsync(Boolean initialFrame)
   at System.Net.Http.Http2Connection.ProcessIncomingFramesAsync()
   --- End of inner exception stack trace ---
   at System.Net.Http.Http2Connection.ThrowRequestAborted(Exception innerException)
   at System.Net.Http.Http2Connection.Http2Stream.CheckResponseBodyState()
   at System.Net.Http.Http2Connection.Http2Stream.TryEnsureHeaders()
   at System.Net.Http.Http2Connection.Http2Stream.ReadResponseHeadersAsync(CancellationToken cancellationToken)
   at System.Net.Http.Http2Connection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at System.Net.Http.Http2Connection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
   at System.Net.Http.AuthenticationHelper.SendWithAuthAsync(HttpRequestMessage request, Uri authUri, Boolean async, ICredentials credentials, Boolean preAuthenticate, Boolean isProxyAuth, Boolean doRequestAuth, HttpConnectionPool pool, CancellationToken cancellationToken)
   at System.Net.Http.DiagnosticsHandler.SendAsyncCore(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.DecompressionHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
   at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponseAsync(HttpRequest request, CookieContainer cookies) in ./Prowlarr.Common/Http/Dispatchers/ManagedHttpDispatcher.cs:line 120
   at NzbDrone.Common.Http.HttpClient.ExecuteRequestAsync(HttpRequest request, CookieContainer cookieContainer) in ./Prowlarr.Common/Http/HttpClient.cs:line 171
   at NzbDrone.Common.Http.HttpClient.ExecuteAsync(HttpRequest request) in ./Prowlarr.Common/Http/HttpClient.cs:line 70
   at NzbDrone.Core.Indexers.IndexerHttpClient.ExecuteProxiedAsync(HttpRequest request, ProviderDefinition definition) in ./Prowlarr.Core/Indexers/IndexerHttpClient.cs:line 44
   at NzbDrone.Core.Indexers.HttpIndexerBase`1.<>c.<<FetchIndexerResponse>b__56_0>d.MoveNext() in ./Prowlarr.Core/Indexers/HttpIndexerBase.cs:line 628
--- End of stack trace from previous location ---
   at Polly.ResiliencePipeline.<>c__9`2.<<ExecuteAsync>b__9_0>d.MoveNext()
--- End of stack trace from previous location ---
   at Polly.Outcome`1.GetResultOrRethrow()
   at Polly.ResiliencePipeline.ExecuteAsync[TResult,TState](Func`3 callback, TState state, CancellationToken cancellationToken)
   at NzbDrone.Core.Indexers.HttpIndexerBase`1.FetchIndexerResponse(IndexerRequest request) in ./Prowlarr.Core/Indexers/HttpIndexerBase.cs:line 627
   at NzbDrone.Core.Indexers.HttpIndexerBase`1.FetchPage(IndexerRequest request, IParseIndexerResponse parser) in ./Prowlarr.Core/Indexers/HttpIndexerBase.cs:line 568
   at NzbDrone.Core.Indexers.HttpIndexerBase`1.FetchReleases(Func`2 pageableRequestChainSelector, SearchCriteriaBase searchCriteria, Boolean isRecent) in ./Prowlarr.Core/Indexers/HttpIndexerBase.cs:line 386

Bingmano avatar May 13 '24 01:05 Bingmano

Firstly try to update to latest, and then report back with new logs. I suspect it's something else in your case because TBP is also down for you with the same error.

System.IO.IOException: The response ended prematurely means the server to which you're making an HTTP request closed the connection without having sent back a complete response.

IPv6 related commit would be a25e79031f263764c2402370588b4f16a5b64109 from Mar 3 first time seen in build v1.14.2.4318. Another is 14ae062db28141954a00a058c72a0be51ae6cf24 which fixes an issue on aarch64.

mynameisbogdan avatar May 13 '24 01:05 mynameisbogdan

Firstly try to update to latest, and then report back with new logs. I suspect it's something else in your case because TBP is also down for you with the same error.

System.IO.IOException: The response ended prematurely means the server to which you're making an HTTP request closed the connection without having sent back a complete response.

IPv6 related commit would be a25e790 from Mar 3 first time seen in build v1.14.2.4318. Another is 14ae062 which fixes an issue on aarch64.

thanks, didn't realize i was behind (running docker, linuxserver.io has not updated past 1.16). I updated to the new latest and will see what happens.

Bingmano avatar May 13 '24 02:05 Bingmano

You should try again in 10-20 mins to update because some cache on our side was cleared and lsio is building the latest release.

mynameisbogdan avatar May 13 '24 02:05 mynameisbogdan

ok so after doing a new pull this morning, i received the below just now. As soon as i got the alert via email, i then clicked test all and it went back to healthy.

2024-05-13 12:35:42.7|Warn|XSpeeds|Unable to connect to indexer, please check your DNS settings and ensure IPv6 is working or disabled. https://www.xspeeds.eu/browse.php?category=0&include_dead_torrents=yes&sort=added&order=desc

[v1.17.2.4511] System.Net.Http.HttpRequestException: An error occurred while sending the request.
 ---> System.IO.IOException: The request was aborted.
 ---> System.IO.IOException: The response ended prematurely while waiting for the next frame from the server.
   at System.Net.Http.Http2Connection.<ReadFrameAsync>g__ThrowMissingFrame|58_1()
   at System.Net.Http.Http2Connection.ReadFrameAsync(Boolean initialFrame)
   at System.Net.Http.Http2Connection.ProcessIncomingFramesAsync()
   --- End of inner exception stack trace ---
   at System.Net.Http.Http2Connection.ThrowRequestAborted(Exception innerException)
   at System.Net.Http.Http2Connection.Http2Stream.CheckResponseBodyState()
   at System.Net.Http.Http2Connection.Http2Stream.TryEnsureHeaders()
   at System.Net.Http.Http2Connection.Http2Stream.ReadResponseHeadersAsync(CancellationToken cancellationToken)
   at System.Net.Http.Http2Connection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at System.Net.Http.Http2Connection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
   at System.Net.Http.AuthenticationHelper.SendWithAuthAsync(HttpRequestMessage request, Uri authUri, Boolean async, ICredentials credentials, Boolean preAuthenticate, Boolean isProxyAuth, Boolean doRequestAuth, HttpConnectionPool pool, CancellationToken cancellationToken)
   at System.Net.Http.DiagnosticsHandler.SendAsyncCore(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.DecompressionHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
   at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponseAsync(HttpRequest request, CookieContainer cookies) in ./Prowlarr.Common/Http/Dispatchers/ManagedHttpDispatcher.cs:line 120
   at NzbDrone.Common.Http.HttpClient.ExecuteRequestAsync(HttpRequest request, CookieContainer cookieContainer) in ./Prowlarr.Common/Http/HttpClient.cs:line 171
   at NzbDrone.Common.Http.HttpClient.ExecuteAsync(HttpRequest request) in ./Prowlarr.Common/Http/HttpClient.cs:line 70
   at NzbDrone.Core.Indexers.IndexerHttpClient.ExecuteProxiedAsync(HttpRequest request, ProviderDefinition definition) in ./Prowlarr.Core/Indexers/IndexerHttpClient.cs:line 44
   at NzbDrone.Core.Indexers.HttpIndexerBase`1.ExecuteAuth(HttpRequest request) in ./Prowlarr.Core/Indexers/HttpIndexerBase.cs:line 727
   at NzbDrone.Core.Indexers.Definitions.XSpeeds.DoLogin() in ./Prowlarr.Core/Indexers/Definitions/XSpeeds.cs:line 90
   at NzbDrone.Core.Indexers.HttpIndexerBase`1.FetchIndexerResponse(IndexerRequest request) in ./Prowlarr.Core/Indexers/HttpIndexerBase.cs:line 671
   at NzbDrone.Core.Indexers.HttpIndexerBase`1.FetchPage(IndexerRequest request, IParseIndexerResponse parser) in ./Prowlarr.Core/Indexers/HttpIndexerBase.cs:line 603
   at NzbDrone.Core.Indexers.HttpIndexerBase`1.FetchReleases(Func`2 pageableRequestChainSelector, SearchCriteriaBase searchCriteria, Boolean isRecent) in ./Prowlarr.Core/Indexers/HttpIndexerBase.cs:line 421

Bingmano avatar May 13 '24 16:05 Bingmano

Sadly cherry picking the logs isn't helpful to diagnostic your issue, but I suspect you're either having some networking issues so maybe check if you're having package loss.

The issue discussed on this bug report is about getting Http request timed out and having to restart Prowlarr to fix the issue.

mynameisbogdan avatar May 13 '24 16:05 mynameisbogdan

I'll take a look into it and start a new thread if i cannot find anything on my end, thanks.

Bingmano avatar May 13 '24 16:05 Bingmano

Firstly you need to join our discord for support because we don't offer support on github and we're off-topic.

mynameisbogdan avatar May 13 '24 16:05 mynameisbogdan

Update: I haven't had this issue again since I changed the interface bind from * to 0.0.0.0. However, I since I don't know the root cause of the problem I'm not sure if this is just coincidence or not. If this is going to be a workaround going forward, a change to the code to allow users to make this change in the web UI would nice - otherwise they are forced to make the change in the config file.

nopoz avatar May 13 '24 17:05 nopoz

I changed the bind to 0.0.0.0 as @nopoz mentions above but I think I'm seeing something similar to what is being reported in this thread:

  • start container, able to use indexers
  • some time goes by, maybe 30-60 seconds
  • tons of System.Net.WebException: Http request timed out

I've verified that networking and dns are functional within the container, not sure why this is going on.

andrewdunndev avatar Jun 02 '24 17:06 andrewdunndev