Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Serverless v4.14.1 doesn't work behind the proxy #13062

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
nminhquang opened this issue Apr 21, 2025 · 1 comment
Closed

Serverless v4.14.1 doesn't work behind the proxy #13062

nminhquang opened this issue Apr 21, 2025 · 1 comment
Assignees

Comments

@nminhquang
Copy link

Issue description

I'm facing the issue that look like serverless fw cannot work with proxy properly.
It can access install.serverless.com through proxy but when it try to publish metric to core.serverless.com, it accessed directly instead of through proxy
Here is the logs:
serverless deploy --config serverless.yml --verbose --debug --disable-usage-reporting

s:core: {
node: 'v18.20.6',
os: 'linux',
arch: 'x64',
shell: undefined,
cwd: '/builds/pg/applications/appl-automation/terraform-aws-lambda-jobs',
nodeJsPath: '/usr/bin/node-18',
scriptPath: '/root/.serverless/releases/4.14.1/package/dist/sf-core.js',
scriptArgs: [
'deploy',
'--config',
'serverless.yml',
'--verbose',
'--debug',
'--disable-usage-reporting'
],
logLevel: 'debug',
isInteractive: undefined
}
s:core: { serverless_framework: '4.14.1' }
Initializing
Initializing
s:core:router: {
command: [ 'deploy' ],
options: {
config: 'serverless.yml',
verbose: true,
debug: '*',
'disable-usage-reporting': true
},
versions: { serverless_framework: '4.14.1' },
compose: undefined
}
s:core:router: CfnRunner returned an empty customConfigFilePath, skipping
s:core:router: ServerlessContainerFrameworkRunner returned an empty customConfigFilePath, skipping
Authenticating
s:core:auth:get-authenticated-data: license key provided manually
Finalizing
s:core:router: Saving meta record to global .serverless directory.
s:core:router: Finalization failed: Error publishing telemetry event batches: Not authenticated
s:core:router:finalization-error-handler: Error during finalization: Error: Sending events failed: Error publishing telemetry event batches: Not authenticated
s:core:router:finalization-error-handler: Error during telemetry event handling: Not authenticated
s:cli-error-handler: Error: request to https://core.serverless.com/api/bff/ failed, reason: connect ETIMEDOUT 100.27.167.56:443
at Authentication.getClientDataFromAccessKey (/root/.serverless/releases/4.14.1/sf-core/src/lib/auth/index.js:1077:13)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at Authentication.getAuthenticatedData (/root/.serverless/releases/4.14.1/sf-core/src/lib/auth/index.js:431:26)
at Authentication.authenticate (/root/.serverless/releases/4.14.1/sf-core/src/lib/auth/index.js:1288:12)
at TraditionalRunner.resolveVariablesAndAuthenticate (/root/.serverless/releases/4.14.1/sf-core/src/lib/runners/index.js:272:30)
at TraditionalRunner.run (/root/.serverless/releases/4.14.1/sf-core/src/lib/runners/framework.js:76:31)
at route (/root/.serverless/releases/4.14.1/sf-core/src/lib/router.js:101:20)
at Object.run (/root/.serverless/releases/4.14.1/sf-core/src/index.js:39:3)
at run2 (/root/.serverless/releases/4.14.1/sf-core/bin/sf-core.js:31:3)
✖ Error: request to https://core.serverless.com/api/bff/ failed, reason: connect ETIMEDOUT 100.27.167.56:443
at Authentication.getClientDataFromAccessKey (/root/.serverless/releases/4.14.1/sf-core/src/lib/auth/index.js:1077:13)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at Authentication.getAuthenticatedData (/root/.serverless/releases/4.14.1/sf-core/src/lib/auth/index.js:431:26)
at Authentication.authenticate (/root/.serverless/releases/4.14.1/sf-core/src/lib/auth/index.js:1288:12)
at TraditionalRunner.resolveVariablesAndAuthenticate (/root/.serverless/releases/4.14.1/sf-core/src/lib/runners/index.js:272:30)
at TraditionalRunner.run (/root/.serverless/releases/4.14.1/sf-core/src/lib/runners/framework.js:76:31)
at route (/root/.serverless/releases/4.14.1/sf-core/src/lib/router.js:101:20)
at Object.run (/root/.serverless/releases/4.14.1/sf-core/src/index.js:39:3)
at run2 (/root/.serverless/releases/4.14.1/sf-core/bin/sf-core.js:31:3)
For help, try the following:
• Run the command again with the "--debug" option
• Run "serverless support"
• Review the docs: https://www.serverless.com/framework/docs/

I have set proxy using command:
export HTTPS_PROXY=proxyhost:port
export HTTP_PROXY=proxyhost:port
export http_proxy=proxyhost:port
export https_proxy=proxyhost:port
And set license key:
export SERVERLESS_LICENSE_KEY=$SERVERLESS_LICENSE_KEY

Context

✖ Error: request to https://core.serverless.com/api/bff/ failed, reason: connect ETIMEDOUT 54.86.177.1:443
at Authentication.getClientDataFromAccessKey (file:///root/.serverless/releases/4.14.1/package/dist/sf-core.js:559:18321)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Authentication.getAuthenticatedData (file:///root/.serverless/releases/4.14.1/package/dist/sf-core.js:559:5368)
at async Authentication.authenticate (file:///root/.serverless/releases/4.14.1/package/dist/sf-core.js:559:21808)
at async _CoreRunner.resolveVariablesAndAuthenticate (file:///root/.serverless/releases/4.14.1/package/dist/sf-core.js:563:2377)
at async _CoreRunner.run (file:///root/.serverless/releases/4.14.1/package/dist/sf-core.js:877:6701)
at async route (file:///root/.serverless/releases/4.14.1/package/dist/sf-core.js:1167:2779)
at async Object.run (file:///root/.serverless/releases/4.14.1/package/dist/sf-core.js:1168:3661)
at async run2 (file:///root/.serverless/releases/4.14.1/package/dist/sf-core.js:1168:4815)
For help, try the following:
• Run the command again with the "--debug" option
• Run "serverless support"
• Review the docs: https://www.serverless.com/framework/docs/

@czubocha czubocha self-assigned this May 1, 2025
@czubocha
Copy link
Contributor

czubocha commented May 1, 2025

Hey @nminhquang, thanks for reporting this!
We've fixed the issue in v4.14.2. Give it a try and let us know if you're still running into any problems.

@czubocha czubocha closed this as completed May 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants