Forum

Please see the image for the template.

Hello, thank you for your feedback. Regarding the points you raised, here is an explanation:

1. The presence of a tinyproxy template in the Marketplace does not mean that using it exempts you from AUP constraints. We provide tinyproxy for legitimate purposes such as internal team proxies, HTTP caching, and firewall filtering; just as Nginx is available in the Marketplace, but Nginx itself cannot be used as an excuse for hosting prohibited content. The same logic applies.

2. Our detection is not triggered simply because you "deployed a tinyproxy image," but because the egress traffic characteristics of that instance were identified as potentially being used for circumvention purposes. We are not 100% certain that it is being used for circumvention, but the traffic patterns do match the characteristics of such usage.

3. If your actual use case is different, please explain the purpose of this tinyproxy:

• Access source (Whose IP connects to it?)
• Access target (Which sites are being proxied?)
• User scale (Just yourself? Team? Publicly accessible?)

After manual review and confirmation, it can be restored and will not be automatically suspended again.

Please also try to understand our position: if prohibited usage (especially circumvention) on the platform is not handled in a timely manner, and our cloud providers (Tencent Cloud, Alibaba Cloud, Volcengine, etc.) impose restrictions on Zeabur's entire account, all users will be affected—including your other normal services (n8n, postgresql, OpenClaw, etc.). To protect all users, we must suspend such instances first and verify them later.

Additionally, we will take your feedback back for evaluation: whether we should add usage instructions or clearer AUP warnings for such tools in the Marketplace to avoid similar misunderstandings in the future. Thank you for pointing this out.

I fully understand the platform's original intent and policies, as I am also building SaaS products myself.

I intended to use it for personal purposes, mainly to conveniently view some WeChat official account articles while at work (since the company has blocked all QQ domains).

I haven't actually used it, because after trying, I found it didn't work, so I just left it alone a few days ago after spending some time setting it up.

I'm not sure why I suddenly received a warning; I even set up authentication for tinyproxy.

I have now deleted the project.

Hi Andy,

We have verified that you did indeed delete it. The issue was on our end regarding the cleanup; you did nothing wrong.

Here is the timeline (all in UTC+8):

• 04-24 14:21: Server suspended (AUP triggered).
• 04-24 16:44: You deleted the NetworkProxy project. The control plane recorded it successfully, but since the server was offline, the deletion command could not be sent to the k3s node.
• 04-24 22:31: After Ian restored the server, the original namespace (environment-69e6c9f728b1ec4f6706039f) was reactivated in k3s, and the tinyproxy container was automatically pulled up by the Deployment—this is why it wasn't visible on the dashboard but was still running on the server.

I have just manually cleared the orphaned namespace on the node. The tinyproxy container has been stopped, and there are no host-level tinyproxy installations on the server (only that one orphan pod).

We have noted this gap in our process and will improve it—if a user deletes a project after an AUP suspension, we should ensure the deleted resources are cleared when the server is restored, rather than requiring the user to follow up. Sorry for the inconvenience.