v1 Backend updated https://github.com/XMPlusDev/XMPlusv1

V1 Backend Update
- Updated to v2.16 with xray-core v1.8.19

Note: Append IPLimiit mapping to backend config.yml. Your must have a dedicated redis server and install redis client on backend servers. DOnot enable if you have no idea how to install redis

!!! Important:
Do not send me a message if you cannot clearly state and explain your issue.

eg. 1. Someone will just send a message "i have a problem". I do not know if he want me to beg him before he state the problem.
eg. 2. Someone will just send a message "i cannot connect after update".

I do not have supper powers to know what is causing your issue if you do not state:

- Panel version
- Backend version and confiig
- Panel network/security config
- Panel error (Enable debug)

If you do not clearly explain your issue i will ignore the message after reading it.

singbox sublink query parameter:

Panel v1 => ?singbox=1

Panel v2 => ?client=singbox

- 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