Frequently asked questions about SaaS Boost

If you enter an invalid SaaS Boost instance URL or an incorrect SaaS Boost product code, the system reports the following error:

The error name is SaasBoostCommodityNotFound, and the description is "The current SaaS Boost product code or public network address does not exist. Go back to My Services to modify the product configuration or unbind the product."

Re-enter your SaaS Boost product code and public network address. Ensure that you paste them without any leading or trailing spaces.

The SaaS Boost public network address field is in the Use Now section on the service instance details page.

The logs may show the following error: failed: The TLS connection was non-properly terminated.

This error often occurs due to intermittent connection issues with github.com during peak hours. If you encounter this error, click Retry and wait for the connection to succeed.

[executionStep begins at 2024-07-24 14:35:02]
[INFO] PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
[14:35:02] [SUCCESS] Credentials obtained successfully
[14:35:02] [INFO] Using working directory /root/workspace/my_repo
[14:35:02] [INFO] Executing step
[14:35:02] [INFO] BUILD_JOB_ID=230836360
[14:35:03] [INFO] Cleaning up directories /root/workspace /root/workspace/my_repo...
[14:35:03] git_host = github.com
[14:35:03] git clone https://github.com/<organization>/<repo>.git  --branch master /root/workspace/my_repo
[14:35:13] Cloning into '/root/workspace/my_repo'...
[14:35:13] fatal: unable to access 'https://github.com/<organization>/<repo>.git/': gnutls_handshake() failed: The TLS connection was non-properly terminated.
[14:35:13] [ERROR] Clone failed
[14:35:13] [ERROR] BUILD ERROR
[14:35:13] [ERROR] 230836360
[14:35:13] [ERROR] Step failed with return code: 2

The pipeline includes npm build and Java build stages. After the build completes, the pipeline uploads the JAR package for Function Compute to an OSS bucket and the server's JAR package to a Compute Nest artifact repository. The actual deployment begins after these files are uploaded.

• Function Compute is deployed by directly replacing the ZIP package in the OSS bucket.

• The server is deployed by running the deploy.sh script in the project.

Once you are familiar with the overall pipeline steps, you can use the pipeline's error logs to diagnose common development issues.

On the pipeline build task details page, go to the Local Debugging Tool tab. This page provides Docker commands, including docker volume create and docker run, to replicate the exact build environment locally for debugging. Click the Copy button to get all the commands.

This failure typically occurs in the following scenarios:

• The user who created the service instance has insufficient permissions.

  If you use a RAM user, you must grant the permissions listed in the following table. For instructions on granting permissions to a RAM user, see Manage RAM user permissions.

  Required cloud resource permissions

  Policy name	Description
  AliyunECSFullAccess	Full access to ECS.
  AliyunVPCFullAccess	Full access to VPC.
  AliyunROSFullAccess	Full access to ROS.
  AliyunCloudMonitorFullAccess	Full access to CloudMonitor.
  AliyunOSSFullAccess	Full access to OSS.
  AliyunOOSFullAccess	Full access to OOS.
  AliyunFCFullAccess	Full access to Function Compute.
  AliyunOTSFullAccess	Full access to Tablestore.
  AliyunComputeNestSupplierFullAccess	Full access for suppliers to manage Compute Nest.

• The selected ECS instance type is sold out in the current availability zone. Choose a different instance type or availability zone and try again.

• A required plugin is not installed in the ACK cluster.

  Install the ack-pod-identity-webhook plugin in your ACK cluster.

  In the ACK console, go to O&M > Add-ons in the left-side navigation pane. On the Security tab, find the ack-pod-identity-webhook component card and click Install.

For more details, view the deployment logs on the service instance details page.

In the Compute Nest console, click Service Instances in the left-side navigation pane. Go to the details page of the relevant service instance, select the Logs tab, and then click the Deployment Logs sub-tab to view the deployment logs. The logs contain information such as the date, log category, resource type, associated ID, source, and status.

• Reverse proxy

  A common method is to use a reverse proxy server, such as Nginx, Apache, HAProxy, or Traefik. You can configure a reverse proxy on the server hosting Domain B to forward requests to the corresponding port on Domain A.

• Cloud load balancer

  You can configure a cloud load balancer to forward requests received for Domain B to the backend server and port associated with Domain A. This is typically configured through the load balancer's management interface.