Forum

Hello,

We have checked your server (Lightsail Tokyo 2C 2GB), and the server itself is running normally. K3s and all system components are functioning correctly, and your other services are also running as expected.

The error "This service is not allowed to deploy on Zeabur" is triggered by the platform's security scanning system blocking the deployment, rather than an issue with the server or the project itself. This indicates that there is content in your GitHub repo that triggered a security check.

Possible reasons:

1. The repo contains files flagged as sensitive (e.g., API keys, credentials, or content misidentified by the security engine).
2. The static site's HTML/JS references external resources that have been flagged.

Suggested actions:

1. Ensure that the repo does not contain any .env files, API keys, or credentials.
2. Check if any sensitive files were committed due to a missing .gitignore.
3. Try creating a minimal test repo (with only an index.html) to see if it deploys successfully — this will help determine if the issue is with the repo content or at the account level.

If the minimal repo also fails to deploy, please let us know, and we will further investigate the specific reason for the security block from our backend.

Thanks for the reply.

I managed to troubleshoot the issue and found that the product link shared by the Google extension might have been flagged as sensitive information: https://chromewebstore.google.com/detail/dlgicionoohogeebgimjjcelfedcoobj?utm_source=item-share-cb

After removing that link, the deployment worked normally.