- Fixed singbox config issue when unsing tcp
- Added apln to security settings
- Added cdn_host network settings

Note:

When using cdn host as a host in app, panel netwoork host must be empty and set cdn host using cdn_host parameter.
If network host is filled, client host must be the same for server to verify else connection will decline.

*** cdn_host is valid for ws, h2, splithttp and httpupgrade only ***

Network settings

{
  "transport" : "ws",
  "acceptProxyProtocol": false,
  "host": "x.tld.com",
  "path": "/xmplus?ed=2560",
  "cdn_host": "www.cloudflare.com"
}

Security settings (append apln)

{
  "serverName": "x.tld.com",
  "rejectUnknownSni": false,
  "allowInsecure": true,
  "fingerprint": "chrome",
  "sni" : "google.com",
  "alpn": [
    "http/1.1",
    "h2"
  ]
}

Clash meta core supported app https://github.com/chen08209/FlClash

replace file in app\Http\Controllers\User to fix singbox sublink issue for v1

Panel Update v20240820
- Fixed minor issue

Backend Update

Panel v1 => v2.2.1

Panel v2 => v1.0.13


### Added xmplus commands

- Generate reality private and public keys
xmplus x25519

- Generate cloudflare warp account
xmplus warp


To use cloudflare warp with wireguard as outbound generate warp account and replace secretKey, publicKey and reserved

Wireguard domainStrategy:

"ForceIPv6v4" | "ForceIPv6" | "ForceIPv4v6" | "ForceIPv4" | "ForceIP"

config.yml

 RouteConfigPath:  /etc/XMPlus/route.json  
 OutboundConfigPath: /etc/XMPlus/outbound.json 

outbound.json

[
  {
    "protocol": "wireguard",
    "settings": {
        "secretKey": "xxxxxxxxxx",
        "address": [
            "172.16.0.2"
        ],
        "peers": [
            {
                "publicKey": "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=",
                "endpoint": "engage.cloudflareclient.com:2408",
                "allowedIPs": [
                    "0.0.0.0/0"
                ]
            }
        ],
        "reserved": [80, 53, 200],
        "mtu": 1280,
        "domainStrategy": "ForceIPv4"
    },
    "tag": "Warp"
  },    
  {
    "protocol": "blackhole",
    "tag": "block"
  }
]

route.json

{
  "domainStrategy": "IPOnDemand",
  "rules": [
    {
      "type": "field",
      "outboundTag": "block",
      "ip": [
        "geoip:private"
      ]
    },
    {
      "type": "field",
      "outboundTag": "block",
      "protocol": [
        "bittorrent"
      ]
    },
    {
      "type": "field",
      "outboundTag": "Warp",
      "network": "udp,tcp"
    }
  ]
}

fixed script issue. Run

xmplus update v2.2.1

to update backend for v1 only

Backend v1.0.15 with Xray-core v24.11.11 https://github.com/XMPlusDev/XMPlus

❗️Note that if you update your backend to latest version and your clients(apps) are using an older xray-core version, there is a possibility of having connection issues. You can always uninstall new backend and reinstall old backend from the github repo . https://github.com/XMPlusDev/XMPlusv1

if you are having this kind of view or pages, clear your /storage/smarty and clear your browser cookies. the template is not encoded since about last 3 or 4 updates so this should not happen. If you sill need the smarty_internal_resource_file.php file you can replace in

vendor/smarty/smarty/libs/sysplugins/smarty_internal_resource_file.php

If your online ips not showing after update(which show have updated onlineip database table) of v1,
run the sql to update online ip table manually.

Use this instead, missing AUTO_INCREMENT on id from older post causing only 1 record to save

DROP TABLE IF EXISTS `online_ip`;
CREATE TABLE IF NOT EXISTS `online_ip` (
  `id` bigint NOT NULL AUTO_INCREMENT,
  `serverid` int NOT NULL,
  `servername` text COLLATE utf8mb4_unicode_ci,
  `userid` int NOT NULL,
  `username` varchar(250) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `ip` varchar(100) COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `datetime` bigint NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

### Panel Update v20250103
- https://github.com/xcode75/XManagerPlus/releases/tag/v20250103

### Important Notice:
- Backend v1.1.0 (Xray-core v25.1.1) does not support panel version before v20250103
- Server port format can be 443, 443-443 or 442-450

* The second value for a port range cannot be smaller the the first. (eg, 443-442. this is invalid format)
* The port for the client is randomly selected if using a port range