Frequently Asked Questions

1. How can I view my application logs (runtime logs, build logs, access logs) in APP Launchpad?

In the APP Launchpad interface, locate the desired application instance and click the Logs button to view detailed logs such as runtime, build, and access logs. For further troubleshooting, click the Terminal button to access the container terminal and run diagnostic commands.

---

2. How can I bind a custom domain to my application in APP Launchpad?

In the application management interface (App Launchpad), click on the desired application and navigate to Update → Network → Public Address. Enter your domain name and complete the CNAME configuration to bind your custom domain. Flexible access policies for both internal and external networks are also supported.

---

3. How do I roll back to a previous version of my application in APP Launchpad?

If there are historical Docker images available, you can manually redeploy a specific version of the application image.

---

4. Does APP Launchpad support custom containers?

Yes! APP Launchpad supports deploying containers using custom Docker images. You can upload private images or reference public images and configure environment variables, port mappings, and other parameters during the deployment process.

---

5. Are HTTPS certificates for applications accessed through APP Launchpad managed automatically?

The platform provides default HTTPS access support and automatically manages certificates through an integrated system (such as Let's Encrypt). When binding a custom domain, the system will automatically request and renew certificates for that domain to ensure secure access.

---

6. How can I configure my application in APP Launchpad to connect to ClawCloud Database or other database services?

In the application configuration interface, use the Environment Variables or Configuration Files option to input the internal database connection address, port, username, password, and other required information.

---

7. What should I do if I get the "no healthy upstream" error when accessing my public URL?

This issue is typically caused by the following reasons:

1. Application instance is not ready: Check the application logs to confirm if the container started successfully and if the port is listening correctly.

2. Health check failure: Ensure the application's health check path (e.g., /health) returns a 200 status code.

3. Incorrect domain configuration: Verify if the CNAME for your custom domain points to the correct entry address.

4. Insufficient resources: Check if the container was terminated due to insufficient memory or CPU.

If the issue persists, we recommend submitting a support ticket or contacting technical support for further assistance.