Powershell Core on linux through Proxy connection issues
I am unable to get Powershell Core 6.1.0 on Linux to access a proxy successfully. Our corporate proxy utilizes IP based authentication and not user based.
So when I attempt to Invoke-WebRequest a bad URL, it will return the HTML of the proxy server rejecting the URL. When I attempt to iwr a genuine allowed URL (one, for example, I am able to browse from firefox on my Ubuntu server).
This is all an attempt to download modules from Powershell Gallery, again browsable from the VM, but cannot access the gallery from powershell even though it knows to use the proxy.
I get a common error on Invoke-WebRequests of 'No such device or address'.
linux powershell proxy powershell-6.1
add a comment |
I am unable to get Powershell Core 6.1.0 on Linux to access a proxy successfully. Our corporate proxy utilizes IP based authentication and not user based.
So when I attempt to Invoke-WebRequest a bad URL, it will return the HTML of the proxy server rejecting the URL. When I attempt to iwr a genuine allowed URL (one, for example, I am able to browse from firefox on my Ubuntu server).
This is all an attempt to download modules from Powershell Gallery, again browsable from the VM, but cannot access the gallery from powershell even though it knows to use the proxy.
I get a common error on Invoke-WebRequests of 'No such device or address'.
linux powershell proxy powershell-6.1
add a comment |
I am unable to get Powershell Core 6.1.0 on Linux to access a proxy successfully. Our corporate proxy utilizes IP based authentication and not user based.
So when I attempt to Invoke-WebRequest a bad URL, it will return the HTML of the proxy server rejecting the URL. When I attempt to iwr a genuine allowed URL (one, for example, I am able to browse from firefox on my Ubuntu server).
This is all an attempt to download modules from Powershell Gallery, again browsable from the VM, but cannot access the gallery from powershell even though it knows to use the proxy.
I get a common error on Invoke-WebRequests of 'No such device or address'.
linux powershell proxy powershell-6.1
I am unable to get Powershell Core 6.1.0 on Linux to access a proxy successfully. Our corporate proxy utilizes IP based authentication and not user based.
So when I attempt to Invoke-WebRequest a bad URL, it will return the HTML of the proxy server rejecting the URL. When I attempt to iwr a genuine allowed URL (one, for example, I am able to browse from firefox on my Ubuntu server).
This is all an attempt to download modules from Powershell Gallery, again browsable from the VM, but cannot access the gallery from powershell even though it knows to use the proxy.
I get a common error on Invoke-WebRequests of 'No such device or address'.
linux powershell proxy powershell-6.1
linux powershell proxy powershell-6.1
edited Oct 26 '18 at 15:55
Ramhound
20.3k156085
20.3k156085
asked Oct 25 '18 at 13:05
ourkidourkid
11
11
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
To get through your proxy correctly I advise you to export your proxy env variable from your Linux layer. This way:
export HTTP_PROXY=http://your-proxy:3128
export HTTPS_PROXY=http://your-proxy:3128
Be careful about the uri, do not put the trailing / at the end of your proxy (cf. this post )
Then on your PowerShell layer you should be able to set the default repository with this:
Register-PSRepository -Default
This command does not work from my Windows session but it does on a PowerShell console from Linux
Eventually you could try the last command from this topic that I've tried before PowerShell crash me something like
If you want to register the default PSRepository PSGallery use Register-PSRepository -Default
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1369945%2fpowershell-core-on-linux-through-proxy-connection-issues%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
To get through your proxy correctly I advise you to export your proxy env variable from your Linux layer. This way:
export HTTP_PROXY=http://your-proxy:3128
export HTTPS_PROXY=http://your-proxy:3128
Be careful about the uri, do not put the trailing / at the end of your proxy (cf. this post )
Then on your PowerShell layer you should be able to set the default repository with this:
Register-PSRepository -Default
This command does not work from my Windows session but it does on a PowerShell console from Linux
Eventually you could try the last command from this topic that I've tried before PowerShell crash me something like
If you want to register the default PSRepository PSGallery use Register-PSRepository -Default
add a comment |
To get through your proxy correctly I advise you to export your proxy env variable from your Linux layer. This way:
export HTTP_PROXY=http://your-proxy:3128
export HTTPS_PROXY=http://your-proxy:3128
Be careful about the uri, do not put the trailing / at the end of your proxy (cf. this post )
Then on your PowerShell layer you should be able to set the default repository with this:
Register-PSRepository -Default
This command does not work from my Windows session but it does on a PowerShell console from Linux
Eventually you could try the last command from this topic that I've tried before PowerShell crash me something like
If you want to register the default PSRepository PSGallery use Register-PSRepository -Default
add a comment |
To get through your proxy correctly I advise you to export your proxy env variable from your Linux layer. This way:
export HTTP_PROXY=http://your-proxy:3128
export HTTPS_PROXY=http://your-proxy:3128
Be careful about the uri, do not put the trailing / at the end of your proxy (cf. this post )
Then on your PowerShell layer you should be able to set the default repository with this:
Register-PSRepository -Default
This command does not work from my Windows session but it does on a PowerShell console from Linux
Eventually you could try the last command from this topic that I've tried before PowerShell crash me something like
If you want to register the default PSRepository PSGallery use Register-PSRepository -Default
To get through your proxy correctly I advise you to export your proxy env variable from your Linux layer. This way:
export HTTP_PROXY=http://your-proxy:3128
export HTTPS_PROXY=http://your-proxy:3128
Be careful about the uri, do not put the trailing / at the end of your proxy (cf. this post )
Then on your PowerShell layer you should be able to set the default repository with this:
Register-PSRepository -Default
This command does not work from my Windows session but it does on a PowerShell console from Linux
Eventually you could try the last command from this topic that I've tried before PowerShell crash me something like
If you want to register the default PSRepository PSGallery use Register-PSRepository -Default
answered Jan 8 at 10:14
Thibault LoisonThibault Loison
11
11
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1369945%2fpowershell-core-on-linux-through-proxy-connection-issues%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown