serverless plugin behind proxy
1
How can I use the command serverless plugin list behind proxy?
I am getting this error:
request to https://raw.githubusercontent.com/serverless/plugins/master/plugins.json failed, reason: connect ECONNREFUSED 151.101.84.133:443
The command serverless deploy works fine with my proxy, so the proxy and/or proxy configuration should not be the problem.
Versions
$ node --version
v11.1.0
$ npm --version
6.4.1
Environment variables
$ env | grep -i proxy
NO_PROXY=localhost,127.0.0.0/8,::1
http_proxy=http://localhost:3128/
npm_config_https_proxy=http://localhost:3128/
https_proxy=http://localhost:3128/
no_proxy=localhost,127.0.0.0/8,::1
npm_config_proxy=http://localhost:3128/
cURL
Even if I curl it, it works fine with my proxy settings. Truncated for brevity.
$ curl --verbose https://raw.githubusercontent.com/serverless/plugins/master/plugins.json
* Trying 127.0.0.1...
* Connected to localhost (127.0.0.1) port 3128 (#0)
* Establish HTTP proxy tunnel to raw.githubusercontent.com:443
> CONNECT raw.githubusercontent.com:443 HTTP/1.1
> Host: raw.githubusercontent.com:443
> User-Agent: curl/7.47.0
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 200 Connection established
< Connection: close
<
* Proxy replied OK to CONNECT request
* found 155 certificates in /etc/ssl/certs/ca-certificates.crt
* found 625 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_RSA_AES_128_GCM_SHA256
* server certificate verification OK
* server certificate status verification SKIPPED
* common name: www.github.com (matched)
* server certificate expiration date OK
* server certificate activation date OK
* certificate public key: RSA
* certificate version: #3
* subject: C=US,ST=California,L=San Francisco,O=GitHub, Inc.,CN=www.github.com
* start date: Thu, 23 Mar 2017 00:00:00 GMT
* expire date: Wed, 13 May 2020 12:00:00 GMT
* issuer: C=US,O=DigiCert Inc,OU=www.digicert.com,CN=DigiCert SHA2 High Assurance Server CA
* compression: NULL
* ALPN, server accepted to use http/1.1
> GET /serverless/plugins/master/plugins.json HTTP/1.1
> Host: raw.githubusercontent.com
> User-Agent: curl/7.47.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Security-Policy: default-src 'none'; style-src 'unsafe-inline'; sandbox
< Strict-Transport-Security: max-age=31536000
< X-Content-Type-Options: nosniff
< X-Frame-Options: deny
< X-XSS-Protection: 1; mode=block
< ETag: "53374f2ed929f6d42faf13ebb025e0ff985941f1"
< Content-Type: text/plain; charset=utf-8
< Cache-Control: max-age=300
< X-Geo-Block-List:
< X-GitHub-Request-Id: 447E:6762:1CABB8:1E679B:5BEAD6AF
< Content-Length: 45355
< Accept-Ranges: bytes
< Date: Tue, 13 Nov 2018 13:50:39 GMT
< Via: 1.1 varnish
< Connection: keep-alive
< X-Served-By: cache-bma1635-BMA
< X-Cache: MISS
< X-Cache-Hits: 0
< X-Timer: S1542117040.576321,VS0,VE107
< Vary: Authorization,Accept-Encoding
< Access-Control-Allow-Origin: *
< X-Fastly-Request-ID: 929450c7326d8ce7c7ffa13174cbd80c86ecc255
< Expires: Tue, 13 Nov 2018 13:55:39 GMT
< Source-Age: 0
<
[
proxy http-proxy serverless-framework serverless serverless-plugins
asked Nov 13 at 13:53
Azize
520417
add a comment |
1
How can I use the command serverless plugin list behind proxy?
I am getting this error:
request to https://raw.githubusercontent.com/serverless/plugins/master/plugins.json failed, reason: connect ECONNREFUSED 151.101.84.133:443
The command serverless deploy works fine with my proxy, so the proxy and/or proxy configuration should not be the problem.
Versions
$ node --version
v11.1.0
$ npm --version
6.4.1
Environment variables
$ env | grep -i proxy
NO_PROXY=localhost,127.0.0.0/8,::1
http_proxy=http://localhost:3128/
npm_config_https_proxy=http://localhost:3128/
https_proxy=http://localhost:3128/
no_proxy=localhost,127.0.0.0/8,::1
npm_config_proxy=http://localhost:3128/
cURL
Even if I curl it, it works fine with my proxy settings. Truncated for brevity.
$ curl --verbose https://raw.githubusercontent.com/serverless/plugins/master/plugins.json
* Trying 127.0.0.1...
* Connected to localhost (127.0.0.1) port 3128 (#0)
* Establish HTTP proxy tunnel to raw.githubusercontent.com:443
> CONNECT raw.githubusercontent.com:443 HTTP/1.1
> Host: raw.githubusercontent.com:443
> User-Agent: curl/7.47.0
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 200 Connection established
< Connection: close
<
* Proxy replied OK to CONNECT request
* found 155 certificates in /etc/ssl/certs/ca-certificates.crt
* found 625 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_RSA_AES_128_GCM_SHA256
* server certificate verification OK
* server certificate status verification SKIPPED
* common name: www.github.com (matched)
* server certificate expiration date OK
* server certificate activation date OK
* certificate public key: RSA
* certificate version: #3
* subject: C=US,ST=California,L=San Francisco,O=GitHub, Inc.,CN=www.github.com
* start date: Thu, 23 Mar 2017 00:00:00 GMT
* expire date: Wed, 13 May 2020 12:00:00 GMT
* issuer: C=US,O=DigiCert Inc,OU=www.digicert.com,CN=DigiCert SHA2 High Assurance Server CA
* compression: NULL
* ALPN, server accepted to use http/1.1
> GET /serverless/plugins/master/plugins.json HTTP/1.1
> Host: raw.githubusercontent.com
> User-Agent: curl/7.47.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Security-Policy: default-src 'none'; style-src 'unsafe-inline'; sandbox
< Strict-Transport-Security: max-age=31536000
< X-Content-Type-Options: nosniff
< X-Frame-Options: deny
< X-XSS-Protection: 1; mode=block
< ETag: "53374f2ed929f6d42faf13ebb025e0ff985941f1"
< Content-Type: text/plain; charset=utf-8
< Cache-Control: max-age=300
< X-Geo-Block-List:
< X-GitHub-Request-Id: 447E:6762:1CABB8:1E679B:5BEAD6AF
< Content-Length: 45355
< Accept-Ranges: bytes
< Date: Tue, 13 Nov 2018 13:50:39 GMT
< Via: 1.1 varnish
< Connection: keep-alive
< X-Served-By: cache-bma1635-BMA
< X-Cache: MISS
< X-Cache-Hits: 0
< X-Timer: S1542117040.576321,VS0,VE107
< Vary: Authorization,Accept-Encoding
< Access-Control-Allow-Origin: *
< X-Fastly-Request-ID: 929450c7326d8ce7c7ffa13174cbd80c86ecc255
< Expires: Tue, 13 Nov 2018 13:55:39 GMT
< Source-Age: 0
<
[
proxy http-proxy serverless-framework serverless serverless-plugins
asked Nov 13 at 13:53
Azize
520417
I also get a failed connection behind proxy like this, but it times out.
– Niklas Rosencrantz
Nov 14 at 8:05
add a comment |
1
1
1
How can I use the command serverless plugin list behind proxy?
I am getting this error:
request to https://raw.githubusercontent.com/serverless/plugins/master/plugins.json failed, reason: connect ECONNREFUSED 151.101.84.133:443
The command serverless deploy works fine with my proxy, so the proxy and/or proxy configuration should not be the problem.
Versions
$ node --version
v11.1.0
$ npm --version
6.4.1
Environment variables
$ env | grep -i proxy
NO_PROXY=localhost,127.0.0.0/8,::1
http_proxy=http://localhost:3128/
npm_config_https_proxy=http://localhost:3128/
https_proxy=http://localhost:3128/
no_proxy=localhost,127.0.0.0/8,::1
npm_config_proxy=http://localhost:3128/
cURL
Even if I curl it, it works fine with my proxy settings. Truncated for brevity.
$ curl --verbose https://raw.githubusercontent.com/serverless/plugins/master/plugins.json
* Trying 127.0.0.1...
* Connected to localhost (127.0.0.1) port 3128 (#0)
* Establish HTTP proxy tunnel to raw.githubusercontent.com:443
> CONNECT raw.githubusercontent.com:443 HTTP/1.1
> Host: raw.githubusercontent.com:443
> User-Agent: curl/7.47.0
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 200 Connection established
< Connection: close
<
* Proxy replied OK to CONNECT request
* found 155 certificates in /etc/ssl/certs/ca-certificates.crt
* found 625 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_RSA_AES_128_GCM_SHA256
* server certificate verification OK
* server certificate status verification SKIPPED
* common name: www.github.com (matched)
* server certificate expiration date OK
* server certificate activation date OK
* certificate public key: RSA
* certificate version: #3
* subject: C=US,ST=California,L=San Francisco,O=GitHub, Inc.,CN=www.github.com
* start date: Thu, 23 Mar 2017 00:00:00 GMT
* expire date: Wed, 13 May 2020 12:00:00 GMT
* issuer: C=US,O=DigiCert Inc,OU=www.digicert.com,CN=DigiCert SHA2 High Assurance Server CA
* compression: NULL
* ALPN, server accepted to use http/1.1
> GET /serverless/plugins/master/plugins.json HTTP/1.1
> Host: raw.githubusercontent.com
> User-Agent: curl/7.47.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Security-Policy: default-src 'none'; style-src 'unsafe-inline'; sandbox
< Strict-Transport-Security: max-age=31536000
< X-Content-Type-Options: nosniff
< X-Frame-Options: deny
< X-XSS-Protection: 1; mode=block
< ETag: "53374f2ed929f6d42faf13ebb025e0ff985941f1"
< Content-Type: text/plain; charset=utf-8
< Cache-Control: max-age=300
< X-Geo-Block-List:
< X-GitHub-Request-Id: 447E:6762:1CABB8:1E679B:5BEAD6AF
< Content-Length: 45355
< Accept-Ranges: bytes
< Date: Tue, 13 Nov 2018 13:50:39 GMT
< Via: 1.1 varnish
< Connection: keep-alive
< X-Served-By: cache-bma1635-BMA
< X-Cache: MISS
< X-Cache-Hits: 0
< X-Timer: S1542117040.576321,VS0,VE107
< Vary: Authorization,Accept-Encoding
< Access-Control-Allow-Origin: *
< X-Fastly-Request-ID: 929450c7326d8ce7c7ffa13174cbd80c86ecc255
< Expires: Tue, 13 Nov 2018 13:55:39 GMT
< Source-Age: 0
<
[
proxy http-proxy serverless-framework serverless serverless-plugins
asked Nov 13 at 13:53
Azize
520417
How can I use the command serverless plugin list behind proxy?
I am getting this error:
request to https://raw.githubusercontent.com/serverless/plugins/master/plugins.json failed, reason: connect ECONNREFUSED 151.101.84.133:443
The command serverless deploy works fine with my proxy, so the proxy and/or proxy configuration should not be the problem.
Versions
$ node --version
v11.1.0
$ npm --version
6.4.1
Environment variables
$ env | grep -i proxy
NO_PROXY=localhost,127.0.0.0/8,::1
http_proxy=http://localhost:3128/
npm_config_https_proxy=http://localhost:3128/
https_proxy=http://localhost:3128/
no_proxy=localhost,127.0.0.0/8,::1
npm_config_proxy=http://localhost:3128/
cURL
Even if I curl it, it works fine with my proxy settings. Truncated for brevity.
$ curl --verbose https://raw.githubusercontent.com/serverless/plugins/master/plugins.json
* Trying 127.0.0.1...
* Connected to localhost (127.0.0.1) port 3128 (#0)
* Establish HTTP proxy tunnel to raw.githubusercontent.com:443
> CONNECT raw.githubusercontent.com:443 HTTP/1.1
> Host: raw.githubusercontent.com:443
> User-Agent: curl/7.47.0
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 200 Connection established
< Connection: close
<
* Proxy replied OK to CONNECT request
* found 155 certificates in /etc/ssl/certs/ca-certificates.crt
* found 625 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_RSA_AES_128_GCM_SHA256
* server certificate verification OK
* server certificate status verification SKIPPED
* common name: www.github.com (matched)
* server certificate expiration date OK
* server certificate activation date OK
* certificate public key: RSA
* certificate version: #3
* subject: C=US,ST=California,L=San Francisco,O=GitHub, Inc.,CN=www.github.com
* start date: Thu, 23 Mar 2017 00:00:00 GMT
* expire date: Wed, 13 May 2020 12:00:00 GMT
* issuer: C=US,O=DigiCert Inc,OU=www.digicert.com,CN=DigiCert SHA2 High Assurance Server CA
* compression: NULL
* ALPN, server accepted to use http/1.1
> GET /serverless/plugins/master/plugins.json HTTP/1.1
> Host: raw.githubusercontent.com
> User-Agent: curl/7.47.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Security-Policy: default-src 'none'; style-src 'unsafe-inline'; sandbox
< Strict-Transport-Security: max-age=31536000
< X-Content-Type-Options: nosniff
< X-Frame-Options: deny
< X-XSS-Protection: 1; mode=block
< ETag: "53374f2ed929f6d42faf13ebb025e0ff985941f1"
< Content-Type: text/plain; charset=utf-8
< Cache-Control: max-age=300
< X-Geo-Block-List:
< X-GitHub-Request-Id: 447E:6762:1CABB8:1E679B:5BEAD6AF
< Content-Length: 45355
< Accept-Ranges: bytes
< Date: Tue, 13 Nov 2018 13:50:39 GMT
< Via: 1.1 varnish
< Connection: keep-alive
< X-Served-By: cache-bma1635-BMA
< X-Cache: MISS
< X-Cache-Hits: 0
< X-Timer: S1542117040.576321,VS0,VE107
< Vary: Authorization,Accept-Encoding
< Access-Control-Allow-Origin: *
< X-Fastly-Request-ID: 929450c7326d8ce7c7ffa13174cbd80c86ecc255
< Expires: Tue, 13 Nov 2018 13:55:39 GMT
< Source-Age: 0
<
[
proxy http-proxy serverless-framework serverless serverless-plugins
proxy http-proxy serverless-framework serverless serverless-plugins
asked Nov 13 at 13:53
Azize
520417
asked Nov 13 at 13:53
Azize
520417
edited Nov 13 at 16:17
asked Nov 13 at 13:53
Azize
520417
asked Nov 13 at 13:53
Azize
520417
asked Nov 13 at 13:53
Azize
520417
520417
I also get a failed connection behind proxy like this, but it times out.
– Niklas Rosencrantz
Nov 14 at 8:05
add a comment |
I also get a failed connection behind proxy like this, but it times out.
– Niklas Rosencrantz
Nov 14 at 8:05
I also get a failed connection behind proxy like this, but it times out.
– Niklas Rosencrantz
Nov 14 at 8:05
I also get a failed connection behind proxy like this, but it times out.
– Niklas Rosencrantz
Nov 14 at 8:05
add a comment |
1 Answer
1
active
oldest
votes
0
This was identified as a bug in serverless plugin according to this issue:
https://github.com/serverless/serverless/issues/5480
The solution will come from this PR:
https://github.com/serverless/serverless/pull/5481
serverless plugin simple does not support proxy up to this version.
answered Nov 14 at 12:40
Azize
520417
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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
});
}
});
draft saved
draft discarded
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%2fstackoverflow.com%2fquestions%2f53282581%2fserverless-plugin-behind-proxy%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
0
This was identified as a bug in serverless plugin according to this issue:
https://github.com/serverless/serverless/issues/5480
The solution will come from this PR:
https://github.com/serverless/serverless/pull/5481
serverless plugin simple does not support proxy up to this version.
answered Nov 14 at 12:40
Azize
520417
add a comment |
0
This was identified as a bug in serverless plugin according to this issue:
https://github.com/serverless/serverless/issues/5480
The solution will come from this PR:
https://github.com/serverless/serverless/pull/5481
serverless plugin simple does not support proxy up to this version.
answered Nov 14 at 12:40
Azize
520417
add a comment |
0
0
0
This was identified as a bug in serverless plugin according to this issue:
https://github.com/serverless/serverless/issues/5480
The solution will come from this PR:
https://github.com/serverless/serverless/pull/5481
serverless plugin simple does not support proxy up to this version.
answered Nov 14 at 12:40
Azize
520417
This was identified as a bug in serverless plugin according to this issue:
https://github.com/serverless/serverless/issues/5480
The solution will come from this PR:
https://github.com/serverless/serverless/pull/5481
serverless plugin simple does not support proxy up to this version.
answered Nov 14 at 12:40
Azize
520417
answered Nov 14 at 12:40
Azize
520417
answered Nov 14 at 12:40
Azize
520417
answered Nov 14 at 12:40
Azize
520417
520417
add a comment |
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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.
draft saved
draft discarded
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%2fstackoverflow.com%2fquestions%2f53282581%2fserverless-plugin-behind-proxy%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
I also get a failed connection behind proxy like this, but it times out.
– Niklas Rosencrantz
Nov 14 at 8:05