Connect the Extension
Pointing the TabSlate extension at your self-hosted server instead of TabSlate Cloud.
Setting the server URL
The extension's login/register screen has an advanced, optional field for the server it talks to — see Settings & Shortcuts → Server URL. Leave it blank to use TabSlate Cloud; set it to your instance's HTTPS URL (the domain you pointed at Caddy, or your own reverse proxy) to use your self-hosted server instead.
The server URL isn't a display preference — the extension's session (access token, refresh token, and account) is tied to whichever server issued it. Changing the server URL after signing in points every future request, including sync, at a different backend with its own separate user database. It doesn't move your account or your synced data from one server to the other; you sign in (or register) against whichever server the field currently points at, as its own account.
Use a trusted TLS certificate
For any server you connect to remotely — not from the same machine — use a certificate from a certificate authority the browser already trusts, such as the one Caddy obtains automatically from Let's Encrypt in the documented deployment (see Docker Compose Deployment). A self-signed certificate, or none at all, either blocks the connection or forces you to work around the browser's own protections to make it succeed — neither is a safe way to run a server your account and data depend on.
Before you connect
Make sure the server is actually reachable and started correctly first — see Troubleshooting for the checks to run against your own instance before assuming the extension is the problem.
Last updated on