Lookup error (403) on public endpoints for customManager/customDatasources #34204
Replies: 4 comments 10 replies
-
Hi there, Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible. Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues. Please follow these steps:
If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide. The Renovate team |
Beta Was this translation helpful? Give feedback.
-
This doesn't reproduce for me when I run locally. My best guess is:
|
Beta Was this translation helpful? Give feedback.
-
For the hosted Renovate, what might be needed to get the custom datasource to use a proper/built-in token for In the logs I see for example: DEBUG: hostRules: no authentication for api.github.com
DEBUG: GET https://api.github.com/repos/ibmruntimes/semeru11-binaries/releases = (code=ERR_NON_2XX_3XX_RESPONSE, statusCode=403 retryCount=0, duration=5)
DEBUG: Failed to look up custom.semeru package java
{
"dependency": "java"
"packageFile": ".tool-versions"
} It worked before (just 2 days ago), but just started failing for me like this / over here: |
Beta Was this translation helpful? Give feedback.
-
Ok there is an alternative solution to my initial issue: as a I rely from "standard" Github content, I can also use github-release or git-refs datasources (I missed them when reading the docs). |
Beta Was this translation helpful? Give feedback.
-
How are you running Renovate?
A Mend.io-hosted app
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
No response
Please tell us more about your question or problem
Hello 👋🏽
I would like some help to understand why Renovate seems to work alternatively with my configuration, using a public endpoint as customDatasource
When I activate this configuration a pull-request is created, but the following runs of renovate close it.
Looking at the job runs on my dashboard, I see the following:
The endpoint I use requires no authentication (a simple
curl https://api.github.com/repos/protocolbuffers/protobuf/releases
works fine) so I don't understand why the PR is created when I enable the rule, and is then auto-closed following these 403 errors.Am I missing something in the configuration?
Thanks in advance for your help.
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions