Troubleshooting
Fixes for a server that won't start, a licence the store can't reach, email that doesn't send, a read-only server, and a Mac app that won't sync.
This page lists problems in the order you're likely to meet them, with the message you'll see and what to do. Start with the server's log, because it usually names the problem:
journalctl -u chronoslice -n 50
The server won't start
Run sudo systemctl status chronoslice and read the last lines of the log. These are the messages you may see.
"released on … after this server's licence stopped covering updates"
The full message reads ChronoSlice 0.3.0 was released on 2027-12-01, after this server's licence stopped covering updates on 2027-11-12. The newest release it covers is ChronoSlice 0.2.0. Renew the licence at https://chronoslice.app/account/licenses, or keep running the release you had. The release you started was dated after your licence's updates ended. Your data isn't touched. Renew and start it again, or go back to the release you had. See When updates end.
"Set CHRONOSLICE_MAIL_FROM too"
You set CHRONOSLICE_SMTP_URL without CHRONOSLICE_MAIL_FROM. Set both, or neither. See Email.
"CHRONOSLICE_SMTP_URL must start with smtps://, smtp:// or file://"
The address has the wrong form. See Email for the forms.
"CHRONOSLICE_MAIL_FROM isn't an email address"
Use an address such as [email protected], or a name and address such as Your Studio <[email protected]>.
"invalid value 'yes' for '--secure-cookies'"
CHRONOSLICE_SECURE_COOKIES takes true or false, and nothing else.
"Address already in use"
Another program is using the port, or ChronoSlice is already running. Check with sudo ss -ltnp | grep 7340. Stop the other program, or set a different CHRONOSLICE_BIND, and change your reverse proxy to match.
"unable to open database file" or "attempt to write a readonly database"
The service's user can't use the database. Check CHRONOSLICE_DB, and check who owns the files:
ls -l /var/lib/chronoslice
sudo chown -R chronoslice:chronoslice /var/lib/chronoslice
The database, and its -wal and -shm files, must belong to the chronoslice user. A restore or a command run as root can leave files owned by root. See Backups and restoring.
"there's no ChronoSlice database at …"
This comes from chronoslice update or chronoslice licence, which never make a new database. They use the service's settings from /etc/chronoslice/env. Run them with sudo, or pass --db.
A setting seems to be ignored
The chronoslice commands you run at a shell read /etc/chronoslice/env too, but a variable already set in your shell wins over the file, and so does a .env file in the folder you run the command from. Check env | grep CHRONOSLICE and the current folder. See Settings reference.
I can't sign in, or saving fails
"You don't have permission to do that." on every save
Sign-in works, but saving fails. Your reverse proxy is replacing the Host header. ChronoSlice refuses a change when the page's address and the Host header it receives don't match. In nginx, add proxy_set_header Host $http_host;. Caddy does this by default. See Reverse proxy and HTTPS.
Sign-in doesn't stick
If you set CHRONOSLICE_SECURE_COOKIES=true and open the site over plain http://, the browser throws the cookie away. Use the https:// address, or turn the setting off while you test.
"Too many failed attempts. Try again in 15 minutes."
After 10 failed sign-ins for one email in 15 minutes, ChronoSlice stops accepting attempts for that email until the 15 minutes pass.
I forgot my password
There's no reset email. Set a new password at the server, as the chronoslice user:
sudo -u chronoslice env CHRONOSLICE_DB=sqlite:///var/lib/chronoslice/chronoslice.db \
chronoslice user set-password [email protected]
The setup page asks for a token
The server has CHRONOSLICE_SETUP_TOKEN set. Enter its value. If you've lost it, look in /etc/chronoslice/env. See The first account.
Uploads fail
An attachment upload that fails with a "413" or "too large" error is being stopped by your proxy. In nginx, raise client_max_body_size to 11m. ChronoSlice's own limit is 10 MB per file.
Changes from another window show up late
The live updates stream is being held back by your proxy. In nginx, add proxy_buffering off; for the events path. See Reverse proxy and HTTPS.
The licence store can't be reached
"The store couldn't be reached (…)"
The full message reads The store couldn't be reached (…). Check this server can reach https://chronoslice.app, then try again. The server couldn't connect to the licence store. Check from the server:
curl -sI https://chronoslice.app | head -1
If that fails, look at the server's internet access, DNS and firewall rules. Outgoing HTTPS to chronoslice.app must be allowed.
Entering a key, Check now, and chronoslice update need the store. A failed daily check only writes a warning to the log, beginning licence check:, and the server carries on with what it last knew. Nothing stops working because the store was unreachable for a day.
"The store is busy. Try again in a minute."
The store is limiting how often you can ask. Wait a minute.
"The store's answer couldn't be verified"
The reply didn't match the signing keys built into your copy of ChronoSlice. Update ChronoSlice, then try again. See Updating.
"This key is already in use on another server"
The key's one seat is taken. See Moving to another server.
Email isn't sending
- Open Invoices, then Settings, and look at the Email card. It says either This server sends email or This server can't send email yet, and lists what's missing.
- Press Send test and read the result.
- Open Invoices, then Emails. It shows each email with its status and, for failures, the reason.
Common causes:
CHRONOSLICE_SMTP_URLandCHRONOSLICE_MAIL_FROMaren't both set, or you didn't restart the service after changing them.CHRONOSLICE_PUBLIC_URLisn't set. Invoice emails link to the invoice, and fail without it. Reminders aren't sent without it either.- The address is a
file://folder. That writes each email into the folder and sends nothing. - The plain
smtp://form sends without encryption, and many providers refuse it. Usesmtps://…:465, orsmtp://…:587?tls=required. - The username or password has special characters that aren't percent-encoded, such as
@or/. - The sender isn't allowed. Many providers only send from addresses on a domain you've verified.
- The client has no billing email. The invoice says
has no billing email. Add one on the client, or type an address. - Mail arrives in spam. Set up SPF and DKIM for the sending domain.
Reminders also need reminder days chosen, a Sent invoice with an address, and Send payment reminders left on for the client. See Reminders and notifications.
ChronoSlice is read-only
Open Settings, then Licence.
Trial ended, read-only. The 30-day trial is over and no key is entered. Enter your key. See Buying and entering a licence.- A key is entered, but the card says it licenses nothing. The reason is shown:
This key was revoked (refunded or replaced),This key is suspended,This key has expired, orThe store's answer about this key doesn't check out. Look at the key in your account at chronoslice.app/account/licenses. Press Check now to ask the store again. - You renewed or entered a key a moment ago, and it's still read-only. Press Check now, or run
sudo chronoslice licence check.
Everything stays viewable and exportable while the server is read-only. See The trial.
Someone can't be made active
The ChronoSlice trial allows up to 5 active users… or This server's … licence allows … active users means you're at your edition's user limit. Deactivate someone first, or upgrade. See People and roles.
An update didn't work
can't write to … ; run it as the user that owns the binary (sudo chronoslice update). Run it withsudo.not installing without --yes when there's nobody to ask. You ran it without a terminal. Add--yes.the download's SHA-256 is …, but the store said …; not installing it. The download was damaged. Nothing was changed. Run it again.Restarting chronoslice didn't work; restart it to run the new release.Runsudo systemctl restart chronosliceand read the log.- It says you're on the newest release. Your updates may have ended. See When updates end.
To go back, see Updating.
The Mac app won't sync
Look at the status at the bottom of the sidebar.
Offline. The app can't reach the server. Check that the server's address works in a browser, and that its certificate is valid. If it saysUse https for this server., you gave anhttp://address. The app accepts plain HTTP only for addresses on your own machine.Signed out — sign in again. The server stopped accepting this Mac's token, for example because it was revoked under Settings, then API tokens. Sign in again. Your local time is kept.Sync failed. Hover over the status for the reason. If it says the server answered with an error, check the server's log.reconnectingdoesn't go away. The live updates connection keeps dropping. Check that your proxy doesn't buffer or time out/api/orgs/{org}/events. See Reverse proxy and HTTPS. The app also retries waiting changes every minute.N refused. The server refused some changes. They're marked in the list with the reason, and Revert puts them back.- Nothing can be changed. The server is read-only. See When the server is read-only.
Press Sync Now in Settings, under Account, to try again straight away. See Working offline and sync.
Stripe
The webhook can't be set up
ChronoSlice can't set up the webhook without a public https:// address in CHRONOSLICE_PUBLIC_URL. Stripe won't send events to http:// or to localhost. Set it and restart. If the key can't manage webhooks, add the webhook by hand. See Getting paid with Stripe.
Still stuck?
Send a support request from the link at the bottom of any docs page. Include your ChronoSlice version, which Settings, then Licence, shows and chronoslice --version prints, and what you tried. The relevant lines from journalctl -u chronoslice help most.
Still stuck?
Send us a request: it goes to the people who build ChronoSlice, and the reply comes by email. Include your ChronoSlice version (Settings › Licence shows it) and what you tried.