Subscription json missing serverName in tlsSettings on External Proxy with Force TLS

[mhnrahmani]

Welcome

• [X] Yes, I'm using the latest major release. Only such installations are supported.
• [X] Yes, I'm using the supported system. Only such systems are supported.
• [X] Yes, I have read all WIKI document,nothing can help me in my problem.
• [X] Yes, I've searched similar issues on GitHub and didn't find any.
• [X] Yes, I've included all information below (version, config, log, etc).

Description of the problem,screencshot would be good

Describe the bug Generated json settings has empty tlsSettings when inbound comes with no TLS but External Proxy with Force TLS. Also tslSettings key comes with a typo in such setup (tslSettings instead of tlsSettings).

To Reproduce Steps to reproduce the behavior:

1. Create an inbound with WS transmission,
2. Add a Host header addressing real server behind cloudflare,
3. Add an external proxy with a cloudflare clean ip (e.g. zula.ir), and choose Force TLS on.
4. Do not turn on TLS. Let security be None and create the inbound.
5. Checkout the difference between the two settings created by the client QR code and the Subscription Json QR code, when scanned by v2rayNG.

Expected behavior If you scan the normal QR code generated for the above inbound's client, you will notice that the intended Host header (step 2) is repeated twice in the settings: once as the host header and once as SNI. However, the scanned Subscription Json will give different settings: In this Json, the "tlsSettings" key is miss-spelled as tslSettings, and it is empty meaning that no SNI is indicated.

Intended expectation is that the tlsSettings still comes with a "serverName" field with its value taken from the entered host header, just like how the normal client link is perceived by v2rayNG.

Version of 3x-ui

Desktop
 - OS: Ubuntu 22.04
 - Xray: 1.8.9
 - 3x-ui: 2.2.6

Smartphone
 - Device: Samsung
 - OS: Android
 - v2rayNG: 1.8.18

x-ui log reports or xray log

# paste log here