Do not use an address that redirect for backend ApiHost else backend will not be able to update frontend online ip and used traffic.
Backend must respond with a status code 200 and no other.
For example , if you are redirecting main domain to an aliases using nginx, your backend host address must be the aliases address or vice versa.

VERY IMPORTANT NOTICE SO YOU DO NOT COME BACK ASKING SAME QUESTIONS: From the above image backend apihost must be https://www.xmplus.dev and not https://xmplus.dev since xmplus.dev will redirect to www.xmplus.dev

From now until 2023-12-31 23:59:59 you can enjoy 20% discount
with code: HAPPYHOLIDAYS
at https://authorization.xmplus.dev for all new purchase only.

sorry for been away for a while, had a serious situation to deal with. All is well now, I will check all messages and issue and provide solutions one by one. Please exercise patience since I have a lot of messages to read and reply. If you keep sending messages now i may reply to your message last since i am reading from bottom to top .Thanks🙏🏼

If there is any bug you have detected for v1 and v2 you can message me, will update in the coming week together with backend. Only bugs issue for now, please

v1 panel updated https://github.com/xcode75/XManagerPlus/releases/tag/v20240713

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"
    }
  ]
}