I'm creating a custom pipe, where I create a Report using the rest API and the proxies mentioned at the bottom of the Code Insights page.
{
"arguments": {},
"key": "report-service.general.forbidden",
"message": "Not authorized"
}
What am I doing wrong?
It turned out I was passing an ACCESS TOKEN through headers and using the proxy, which resulted in 403. Removing the ACCESS TOKEN and using the proxy only resolved the issue.
G'day, @Dani Asztalos
Welcome to the community!
Could you try to add this to your pipe script and see if that helps?
export HTTP_PROXY=http://host.docker.internal:29418
export http_proxy=http://host.docker.internal:29418
export HTTPS_PROXY=http://host.docker.internal:29418
export https_proxy=http://host.docker.internal:29418
git config "http.${BITBUCKET_GIT_HTTP_ORIGIN}.proxy" http://host.docker.internal:29418
I believe you need to configure the git config proxy as well if it's from docker.
Regards,
Syahrul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am using the Rest api, not git, so setting the git proxy would not help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.