Score:0

Best way to disable default Azure proxy on on-prem hosts

in flag

I was recently doing some work on some servers, and had issues with outbound connectivity. I tracked down the file /usr/lib/systemd/system.conf.d/proxy.conf which contained the line DefaultEnvironment="https_proxy=http://100.79.11.37:8080" - this had the effect of making all https calls made by all systemd units go out via this proxy, which was the cause of the issues. I'm told this is part of a set of tools to make on-prem servers behave like Azure servers.

Once found I was able to work around it easily by putting a line Environment=no_proxy=* in my own service definition files.

For future peoples sake (internet searches turned up nothing for "100.79.11.37 8080" at the time) and out of curiosity, how are other people dealing with this?

  • Overriding in each service file separately like me?
  • Putting in another custom conf (with potentially more sophisticated rules)?
  • Just removing that bundled conf file entirely?
  • Something better?
ng flag
If these are on-prem servers, so not running in Azure, where is the proxy setting coming from in the first place?
garethhumphriesgkc avatar
in flag
I believe it's installed as part of the ADC suite, which is a tool Microsoft distribute for connecting on-prem services to Azure.
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.