Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Run Pipeline-runner behind a proxy

Hey I want to try the new pipeline runner feature. 

Because my it don't allows Linux-Pcs I try to setup the runner through WSL on windows. 


When starting the runner the following error occurs: 

[2021-07-14 07:14:42,963] Updating runner state to "ONLINE".
[2021-07-14 07:15:11,006] An error occurred whislt updating runner state to "ONLINE". finishConnect(..) failed: Connection refused
at io.netty.util.concurrent.SingleThreadEventExecutor$
at io.netty.util.internal.ThreadExecutorMap$
at java.base/ Source)
Wrapped by:$AnnotatedConnectException: finishConnect(..) failed: Connection refused:
Suppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException:
Error has been observed at the following site(s):
|_ checkpoint ⇢ Request to POST [DefaultWebClient]
Stack trace:
Wrapped by: java.lang.RuntimeException:$AnnotatedConnectException: finishConnect(..) failed: Connection refused:
at io.reactivex.internal.util.ExceptionHelper.wrapOrThrow(
at io.reactivex.internal.observers.BlockingMultiObserver.blockingGet(
at io.reactivex.Single.blockingGet(
at com.atlassian.pipelines.stargate.client.core.auth.oauth.OAuthHeaderInterceptorImpl.lambda$new$1(
at com.github.benmanes.caffeine.cache.LocalLoadingCache.lambda$newMappingFunction$2(
at com.github.benmanes.caffeine.cache.BoundedLocalCache.lambda$doComputeIfAbsent$14(
at java.base/java.util.concurrent.ConcurrentHashMap.compute(Unknown Source)
at com.github.benmanes.caffeine.cache.BoundedLocalCache.doComputeIfAbsent(
at com.github.benmanes.caffeine.cache.BoundedLocalCache.computeIfAbsent(
at com.github.benmanes.caffeine.cache.LocalCache.computeIfAbsent(
at com.github.benmanes.caffeine.cache.LocalLoadingCache.get(
at com.atlassian.pipelines.stargate.client.core.auth.oauth.OAuthHeaderInterceptorImpl.lambda$exchangeFilter$4(
at org.springframework.web.reactive.function.client.ExchangeFilterFunction.lambda$ofRequestProcessor$3(
at org.springframework.web.reactive.function.client.ExchangeFilterFunction.lambda$apply$2(
at org.springframework.web.reactive.function.client.DefaultWebClient$DefaultRequestBodyUriSpec.lambda$exchange$0(
at reactor.core.publisher.MonoDefer.subscribe(
at reactor.core.publisher.InternalMonoOperator.subscribe(
at reactor.core.publisher.FluxRetryWhen$RetryWhenMainSubscriber.resubscribe(
at reactor.core.publisher.FluxRetryWhen$RetryWhenOtherSubscriber.onNext(
at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.innerNext(
at reactor.core.publisher.FluxConcatMap$ConcatMapInner.onNext(
at reactor.core.publisher.MonoDelay$
... 7 common frames omitted
Wrapped by: reactor.retry.RetryExhaustedException: java.lang.RuntimeException:$AnnotatedConnectException: finishConnect(..) failed: Connection refused:
at reactor.retry.DefaultRetry.retry(
at reactor.retry.DefaultRetry.lambda$apply$1(
at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.drain(
at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.innerComplete(
at reactor.core.publisher.FluxConcatMap$ConcatMapInner.onComplete(
at reactor.core.publisher.MonoDelay$
at java.base/ Source)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$ Source)
at java.base/ Source)

So I think the problem is, that the working pc is behind a proxy and the runner has no chance to connect to bitbucket, because no proxy is configured. 


Any help on this problem would be nice. 

Thanks in advance  

1 answer

0 votes
Caroline R Atlassian Team Jul 19, 2021

Hi, @Dominic Warzok! Welcome to the community! 

Currently, proxy is not supported by Pipelines Runners, but we already have a feature request to implement this:

As you can see on the feature request, we have a workaround that can be performed:

Include the following configuration in `~/.docker/config.json` to force the docker daemon to add the proxy configuration while initiating the docker container.

  "proxies": {
    "default": {
      "httpProxy": "",
      "httpsProxy": ""

I've linked your question to this feature. Please consider adding yourself as a watcher, this way you get updated as we make progress with this. 

If you are not familiar with our Feature Request Policy, you can read more about it here: 

Please, feel free to share any additional questions or concerns regarding this subject. 

Kind regards,

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

2,247 views 2 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you