Tasks fails behind when agent is behind proxy

[amejiasr]

Hello,
We are experiencing an issue running this task from devops.

Task : Azure Data Factory Trigger
Description : Start/stop an Azure Data Factory Trigger
Version : 2.2.0
Author : Jan Pieter Posthuma
Help : More Information

We are using a private agent to run the whole pipeline, but when we reach the task stop adf triggers it fails with the next error:
"
2020-04-03T11:55:39.5962047Z ##[debug]a8353143-a5bb-4b8a-bc30-78206609c459 auth param serviceprincipalid = ***
2020-04-03T11:55:39.5964210Z ##[debug]a8353143-a5bb-4b8a-bc30-78206609c459 auth param serviceprincipalkey = ***
2020-04-03T11:55:39.5965894Z ##[debug]a8353143-a5bb-4b8a-bc30-78206609c459 data environmentAuthorityUrl = https://login.windows.net/
2020-04-03T11:55:39.5967922Z ##[debug]a8353143-a5bb-4b8a-bc30-78206609c459 auth param tenantid = ***
2020-04-03T11:55:39.5969647Z ##[debug]a8353143-a5bb-4b8a-bc30-78206609c459=https://management.azure.com/
2020-04-03T11:55:39.5971122Z ##[debug]Parsed task inputs
2020-04-03T11:55:39.6195880Z (node:35240) Warning: Use Cipheriv for counter mode of aes-256-ctr
2020-04-03T11:55:39.6851206Z ##[error]Error login in to Azure. Please check the Service Configuration. Error: Failed to acquire token for application with the provided secret.
Error: tunneling socket could not be established, cause=socket hang up.
2020-04-03T11:55:39.6863609Z ##[debug]Processed: ##vso[task.issue type=error;]Error login in to Azure. Please check the Service Configuration. Error: Failed to acquire token for application with the provided secret. %0AError: tunneling socket could not be established, cause=socket hang up.
2020-04-03T11:55:39.6865325Z ##[debug]task result: Failed
2020-04-03T11:55:39.6866464Z ##[error]Unhandled: Azure clients require credentials.
2020-04-03T11:55:39.6867714Z ##[debug]Processed: ##vso[task.issue type=error;]Unhandled: Azure clients require credentials.
2020-04-03T11:55:39.6869986Z ##[debug]Processed: ##vso[task.complete result=Failed;]Unhandled: Azure clients require credentials.
2020-04-03T11:55:39.6870808Z ##[debug]task result: Failed
2020-04-03T11:55:39.6872330Z ##[debug]Processed: ##vso[task.complete result=Failed;]
2020-04-03T11:55:39.6891126Z ##[section]Finishing: Stops trigger to be deployed
"

We have tested the configuration from devops, agent and access to Azure and it is working fine, but we get the above error.

How can we solve it?
Alejandro Mejías

[liprec]

If I look at the error message it looks like the service connection with Azure is not working properly:
Error login in to Azure. Please check the Service Configuration. Error: Failed to acquire token for application with the provided secret. %0AError: tunneling socket could not be established, cause=socket hang up.

Can you validate or reconfigure the Service connection with Azure?

[amejiasr]

Sorry for the delay, It was bank holiday here...
I verified the service configuration in azure, and it works as you can see below:

[amejiasr]

The connection service was tested with Azure support and they granted that the access to Azure was available and working rigth...

[liprec]

Can your agent directly connect to Azure? Or does it connect via a proxy?

[amejiasr]

Hello Jan, We are running the agent behind a proxy, but the powershell cmdlet to stop and start the trigger launched through the same agent works fine… Best regards Alejandro Mejías De: Jan Pieter Posthuma [mailto:[email protected]] Enviado el: viernes, 17 de abril de 2020 11:53 Para: liprec/vsts-publish-adf <[email protected]> CC: ALEJANDRO MEJIAS RIOS (Contractor) <[email protected]>; Author <[email protected]> Asunto: [EXTERNAL] Re: [liprec/vsts-publish-adf] fail to run stop adf triggers from devops pipeline (#55) Can your agent directly connect to Azure? Or does it connect via a proxy? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/liprec/vsts-publish-adf/issues/55*issuecomment-615155554__;Iw!!FVajH6CFHhmYMuQ!oqe1Bjz7UKPpKFikzjq3Em798jIRu4AR-74NitewipSwJSnb1y5n4gjhBo20UcSgpZGBbds-p3U$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/APBOVKAX7GBRITDGGZF6WMDRNARIZANCNFSM4L36L6FA__;!!FVajH6CFHhmYMuQ!oqe1Bjz7UKPpKFikzjq3Em798jIRu4AR-74NitewipSwJSnb1y5n4gjhBo20UcSgpZGB3wk36oc$>. **************************************

[liprec]

That is (probably) causing the issue as currently there is no special code regarding connection via a proxy.
I will take a look what I can do to enable connection via a proxy server.

[amejiasr]

Great, thank you… Best regards. Alejandro Mejías De: Jan Pieter Posthuma [mailto:[email protected]] Enviado el: viernes, 17 de abril de 2020 13:01 Para: liprec/vsts-publish-adf <[email protected]> CC: ALEJANDRO MEJIAS RIOS (Contractor) <[email protected]>; Author <[email protected]> Asunto: [EXTERNAL] Re: [liprec/vsts-publish-adf] fail to run stop adf triggers from devops pipeline (#55) That is (probably) causing the issue as currently there is no special code regarding connection via a proxy. I will take a look what I can do to enable connection via a proxy server. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/liprec/vsts-publish-adf/issues/55*issuecomment-615183645__;Iw!!FVajH6CFHhmYMuQ!tQ-0flya-ZOqxUPifctN8qju3FFQBTRcan9G9Rw__HXcowYeYrte5GCSVof4JOnENrQ-Cb9-Up4$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/APBOVKEIWICOLESSOTW6HSTRNAZGPANCNFSM4L36L6FA__;!!FVajH6CFHhmYMuQ!tQ-0flya-ZOqxUPifctN8qju3FFQBTRcan9G9Rw__HXcowYeYrte5GCSVof4JOnENrQ-eSVy6Dc$>. **************************************