ServeSense
Server Setup and Configuration
A sequential guide to configuring all parameters before running the server.
Step 1: Network, Root & Advanced Settings
This step configures the server's network binding, primary directory, and core security features.

A. Basic Settings
| Field | Description |
|---|---|
| Bind IP | The specific IP address the server listens on. Use 0.0.0.0 (the default) to listen on all available network interfaces. |
| Port | The network port for the selected protocol (SFTP default: 22; FTPS default: 990, FTP default: 21). |
| Root Folder | The mandatory base directory for all user accounts. All user home directories are contained within this folder. |
B. Advanced Settings
| Setting | Description |
|---|---|
| Logging | Toggle logging Enabled or Disabled. Disabling logging improves performance under high load (only available in Ultimate Plan). |
| Max upload (MB) | Sets the maximum allowed size (in Megabytes) for any single file upload. Set to 0 for unlimited size. |
| Brute Force Protection | Controls the anti-brute force mechanism. |
| Max tries before block | The number of failed login attempts allowed before blocking the connecting client. |
| Block duration (minutes) | The time (in minutes) the client is blocked after reaching the max tries limit. Set either to 0 to disable Brute Force Protection. |
| IP Whitelist | A comma-separated list of IP addresses or CIDR ranges. If set, only these addresses are allowed to connect. |
| IP Blacklist | A comma-separated list of IP addresses or CIDR ranges. Connections from these addresses will always be denied. |
| SSH Host Key | (SFTP only) Path to the SSH Host Key file (.key). If left blank or the file is missing, ServeSense will automatically generate a secure key (RSA and Ed25519). |
| FTPS Cert/Key | (FTPS only) Paths to the PEM certificate and key files. If left blank or files are missing, ServeSense will automatically generate self-signed certificate files. |
Step 2: Accounts
Configure user accounts, passwords, permissions, and virtual home directories.

Important
Username and Password fields must NOT contain the colon character (
:).| Field | Description |
|---|---|
| Username / Password | User login credentials. |
| Permissions | Granular access control for the account: |
| read | Allows downloading and listing files. |
| write | Allows uploading, creating directories (MKDIR), and renaming files. |
| delete | Allows deleting files (REMOVE) and directories (RMDIR). |
| list | Allows listing directory contents (LIST/STAT). |
| Home (subfolder) | The virtual root directory for the user. This path is relative to the Root Folder set in Step 1. |
🔑 Home (subfolder) Configuration Guide
| Input | Resulting Access/Path | Purpose |
|---|---|---|
| (Default/Empty) | A new folder is automatically created inside the Root Folder with the same name as the Username. | Standard setup for restricted access (Least Privilege). |
. (Single Dot) | The user gains access to the entire Root Folder set in Step 1. | Administrator/Super-admin access (accessing all user directories is possible). |
dirA/dirB | Creates a nested directory structure Root Folder\dirA\dirB as the user's home. | Defining a specific path for the user. |
Step 3: Run & Monitor
Start the server and observe the operational log.

- Click
Nextfrom Step 2. - Click the button to start the server. The button will change to .
- Server Log: View real-time status, connection info, and warnings/errors.
- Click to save the session log to a file for analysis.