Troubleshooting
Start with Settings › Health. Every minute, Solel checks the drives, space, backups and the services it runs on, and each check says what to do about anything that needs a look. Everyone can see it, and admins are told when something goes wrong.
The desktop won't open
Check the server is on and you're using the right address, then see When it won't start. If the desktop opens but an app is causing trouble, an admin can choose Restart in safe mode in Settings › Health, which starts Solel with every app off. See Health and safe mode.
You can't sign in
- "That username and password don't match": check both and try again. After five wrong tries, that username has to wait 15 minutes.
- Forgotten your password: the owner chooses Forgotten your password? and enters a recovery code. Anyone else asks an admin, who chooses their name in Settings › People, then Reset password….
- Lost your authenticator app or passkey: choose Use a backup code instead and enter one of your backup codes. Or ask an admin to choose Clear second steps… for you.
- A passkey stopped working: passkeys belong to your server's address, so if an admin changed it, sign in with your password and add a new passkey. The Linux desktop app can't use passkeys at all.
- "This invite doesn't work any more": it was used, ran out after a week or was taken back. Ask for a new one.
See Sign-in and security.
Space is running low
Settings › Storage shows what fills the drive. Under Make some room, it suggests what to clear: your Trash, models no Sol uses and old snapshots. See Storage and drive health.
A drive is failing
Solel asks each drive how it's doing every half hour, and tells admins as soon as one runs hot, wears out or starts to fail. If Settings › Storage says a drive is failing, copy what matters off the server now, then replace the drive. See Storage and drive health and Back up to another drive.
Private access won't connect
- Check Private access is on in Settings › Network.
- Check UDP port 51820 is forwarded on your router to the server.
- Check the tunnel is turned on in the WireGuard app.
- If an admin changed where devices connect, devices set up before still dial the old address. Remove yours in Settings › Phones and laptops and add it again.
- If Settings says Private access isn't running, the server was started without the tunnel. Admins see the command that turns it on; run it in /opt/solel as
sudo docker compose up -d caddy tunnel core.
See Reach home when you're out.
An update didn't go in
If a new version doesn't come up healthy, Solel puts the old one back by itself, and Settings › Updates says the last try didn't work. You can try again from there. See Updates.
Jethro isn't answering
On a new server, Jethro is ready once the AI model has downloaded, which can take a while. On the server, sudo docker compose logs -f models in /opt/solel shows the download.
If Settings › Models says the model didn't start, it may need more memory than the server has. Choose Restart to try again, or choose a smaller model. If it says The model runtime isn't running, see When it won't start.