ZKRINET Docs
Platform

Troubleshooting

My deploy was rolled back

The project didn't respond within about 30 seconds after the restart, or / didn't show your pb_public/index.html. Everything is restored to the state before the deploy. Open the Deploy tab and click the deploy — the log shows the last lines from PocketBase.

Common causes:

If you have a computer: run the same code locally with PocketBase 0.40.4 (./pocketbase serve) — the error usually shows up directly in the terminal.

The project doesn't respond

If the project shows as Error in the panel, we restart it automatically, and after two missed checks you get an alert. If you just deployed something: look in the deploy log. If you just changed building blocks: look in the log under Building blocks.

The start page shows "Zkrinet" instead of my site

You don't have a pb_public/index.html yet. Deploy it with deploy.

I have old CSS/JS after a deploy

Hard-reload the page (Ctrl/Cmd + Shift + R). Files without their own Cache-Control get private, no-cache, so the browser asks for new versions — but a tab that has been open for a long time can have old code in memory.

My new address or domain doesn't work for me

Try from your phone on 4G/5G. If it works there, but not on your computer, your router or computer has an old DNS answer saved. Restart the router, or temporarily change your computer's DNS to 1.1.1.1.

I can't get into the admin panel

Email from my project doesn't arrive

PocketBase sends email via the SMTP service you set up under Settings → Mail settings in the admin panel — just like when you run it yourself. Use port 465 or 587; port 25 is closed. Test with Send test email.

Rate limits hit everyone at the same time

The base layer sets Trusted proxy to CF-Connecting-IP so that each visitor is counted separately. If you have changed Settings → Trusted proxy yourself, your setting applies. See Visitor IP address.

The building block couldn't be installed

The change was rolled back if the project didn't respond afterwards. The log under Building blocks shows why. Most common is a clash with a file of your own that has the same name as the block's — the block's version is then used, and the log says so.

Nothing helps

Email hej@zkrinet.com with the project's address and what you did just before.