Getting started
Install Nevect
Install from the personalized commands in your account and complete the first login.
Prerequisites
Complete server preparation and open a root SSH session. Have access to your Nevect account. A new installation uses an empty installation directory; the installer refuses to overwrite an existing non-empty installation.
Copy the two commands
- Open My account and find Install on Ubuntu 22.04 or 24.04.
- Use Copy beside the first command. It downloads the installation script to your server.
- Paste it into the root shell and wait for a successful exit.
- Copy the second command directly from your account and run it. It contains an installation token associated with your account.
Treat the second command as a private credential. Do not publish it, put it in a shared ticket or copy another user's command. Copy each command once; do not join repeated display text.
Follow the installer
The installer downloads and verifies the selected release, prepares dependencies, starts services and checks their health. Read the actual terminal result before retrying. An interrupted command or a timeout does not establish whether installation completed.
Save the printed login URL, credentials and Tracker ID securely. The initial login entry is normally http://SERVER_IP/index; after authentication the interface uses /panel/. A configured custom login entry can replace the default.
Activate and verify
Open the printed URL, sign in, then bind and activate the installation. Confirm the Nevect version and license state. Finish domain configuration before using production campaign links.
Installation stopped
Keep the exact error and the last successful step. Check OS, architecture, root access, downloads, disk space and conflicting services. Do not delete the installation directory or run a fresh install over tracking data. Existing installations use the update workflow.
Verify each installation stage
| Stage | Expected result | If it differs |
|---|---|---|
| Download command | The script downloads successfully to the path in your account command | Check DNS, outbound HTTPS, free disk space and the exact terminal error |
| Personalized install command | Verification and service health checks finish successfully | Keep the final error; do not remove directories or bypass verification |
| First panel login | The printed login URL opens and accepts the issued credentials | Check your server’s address, firewall and configured login entry |
| Portal activation | Your Tracker ID appears in My bindings with an applied term | Follow the licensing guide; downloading software alone does not activate a term |
| Tracking domain | Generated links use the intended reachable domain | Configure DNS and HTTPS before sending campaign traffic |
The Nevect website account and the server panel are separate logins. A successful website sign-in does not establish that the server panel is healthy.
Retry without losing the useful evidence
If the shell disconnects, first check whether the original process is still running and save the latest terminal output. A browser timeout or lost SSH session alone does not tell you which installation stage completed. Use the exact error to distinguish a failed download, verification failure, port conflict and application health failure.
For a token-related rejection, sign in to your own website account and copy its current command again. Do not replace individual token bytes or copy a command from another account. When contacting support, redact the token and credentials, and include the OS, architecture, stage and error text.
After successful activation, continue with your first campaign and click and conversion verification.