Language: English | Русский
Personal backup / survival archive of S-UI.
The original upstream repository alireza0/s-ui became unavailable for me and started returning 404 for the repository, releases, raw install script and the author profile. This repository is kept as a personal backup of a known working S-UI installation.
This is not an official S-UI repository.
https://github.com/FireTIA/S_UI_Backup
Archived working installation:
Panel: S-UI
Version S-UI: v1.4.1
Core: sing-box based
Backup date: 2026-05-11
Original install path: /usr/local/s-ui
Binary name: sui
Management command: s-ui
Systemd service: s-ui.service
Expected structure:
S_UI_Backup/
├── README.md
├── checksums.md5
├── checksums.hash
├── checksums.sha1
├── checksums.sha256
├── checksums.sha512
└── root/
└── s-ui-survival/
├── file-info.txt
├── s-ui-command
├── s-ui.service
├── s-ui.sh
├── sui.bin
├── s-ui-systemd-cat.txt
├── s-ui-status.txt
├── tree-lite.txt
└── s-ui-full-2026-05-11/
└── usr/
└── local/
└── s-ui/
├── db/
├── s-ui.service
├── s-ui.sh
└── sui
The db/ directory is intentionally kept without the real database.
Do not upload a real s-ui.db to a public GitHub repository.
A real S-UI database may contain:
- admin panel settings
- users
- UUIDs
- Reality keys
- subscription data
- domains
- ports
- traffic limits
- other sensitive server configuration
This public backup should not contain:
s-ui.db
s-ui.db-wal
s-ui.db-shm
*.sqlite
*.sqlite3
Recommended .gitignore:
*.db
*.db-wal
*.db-shm
*.sqlite
*.sqlite3
*.logClone the script and run it:
curl -sSL https://raw.githubusercontent.com/FireTIA/S_UI_Backup/refs/heads/main/first-install-S-UI.sh -o first-install-S-UI.sh && sudo bash first-install-S-UI.shTarget system: Ubuntu/Debian with systemd.
Install required tools:
sudo apt update
sudo apt install -y git sqlite3 ca-certificatesClone this repository:
git clone https://github.com/FireTIA/S_UI_Backup.git
cd S_UI_Backup/root/s-ui-survivalStop old S-UI service if it exists:
sudo systemctl stop s-ui 2>/dev/null || trueCreate install directories:
sudo mkdir -p /usr/local/s-ui/dbCopy S-UI files:
sudo cp -f sui.bin /usr/local/s-ui/sui
sudo cp -f s-ui.sh /usr/local/s-ui/s-ui.sh
sudo cp -f s-ui.service /usr/local/s-ui/s-ui.serviceFix permissions:
sudo chmod +x /usr/local/s-ui/sui
sudo chmod +x /usr/local/s-ui/s-ui.shInstall the systemd service:
sudo cp -f /usr/local/s-ui/s-ui.service /etc/systemd/system/s-ui.serviceInstall the s-ui management command:
sudo cp -f s-ui-command /usr/bin/s-ui
sudo chmod +x /usr/bin/s-uiReload systemd and start S-UI:
sudo systemctl daemon-reload
sudo systemctl enable --now s-uiCheck service status:
sudo systemctl status s-ui --no-pagerOpen the S-UI management menu:
sudo s-uiIf you prefer to restore from the archived directory tree instead of loose files:
cd S_UI_Backup/root/s-ui-survivalCopy the archived install tree:
sudo mkdir -p /usr/local/s-ui
sudo cp -a s-ui-full-2026-05-11/usr/local/s-ui/. /usr/local/s-ui/Fix permissions:
sudo chmod +x /usr/local/s-ui/sui
sudo chmod +x /usr/local/s-ui/s-ui.shInstall service and command:
sudo cp -f /usr/local/s-ui/s-ui.service /etc/systemd/system/s-ui.service
sudo cp -f s-ui-command /usr/bin/s-ui
sudo chmod +x /usr/bin/s-uiStart S-UI:
sudo systemctl daemon-reload
sudo systemctl enable --now s-ui
sudo s-uiOnly do this if you have your own private s-ui.db backup.
Do not use a database from an untrusted source.
Stop S-UI:
sudo systemctl stop s-uiRemove old database files:
sudo rm -f /usr/local/s-ui/db/s-ui.db
sudo rm -f /usr/local/s-ui/db/s-ui.db-wal
sudo rm -f /usr/local/s-ui/db/s-ui.db-shmCopy your private database:
sudo cp -f s-ui.db /usr/local/s-ui/db/s-ui.dbFix permissions:
sudo chown root:root /usr/local/s-ui/db/s-ui.db
sudo chmod 600 /usr/local/s-ui/db/s-ui.dbCheck SQLite integrity:
sudo sqlite3 /usr/local/s-ui/db/s-ui.db "PRAGMA integrity_check;"Start S-UI:
sudo systemctl start s-uiCheck status:
sudo systemctl status s-ui --no-pagerFrom the repository root:
cd S_UI_BackupCheck SHA256 sums:
sha256sum -c checksums.sha256Other checksum files are also included:
checksums.md5
checksums.sha1
checksums.sha512
checksums.hash
If your checksum tool uses different path formatting, manually compare the hashes for important files:
sha256sum root/s-ui-survival/sui.bin
sha256sum root/s-ui-survival/s-ui.sh
sha256sum root/s-ui-survival/s-ui.service
sha256sum root/s-ui-survival/s-ui-commandCheck S-UI service logs:
sudo journalctl -u s-ui -e --no-pagerFollow logs live:
sudo journalctl -u s-ui -fOpen the management menu:
sudo s-uiRestart S-UI:
sudo systemctl restart s-uiStop S-UI:
sudo systemctl stop s-uiStart S-UI:
sudo systemctl start s-uiCheck service state:
sudo systemctl status s-ui --no-pagerDo not use the built-in update option unless you know exactly where the update source points.
The original upstream disappeared for me, so the update function may fail or break the installation.
Recommended approach:
- keep this repository as an archive
- test restore on a separate VPS first
- do not overwrite a working production installation without a private backup
- keep real database backups private
- keep at least one offline copy of the original full backup
This repository is only an archival backup of a working S-UI installation.
It is not official, not maintained by the original author, and comes with no warranty.
Use at your own risk.
This repository contains backup files from the upstream S-UI project.
Upstream project: https://github.com/alireza0/s-ui
Original license: GNU General Public License v3.0
This repository is distributed under the GNU General Public License v3.0. See the LICENSE file for details.
This is an unofficial survival backup and is not affiliated with the original S-UI authors.