Skip to content

X-NET v1.4.1

Choose a tag to compare

@xpanel-cp xpanel-cp released this 29 Sep 12:44
· 10 commits to main since this release

✨ New Features

SSH User Contact Information

  • Added two independent contact fields for each SSH account: Mobile Number and Telegram ID, separate from the username and notes.

  • Smart validation:

    • Mobile numbers accept digits only. Persian/Arabic numerals are automatically converted to English digits.
    • Telegram IDs accept English letters, numbers, and _.
    • The @ prefix can be entered but is automatically removed when saved.

Redesigned SSH User Create/Edit Form

  • The previous single long-form interface has been divided into four dedicated tabs:

    • Basic
    • Subscription
    • Contact Information
    • Advanced
  • When creating a new user, the form now uses a step-by-step Wizard flow.

  • The final Confirm & Deploy button is shown only on the last step.

  • When editing an existing user, all tabs remain freely accessible.

Start Subscription on First Connection — Now Available During Editing

  • The Start validity on first connection option, previously available only when creating an account, can now also be configured while editing accounts that have not yet been activated.
  • For accounts whose subscription has already started, the option is displayed as read-only to prevent data inconsistencies.

Automatic Post-Expiration Actions

Each SSH account can now have a specific action configured after its subscription expires:

  • No action
  • Notify administrator
  • Automatically disable
  • Notify + automatically disable

Additional options include a configurable delay after expiration:

  • Immediately
  • 1 day
  • 2 days
  • 3 days
  • 7 days
  • Custom delay

Notifications use the existing Telegram bot and the panel's existing system log.

Important: Automatically disabling expired accounts remains the panel's default behavior and does not depend on this setting. This feature adds an additional notification/action layer and does not replace the existing expiration enforcement.

SSH Lock to IP — New Feature

  • SSH accounts can now be locked to a specific IP address.

  • Connections from any other IP are detected at the server level and automatically terminated.

  • Supported protocols:

    • SSH TCP
    • Dropbear
    • WS
    • WS-TLS
  • A smart grace period and cooldown mechanism prevents a temporary reconnect from terminating a valid session or causing repeated disconnect/reconnect loops.

  • Known limitation: Due to the current architecture, which relies on external stunnel/dnstt components for SSH TLS and SlowDNS, this feature is currently unavailable for those two protocols because the panel does not have access to the client's real IP address on those paths.

  • This feature directly addresses user reports regarding the limitations of the previous IP Limit functionality.


🐛 Bug Fixes

Critical Panel Stability Fix

A critical stability issue has been completely fixed.

If the panel's Telegram bot was not configured or became unavailable, the panel could stop responding after a certain number of login/API requests (approximately 100 requests). This affected the entire panel, not just Telegram — including login and API requests — until the service was restarted.

This issue has been fully resolved.

Telegram availability or downtime can no longer block the panel's core functionality.

Fixed Subscription Renewal for Accounts Pending First Connection

Renewing an account that had not yet connected (the Pending state) could incorrectly start its subscription immediately.

This caused the reported issue where an account could effectively lose several days of its validity after being renewed.

The behavior is now corrected:

  • Renewal of a pending account only extends its pending period.
  • The subscription does not start prematurely.
  • Validity begins according to the account's configured first-connection behavior.

Fixed Expiration-State Inconsistency

In certain edge cases, an unrelated account edit — such as changing a note — could incorrectly reset the internal post-expiration action state.

This has been fixed and covered by automated tests to prevent regression.

Fully Fixed Allow Insecure Handling

Previously, the Allow Insecure option (skip SSL certificate verification) was applied only to share links.

It had no effect on:

  • sing-box JSON
  • Clash

As a result, there was no reliable way to disable certificate verification for those output formats.

This has now been fully corrected.

The behavior is consistent across all three output formats:

  • Share Links
  • sing-box JSON
  • Clash

The Allow Insecure setting can now be properly enabled or disabled across all supported outputs.

apt update
bash <(curl -fsSL https://raw.githubusercontent.com/xpanel-cp/x-net/main/install/xnet.sh)