Skip to content

Operate NextChat

Keep access private, back up instance settings and export browser conversations separately. The root EBS volume and the browser store different data.

Service and logs

Check the service and inspect recent logs:

sudo systemctl status nextchat.service --no-pager
sudo journalctl -u nextchat.service --since '15 minutes ago' --no-pager

Restart the application after an approved configuration change:

sudo systemctl restart nextchat.service

Keep port 3000 on loopback and inbound rules closed. Restrict Session Manager to trusted operators. This is a shared instance access code, with no per-user server accounts or enterprise RBAC. The image does not add public HTTPS or a shared chat database. Review logs for sensitive content before sharing them.

Backups

Back up /etc/nextchat/instance.json, the private files in /home/ubuntu/.config/nextchat/ and any needed /home/ubuntu/nextchat-demo/ runs. Use encrypted storage and restrict backup readers; settings contain credentials. The root volume can be deleted when you terminate an instance.

Browser chats use IndexedDB with a localStorage fallback. Export them from NextChat before changing browser profiles, clearing site storage or moving workstations. An EBS snapshot does not back up these browser conversations. Remote chat synchronization is not configured by this image.

Access-code recovery

If only the Ubuntu access-code copy is missing and the persistent root configuration is intact, the setup service can restore that copy:

sudo systemctl restart sushi-nextchat-firstboot.service

If /etc/nextchat/instance.json is lost or damaged, restore your secure backup first. Do not delete it to regenerate access: it also contains your provider settings. Keep existing configuration and saved runs during diagnosis.

Updates and support

Use a reviewed replacement image for application updates and migrate your settings securely. Arbitrary container or dependency upgrades can change the managed configuration. Keep snapshots and browser exports before migration.

Contact Software Sushi with the package version, symptom and redacted service output. Never include keys, access codes or private conversations. Technical-support coverage requires a separate agreement; the software charge does not include upstream commercial support.

Last updated November 16, 2026 · Suggest an improvement