*.suji.fr address.
This page covers running NocoDB on Suji end-to-end. NocoDB is maintained upstream; Suji provides the marketplace packaging.
Before you install
Nothing to prepare. NocoDB stores its data in a local database inside the install, and you’ll create your admin account in the browser on first run.NocoDB has no generated password and no credentials file — the first person to sign up becomes the super-admin. Create your account immediately after install.
Install
Dashboard → Apps → NocoDB → Install:| Field | Required | Notes |
|---|---|---|
| VM | yes | Pick a VM with free capacity, or create one. |
| Subdomain | no | Suggestion is nocodb. Reached at https://<subdomain>.suji.fr. |
| JWT secret | no | Auto-generated if left blank. Signs auth tokens — no need to set it. |
running in ~1 minute and is live at https://nocodb-<random>.suji.fr, served over HTTPS through the tunnel.
First connection — create your super-admin account
- Open the install URL (
https://nocodb-<random>.suji.fr). - NocoDB shows a Sign Up screen on first run.
- Enter your email and a password. The first account created is the super-admin.
- You land in the NocoDB dashboard.
Build your first base
Inside the dashboard:- Click Create Base (NocoDB’s term for a workspace/database).
- Add tables and columns, or import from CSV/Excel.
- Switch between Grid, Gallery, Kanban, and Form views.
- Invite collaborators from Team & Settings (email features depend on an SMTP provider — not configured by default).
Day-to-day management
| Want to… | Where |
|---|---|
| Build tables / views | The NocoDB dashboard (https://nocodb-<random>.suji.fr) |
| Manage users / API tokens | Dashboard → Team & Settings |
| View container logs | Dashboard → Logs (pick NocoDB) |
| Open a shell inside the container | Dashboard → Terminal (pick NocoDB) |
| Browse data on disk | Dashboard → Files (pick the NocoDB volume) |
| Restart the app | Install detail page → Restart |
| Upgrade to a newer version | Install detail page → Upgrade (when available) |
| Remove the install + its data | Install detail page → Uninstall |
Troubleshooting
Everyone logged out after a restart/upgrade
Everyone logged out after a restart/upgrade
Auth tokens are signed with the JWT secret. If it changed, existing sessions are invalidated and everyone has to sign in again — the data itself is untouched.
Invite / notification emails aren't sending
Invite / notification emails aren't sending
NocoDB needs an SMTP provider for outbound email, which isn’t configured by default. Note that the network blocks outbound SMTP on ports 25 and 465 — use port 587 or an HTTP-based provider. Add the SMTP env vars to the install yourself via Edit Install → environment variables, then redeploy.
Bad gateway (Cloudflare 502)
Bad gateway (Cloudflare 502)
NocoDB isn’t reachable through the tunnel yet — usually still starting (wait ~30 s, especially after an upgrade). If it persists, the Logs tab shows why the container isn’t up.
Where things live
| What | Inside container | Named volume |
|---|---|---|
| Metadata DB, attachments, app data | /usr/app/data | nocodb-data |
/usr/app/data — there’s no separate database container. Uninstalling deletes the volume by default; choose keep data during uninstall to preserve your bases.
Recommended size
- Small is plenty. NocoDB needs only ~512 MB and the compose caps it at 1 GB.
- Pressure scales with table size, attachments, and concurrent editors. Large bases or many users → size up.
- If you run other apps on the same VM, remember the VM’s total CPU/memory is shared.
Reporting issues
| Class | Where |
|---|---|
| NocoDB bug (views, formulas, import, API) | nocodb/nocodb issues |
| Marketplace packaging bug (compose / manifest / install form) | suji-hq/suji-templates issues |
| Suji platform bug (dashboard, billing, network) | Support ticket from the dashboard |