Where Does TUIC Store Its Config?
TUIC server reads a JSON config you pass with -c, conventionally kept at /etc/tuic/config.json Linux.
Last updated
TUIC configures through a JSON file given on the command line. Installers and Docker images conventionally settle on /etc/tuic/config.json, with the systemd unit pointing there. The file defines listen socket, users, certs and congestion control.
Keep certs beside the config or use absolute paths inside it. Relative paths break when the working directory differs between manual runs and systemd. One folder with config plus certs avoids that class of failure.
Where TUIC stores this, by platform
/etc/tuic/config.json (path passed with -c)
Server socket, users, certs and tuning in JSON. Systemd reads it from the unit file. Docker mounts host config to /etc/tuic. Keep cert paths absolute.
Frequently asked questions
How do I migrate a TUIC server?
Copy config.json plus the certificate and key to the same paths on the new host. Update the service file if paths change. Restart and watch logs for cert errors before opening the firewall.
Edits do nothing. Why?
Check the -c path in your systemd unit or Docker mount. The service reads exactly the file you point it at. A stale copy in another folder does nothing.
Notice an outdated path? Let us know.