Why is it like this? If it keeps giving errors and can't be used, I want a refund.
ForumForumWhy is it like this? If it keeps giving errors and can't be used, I want a refund.
Hi! I checked your project — good news, your SillyTavern is up and running now. Your service sillytavern-tated (talkwithhusband.zeabur.app) is in RUNNING state and its logs show it actively serving chat, so the deployment is healthy.
Here's what happened. Your first service was deployed straight from the raw ghcr.io/sillytavern/sillytavern image. The thing is, SillyTavern ships locked down for local use only:
127.0.0.1 (not 0.0.0.0), and127.0.0.1.Zeabur's reverse proxy reaches your container from an internal cluster IP (10.42.0.1), which isn't on that whitelist — so the proxy could never connect, and the service kept crash-looping. That's the "NOT RUNNING" you saw. It's not a fault with the server; it's just that a bare image has none of the settings needed to be reachable from outside.
Our SillyTavern template (which you redeployed with) pre-configures all of that — it opens the listen address, swaps whitelist mode for a proper login, sets the right port, and adds a persistent volume for your chats and characters. That's why it works now. 👍
When you open the site you'll get a username/password popup — that's the template's built-in login, not an error:
zeaburPASSWORD. You can change both there anytime.On the refund: since you're on a Tencent (Jakarta) server, you can cancel and get refunded yourself anytime from Dashboard → your server's page → Cancel — no need to wait on us. But it's working now, so hopefully you won't need to. Let me know if anything's still off!
This post has been inactive for a while. We will be closing it in 2 days if there is no new activity.