When the Serverless Framework CLI is started, if a component is referenced in the yaml configuration file by default, you need to make sure that the folder is empty before you can run the component installation command properly.
serverless create command again in an empty folder will not cause this error.
If you have any other questions or feedback, please visit GitHub Repository Issues.
This error is caused by account arrears, as it is impossible to create pay-as-you-go resources. Please check whether your account is in arrears. This error can be resolved by topping up your account to a positive balance.
Under the strict permission management of Window Powershell, you only need to run the
set-executionpolicy remotesigned command for the deployment. In Windows, we recommend using the
serverless deploy command.
Problem: Serverless Framework checks whether the user is in Mainland China by default during deployment. If your development environment is outside Mainland China and you want to use the Mainland China edition of Serverless Framework, you can configure it as follows:
Solution: add SERVERLESS_PLATFORM_VENDOR=tencent in the .env file to start the Mainland China edition by default, which provides an interactive quick deployment process (for more information, please see Getting Started).
Problem: the error message is Cannot get secretId/Key, your account could be sub-account or does not have access, please check if SLS_QcsRole role exists in your account, and visit https://console.cloud.tencent.com/cam to bind this role to your account.
Solution: this error is caused by insufficient account permissions. You can update the configuration as instructed in Account and Permission Configuration.
If you have any other questions or feedback, please submit a ticket or Github issues for assistance.
Problem: your environment does not have permission to access the public network and can access the public network only through a proxy, and a network failure is reported when
sls deploy is executed.
Solution: add the following configuration to the .env file:
HTTP_PROXY=http://127.0.0.1:12345 # Your proxy HTTPS_PROXY=http://127.0.0.1:12345 # Your proxy