Repology blocks Managed Renovate

[DucretJe]

How are you running Renovate?

A Mend.io-hosted app

Which platform you running Renovate on?

GitHub.com

Which version of Renovate are you using?

43.219.0

Please tell us more about your question or problem

Renovate fails to lookup repology dependencies (gets timeout)

Last time I seen it working was on June 5

Logs (if relevant)

Logs

WARN: Repology lookup failed with unexpected error
{
  "packageName": "debian_13/build-essential",
  "err": {
    "name": "RequestError",
    "code": "ETIMEDOUT",
    "timings": {
      "start": 1781594495314,
      "socket": 1781594495315,
      "lookup": 1781594495316,
      "error": 1781594495568,
      "phases": {
        "wait": 1,
        "dns": 1,
        "total": 254
      }
    },
    "options": {
      "headers": {
        "user-agent": "Mend-hosted Renovate/43.219.0 (https://**redacted**@mend.io)",
        "accept": "application/json",
        "accept-encoding": "gzip, deflate, br, zstd"
      },
      "url": "https://repology.org/tools/project-by?repo=debian_13&name_type=binname&target_page=api_v1_project&noautoresolve=on&name=build-essential",
      "hostType": "repology",
      "username": "",
      "password": "",
      "method": "GET",
      "http2": false
    },
    "stack": "RequestError: \n    at ClientRequest.<anonymous> (file:///usr/local/renovate/node_modules/.pnpm/got@14.6.6/node_modules/got/dist/source/core/index.js:868:107)\n    at Object.onceWrapper (node:events:631:26)\n    at ClientRequest.emit (node:events:521:24)\n    at ClientRequest.emit (node:domain:489:12)\n    at emitErrorEvent (node:_http_client:109:11)\n    at TLSSocket.socketErrorListener (node:_http_client:593:5)\n    at TLSSocket.emit (node:events:509:28)\n    at TLSSocket.emit (node:domain:489:12)\n    at emitErrorNT (node:internal/streams/destroy:170:8)\n    at emitErrorCloseNT (node:internal/streams/destroy:129:3)\n    at processTicksAndRejections (node:internal/process/task_queues:90:21)AggregateError: \n    at internalConnectMultiple (node:net:1193:18)\n    at internalConnectMultiple (node:net:1269:5)\n    at Timeout.internalConnectMultipleTimeout (node:net:1810:5)\n    at listOnTimeout (node:internal/timers:607:11)\n    at processTimers (node:internal/timers:541:7)"
  }
}

[reitzig]

Same: https://developer.mend.io/github/reitzig/texlive-docker/-/job/89f98ef3-77d3-457e-b571-0c0fe8e9bb9e

Probably related:

Due to increased traffic from misbehaving API clients, the terms of service have been updated: bulk clients are now required to provide a link to their source code repository with an accessible issue tracker.
repology.org/news

[jamietanna]

Thanks for sharing - we do end up sending more in-depth user-agents on Mend-hosted infra, as well as in the CLI, but not sure if there's additional contact needed with them?