[Question]: Can`t connect to panel via https

[Ynetanaki]

What are you trying to do?

I installed 3x-ui and tryed connect to it with opera and tor browsers. I can't do it with error ERR_CONNECTION_TIMED_OUT. I login succesfully once and made first client but then I can't connect as client via v2rayng and then I can't connect to panel again

What have you already tried?

• Reinstall 3x-ui 3 or 4 times
• Read Question: HTTPS connection to panel is not working Question: HTTPS connection to panel is not working #3241
• Read [Bug]: VLESS + Reality TCP handshake drops after xray 26.6.1 update
  [Bug]: VLESS + Reality TCP handshake drops after xray 26.6.1 update #4980
• Used ss -tulnp | grep PORT
• Used journalctl -u x-ui -f --lines=100
• Disabled and enabled ufw (I connected once when it was disabled but then connection was lost and i cant connect second time)
• Change ufw rules: ufw allow 21438/tcp After that i still can't connect to panel with error in opera: ERR_SSL_PROTOCOL_ERROR and error in tor: SSL_ERROR_RX_RECORD_TOO_LONG
• Used iptables -L -n
• Also I tryed install 3x-ui pro by mozaroc from github (I used it last 6 months and it works good but one day I cant connect to my vpn by v2rayng and now I'm here). It's 3x-ui version was 2.9.8 and when I reinstall it I still can't connect to my panel with opera but can with tor. It's strange. The command I used to install it was bash <(wget -qO- https://github.com/mozaroc/x-ui-pro/raw/master/x-ui-pro.sh) -install yes -panel 1 -ONLY_CF_IP_ALLOW no

3x-ui version

3.2.6

How did you install 3x-ui?

With command bash <(curl -Ls https://raw.githubusercontent.com/mhsanaei/3x-ui/master/install.sh)

Operating system

Debian 12

Screenshots or config snippets

• Used ss -tulnp | grep 32675 and it wrote:
  tcp LISTEN 0 4096 *:32675 *:* users:(("x-ui",pid=47670,fd=10))
• Used journalctl -u x-ui -f --lines=100 and it wrote:

Jun 05 17:26:49 VM-105107 /usr/local/x-ui/x-ui[39644]: WARNING - XRAY: common/errors: The feature Trojan (with no Flow, etc.) is deprecated, not recommended for using and might be removed. Please migrate to VLESS with Flow & Seed as soon as possible.
Jun 05 17:26:49 VM-105107 /usr/local/x-ui/x-ui[39644]: ERROR - XRAY: Failed to start: app/proxyman/inbound: failed to listen TCP on 443 > transport/internet: failed to listen on address: 0.0.0.0:443 > transport/internet/tcp: failed to listen TCP on 0.0.0.0:443 > listen tcp 0.0.0.0:443: bind: address already in use
Jun 05 17:26:49 VM-105107 /usr/local/x-ui/x-ui[39644]: ERROR - Failure in running xray-core: exit status 255
Jun 05 17:26:49 VM-105107 x-ui[39644]: 2026/06/05 17:26:49 http: TLS handshake error from 127.0.0.1:27264: tls: first record does not look like a TLS handshake
Jun 05 17:26:50 VM-105107 x-ui[39644]: 2026/06/05 17:26:50 http: TLS handshake error from 94.253.102.102:43125: read tcp 163.5.16.253:8443->94.253.102.102:43125: read: connection timed out
Jun 05 17:26:51 VM-105107 /usr/local/x-ui/x-ui[39644]: INFO - XRAY: infra/conf/serial: Reading config: &{Name:bin/config.json Format:json}
Jun 05 17:26:51 VM-105107 /usr/local/x-ui/x-ui[39644]: WARNING - XRAY: common/errors: The feature WebSocket transport (with ALPN http/1.1, etc.) is deprecated, not recommended for using and might be removed. Please migrate to XHTTP H2 & H3 as soon as possible.
Jun 05 17:26:51 VM-105107 /usr/local/x-ui/x-ui[39644]: WARNING - XRAY: common/errors: The feature gRPC transport (with unnecessary costs, etc.) is deprecated, not recommended for using and might be removed. Please migrate to XHTTP stream-up H2 as soon as possible.
Jun 05 17:26:51 VM-105107 /usr/local/x-ui/x-ui[39644]: WARNING - XRAY: common/errors: The feature Trojan (with no Flow, etc.) is deprecated, not recommended for using and might be removed. Please migrate to VLESS with Flow & Seed as soon as possible.
Jun 05 17:26:51 VM-105107 /usr/local/x-ui/x-ui[39644]: ERROR - XRAY: Failed to start: app/proxyman/inbound: failed to listen TCP on 443 > transport/internet: failed to listen on address: 0.0.0.0:443 > transport/internet/tcp: failed to listen TCP on 0.0.0.0:443 > listen tcp 0.0.0.0:443: bind: address already in use
Jun 05 17:26:51 VM-105107 /usr/local/x-ui/x-ui[39644]: ERROR - Failure in running xray-core: exit status 255
Jun 05 17:26:53 VM-105107 /usr/local/x-ui/x-ui[39644]: INFO - XRAY: infra/conf/serial: Reading config: &{Name:bin/config.json Format:json}
Jun 05 17:26:53 VM-105107 /usr/local/x-ui/x-ui[39644]: WARNING - XRAY: common/errors: The feature WebSocket transport (with ALPN http/1.1, etc.) is deprecated, not recommended for using and might be removed. Please migrate to XHTTP H2 & H3 as soon as possible.
Jun 05 17:26:53 VM-105107 /usr/local/x-ui/x-ui[39644]: WARNING - XRAY: common/errors: The feature gRPC transport (with unnecessary costs, etc.) is deprecated, not recommended for using and might be removed. Please migrate to XHTTP stream-up H2 as soon as possible.
Jun 05 17:26:53 VM-105107 /usr/local/x-ui/x-ui[39644]: WARNING - XRAY: common/errors: The feature Trojan (with no Flow, etc.) is deprecated, not recommended for using and might be removed. Please migrate to VLESS with Flow & Seed as soon as possible.
Jun 05 17:26:53 VM-105107 /usr/local/x-ui/x-ui[39644]: ERROR - XRAY: Failed to start: app/proxyman/inbound: failed to listen TCP on 443 > transport/internet: failed to listen on address: 0.0.0.0:443 > transport/internet/tcp: failed to listen TCP on 0.0.0.0:443 > listen tcp 0.0.0.0:443: bind: address already in use
Jun 05 17:26:53 VM-105107 /usr/local/x-ui/x-ui[39644]: ERROR - Failure in running xray-core: exit status 255
Jun 05 17:26:55 VM-105107 /usr/local/x-ui/x-ui[39644]: INFO - XRAY: infra/conf/serial: Reading config: &{Name:bin/config.json Format:json}
Jun 05 17:26:55 VM-105107 /usr/local/x-ui/x-ui[39644]: WARNING - XRAY: common/errors: The feature WebSocket transport (with ALPN http/1.1, etc.) is deprecated, not recommended for using and might be removed. Please migrate to XHTTP H2 & H3 as soon as possible.
Jun 05 17:26:55 VM-105107 /usr/local/x-ui/x-ui[39644]: WARNING - XRAY: common/errors: The feature gRPC transport (with unnecessary costs, etc.) is deprecated, not recommended for using and might be removed. Please migrate to XHTTP stream-up H2 as soon as possible.
Jun 05 17:26:55 VM-105107 /usr/local/x-ui/x-ui[39644]: WARNING - XRAY: common/errors: The feature Trojan (with no Flow, etc.) is deprecated, not recommended for using and might be removed. Please migrate to VLESS with Flow & Seed as soon as possible.
Jun 05 17:26:55 VM-105107 /usr/local/x-ui/x-ui[39644]: ERROR - XRAY: Failed to start: app/proxyman/inbound: failed to listen TCP on 443 > transport/internet: failed to listen on address: 0.0.0.0:443 > transport/internet/tcp: failed to listen TCP on 0.0.0.0:443 > listen tcp 0.0.0.0:443: bind: address already in use
Jun 05 17:26:55 VM-105107 /usr/local/x-ui/x-ui[39644]: ERROR - Failure in running xray-core: exit status 255
Jun 05 17:26:55 VM-105107 x-ui[39644]: 2026/06/05 17:26:55 http: TLS handshake error from 94.253.102.102:60938: read tcp 163.5.16.253:8443->94.253.102.102:60938: use of closed network connection
Jun 05 17:26:55 VM-105107 /usr/local/x-ui/x-ui[39644]: INFO - WebSocket hub stopped
Jun 05 17:26:55 VM-105107 x-ui[39644]: 2026/06/05 17:26:55 http: TLS handshake error from 94.253.102.102:19313: read tcp 163.5.16.253:8443->94.253.102.102:19313: use of closed network connection
Jun 05 17:26:55 VM-105107 x-ui[39644]: 2026/06/05 17:26:55 http: TLS handshake error from 94.253.102.102:13117: read tcp 163.5.16.253:8443->94.253.102.102:13117: use of closed network connection
Jun 05 17:26:55 VM-105107 x-ui[39644]: 2026/06/05 17:26:55 http: TLS handshake error from 94.253.102.102:40372: read tcp 163.5.16.253:8443->94.253.102.102:40372: use of closed network connection
Jun 05 17:26:55 VM-105107 x-ui[39644]: 2026/06/05 17:26:55 http: TLS handshake error from 94.253.102.102:50346: read tcp 163.5.16.253:8443->94.253.102.102:50346: use of closed network connection
Jun 05 17:26:55 VM-105107 x-ui[39644]: 2026/06/05 17:26:55 http: TLS handshake error from 94.253.102.102:1265: read tcp 163.5.16.253:8443->94.253.102.102:1265: use of closed network connection
Jun 05 17:26:55 VM-105107 x-ui[39644]: 2026/06/05 17:26:55 http: TLS handshake error from 94.253.102.102:22367: read tcp 163.5.16.253:8443->94.253.102.102:22367: use of closed network connection
Jun 05 17:26:55 VM-105107 x-ui[39644]: 2026/06/05 17:26:55 http: TLS handshake error from 94.253.102.102:1224: read tcp 163.5.16.253:8443->94.253.102.102:1224: use of closed network connection
Jun 05 17:26:55 VM-105107 x-ui[39644]: 2026/06/05 17:26:55 http: TLS handshake error from 94.253.102.102:50338: read tcp 163.5.16.253:8443->94.253.102.102:50338: use of closed network connection
Jun 05 17:26:55 VM-105107 x-ui[39644]: 2026/06/05 17:26:55 http: TLS handshake error from 94.253.102.102:60983: read tcp 163.5.16.253:8443->94.253.102.102:60983: use of closed network connection
Jun 05 17:26:55 VM-105107 x-ui[39644]: 2026/06/05 17:26:55 http: TLS handshake error from 94.253.102.102:46984: read tcp 163.5.16.253:8443->94.253.102.102:46984: use of closed network connection
Jun 05 17:26:55 VM-105107 x-ui[39644]: 2026/06/05 17:26:55 http: TLS handshake error from 94.253.102.102:8791: read tcp 163.5.16.253:8443->94.253.102.102:8791: use of closed network connection
Jun 05 17:26:55 VM-105107 x-ui[39644]: 2026/06/05 17:26:55 http: TLS handshake error from 94.253.102.102:13108: read tcp 163.5.16.253:8443->94.253.102.102:13108: use of closed network connection
Jun 05 17:26:55 VM-105107 x-ui[39644]: 2026/06/05 17:26:55 http: TLS handshake error from 94.253.102.102:8824: read tcp 163.5.16.253:8443->94.253.102.102:8824: use of closed network connection
Jun 05 17:26:55 VM-105107 x-ui[39644]: 2026/06/05 17:26:55 http: TLS handshake error from 94.253.102.102:50366: read tcp 163.5.16.253:8443->94.253.102.102:50366: use of closed network connection
Jun 05 17:26:55 VM-105107 x-ui[39644]: 2026/06/05 17:26:55 http: TLS handshake error from 94.253.102.102:29887: read tcp 163.5.16.253:8443->94.253.102.102:29887: use of closed network connection
Jun 05 17:26:55 VM-105107 x-ui[39644]: 2026/06/05 17:26:55 Shutting down servers.
Jun 05 17:26:55 VM-105107 systemd[1]: Stopping x-ui.service - x-ui Service...
Jun 05 17:26:55 VM-105107 systemd[1]: x-ui.service: Deactivated successfully.
Jun 05 17:26:55 VM-105107 systemd[1]: Stopped x-ui.service - x-ui Service.
Jun 05 17:26:55 VM-105107 systemd[1]: x-ui.service: Consumed 16.286s CPU time.
Jun 05 17:29:03 VM-105107 systemd[1]: Started x-ui.service - x-ui Service.
Jun 05 17:29:03 VM-105107 x-ui[43319]: 2026/06/05 17:29:03 Starting x-ui 2.9.4
Jun 05 17:29:03 VM-105107 systemd[1]: Stopping x-ui.service - x-ui Service...
Jun 05 17:29:03 VM-105107 systemd[1]: x-ui.service: Deactivated successfully.
Jun 05 17:29:03 VM-105107 systemd[1]: Stopped x-ui.service - x-ui Service.
Jun 05 17:29:07 VM-105107 systemd[1]: Started x-ui.service - x-ui Service.
Jun 05 17:29:07 VM-105107 x-ui[43416]: 2026/06/05 17:29:07 Starting x-ui 2.9.4
Jun 05 17:29:07 VM-105107 /usr/local/x-ui/x-ui[43416]: INFO - Web server running HTTPS on [::]:21438
Jun 05 17:29:07 VM-105107 /usr/local/x-ui/x-ui[43416]: INFO - custom geo startup: no custom geofiles configured
Jun 05 17:29:07 VM-105107 /usr/local/x-ui/x-ui[43416]: INFO - Sub server running HTTPS on [::]:53152
Jun 05 17:29:07 VM-105107 /usr/local/x-ui/x-ui[43416]: INFO - XRAY: infra/conf/serial: Reading config: &{Name:bin/config.json Format:json}
Jun 05 17:29:07 VM-105107 /usr/local/x-ui/x-ui[43416]: WARNING - XRAY: infra/conf: REALITY: Listening on non-443 ports may get your IP blocked by the GFW
Jun 05 17:29:07 VM-105107 /usr/local/x-ui/x-ui[43416]: WARNING - XRAY: common/errors: The feature WebSocket transport (with ALPN http/1.1, etc.) is deprecated, not recommended for using and might be removed. Please migrate to XHTTP H2 & H3 as soon as possible.
Jun 05 17:29:07 VM-105107 /usr/local/x-ui/x-ui[43416]: WARNING - XRAY: common/errors: The feature gRPC transport (with unnecessary costs, etc.) is deprecated, not recommended for using and might be removed. Please migrate to XHTTP stream-up H2 as soon as possible.
Jun 05 17:29:07 VM-105107 /usr/local/x-ui/x-ui[43416]: WARNING - XRAY: common/errors: The feature Trojan (with no Flow, etc.) is deprecated, not recommended for using and might be removed. Please migrate to VLESS with Flow & Seed as soon as possible.
Jun 05 17:29:07 VM-105107 /usr/local/x-ui/x-ui[43416]: WARNING - XRAY: transport/internet/tcp: accepting PROXY protocol
Jun 05 17:29:07 VM-105107 /usr/local/x-ui/x-ui[43416]: WARNING - XRAY: core: Xray 26.4.25 started
Jun 05 17:29:09 VM-105107 x-ui[43416]: 2026/06/05 17:29:09 Shutting down servers.
Jun 05 17:29:09 VM-105107 /usr/local/x-ui/x-ui[43416]: INFO - WebSocket hub stopped
Jun 05 17:29:09 VM-105107 systemd[1]: Stopping x-ui.service - x-ui Service...
Jun 05 17:29:09 VM-105107 systemd[1]: x-ui.service: Deactivated successfully.
Jun 05 17:29:09 VM-105107 systemd[1]: Stopped x-ui.service - x-ui Service.
Jun 05 17:29:09 VM-105107 systemd[1]: Started x-ui.service - x-ui Service.
Jun 05 17:29:09 VM-105107 x-ui[43460]: 2026/06/05 17:29:09 Starting x-ui 2.9.4
Jun 05 17:29:09 VM-105107 /usr/local/x-ui/x-ui[43460]: INFO - Web server running HTTPS on [::]:21438
Jun 05 17:29:09 VM-105107 /usr/local/x-ui/x-ui[43460]: INFO - custom geo startup: no custom geofiles configured
Jun 05 17:29:09 VM-105107 /usr/local/x-ui/x-ui[43460]: INFO - Sub server running HTTPS on [::]:53152
Jun 05 17:29:09 VM-105107 /usr/local/x-ui/x-ui[43460]: INFO - XRAY: infra/conf/serial: Reading config: &{Name:bin/config.json Format:json}
Jun 05 17:29:09 VM-105107 /usr/local/x-ui/x-ui[43460]: WARNING - XRAY: infra/conf: REALITY: Listening on non-443 ports may get your IP blocked by the GFW
Jun 05 17:29:09 VM-105107 /usr/local/x-ui/x-ui[43460]: WARNING - XRAY: common/errors: The feature WebSocket transport (with ALPN http/1.1, etc.) is deprecated, not recommended for using and might be removed. Please migrate to XHTTP H2 & H3 as soon as possible.
Jun 05 17:29:09 VM-105107 /usr/local/x-ui/x-ui[43460]: WARNING - XRAY: common/errors: The feature gRPC transport (with unnecessary costs, etc.) is deprecated, not recommended for using and might be removed. Please migrate to XHTTP stream-up H2 as soon as possible.
Jun 05 17:29:09 VM-105107 /usr/local/x-ui/x-ui[43460]: WARNING - XRAY: common/errors: The feature Trojan (with no Flow, etc.) is deprecated, not recommended for using and might be removed. Please migrate to VLESS with Flow & Seed as soon as possible.
Jun 05 17:29:09 VM-105107 /usr/local/x-ui/x-ui[43460]: WARNING - XRAY: transport/internet/tcp: accepting PROXY protocol
Jun 05 17:29:09 VM-105107 /usr/local/x-ui/x-ui[43460]: WARNING - XRAY: core: Xray 26.4.25 started
Jun 05 17:30:08 VM-105107 /usr/local/x-ui/x-ui[43460]: INFO - R5POmPy0Ho logged in successfully, Ip Address: 127.0.0.1
Jun 05 17:30:08 VM-105107 /usr/local/x-ui/x-ui[43460]: INFO - R5POmPy0Ho logged in successfully
Jun 05 17:32:39 VM-105107 /usr/local/x-ui/x-ui[43460]: INFO - XRAY: infra/conf/serial: Reading config: &{Name:bin/config.json Format:json}
Jun 05 17:32:39 VM-105107 /usr/local/x-ui/x-ui[43460]: WARNING - XRAY: infra/conf: REALITY: Listening on non-443 ports may get your IP blocked by the GFW
Jun 05 17:32:39 VM-105107 /usr/local/x-ui/x-ui[43460]: WARNING - XRAY: common/errors: The feature WebSocket transport (with ALPN http/1.1, etc.) is deprecated, not recommended for using and might be removed. Please migrate to XHTTP H2 & H3 as soon as possible.

• Change ufw rules: ufw allow 21438/tcp After that i still can't connect to panel with error in opera: ERR_SSL_PROTOCOL_ERROR and error in tor: SSL_ERROR_RX_RECORD_TOO_LONG
• Used iptables -L -n it wrote:

Chain INPUT (policy DROP)
target     prot opt source               destination         
ufw-before-logging-input  0    --  0.0.0.0/0            0.0.0.0/0           
ufw-before-input  0    --  0.0.0.0/0            0.0.0.0/0           
ufw-after-input  0    --  0.0.0.0/0            0.0.0.0/0           
ufw-after-logging-input  0    --  0.0.0.0/0            0.0.0.0/0           
ufw-reject-input  0    --  0.0.0.0/0            0.0.0.0/0           
ufw-track-input  0    --  0.0.0.0/0            0.0.0.0/0           
DROP       1    --  0.0.0.0/0            0.0.0.0/0            icmptype 8

Chain FORWARD (policy DROP)
target     prot opt source               destination         
DOCKER-USER  0    --  0.0.0.0/0            0.0.0.0/0           
DOCKER-ISOLATION-STAGE-1  0    --  0.0.0.0/0            0.0.0.0/0           
ACCEPT     0    --  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED
DOCKER     0    --  0.0.0.0/0            0.0.0.0/0           
ACCEPT     0    --  0.0.0.0/0            0.0.0.0/0           
ACCEPT     0    --  0.0.0.0/0            0.0.0.0/0           
ACCEPT     0    --  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED
DOCKER     0    --  0.0.0.0/0            0.0.0.0/0           
ACCEPT     0    --  0.0.0.0/0            0.0.0.0/0           
ACCEPT     0    --  0.0.0.0/0            0.0.0.0/0           
ufw-before-logging-forward  0    --  0.0.0.0/0            0.0.0.0/0           
ufw-before-forward  0    --  0.0.0.0/0            0.0.0.0/0           
ufw-after-forward  0    --  0.0.0.0/0            0.0.0.0/0           
ufw-after-logging-forward  0    --  0.0.0.0/0            0.0.0.0/0           
ufw-reject-forward  0    --  0.0.0.0/0            0.0.0.0/0           
ufw-track-forward  0    --  0.0.0.0/0            0.0.0.0/0           

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         
ufw-before-logging-output  0    --  0.0.0.0/0            0.0.0.0/0           
ufw-before-output  0    --  0.0.0.0/0            0.0.0.0/0           
ufw-after-output  0    --  0.0.0.0/0            0.0.0.0/0           
ufw-after-logging-output  0    --  0.0.0.0/0            0.0.0.0/0           
ufw-reject-output  0    --  0.0.0.0/0            0.0.0.0/0           
ufw-track-output  0    --  0.0.0.0/0            0.0.0.0/0           

Chain DOCKER (2 references)
target     prot opt source               destination         
ACCEPT     17   --  0.0.0.0/0            172.29.172.2         udp dpt:40452
ACCEPT     17   --  0.0.0.0/0            172.29.172.3         udp dpt:4500
ACCEPT     17   --  0.0.0.0/0            172.29.172.3         udp dpt:500

Chain DOCKER-ISOLATION-STAGE-1 (1 references)
target     prot opt source               destination         
DOCKER-ISOLATION-STAGE-2  0    --  0.0.0.0/0            0.0.0.0/0           
DOCKER-ISOLATION-STAGE-2  0    --  0.0.0.0/0            0.0.0.0/0           
RETURN     0    --  0.0.0.0/0            0.0.0.0/0           

Chain DOCKER-ISOLATION-STAGE-2 (2 references)
target     prot opt source               destination         
DROP       0    --  0.0.0.0/0            0.0.0.0/0           
DROP       0    --  0.0.0.0/0            0.0.0.0/0           
RETURN     0    --  0.0.0.0/0            0.0.0.0/0           

Chain DOCKER-USER (1 references)
target     prot opt source               destination         
RETURN     0    --  0.0.0.0/0            0.0.0.0/0           

Chain ufw-after-forward (1 references)
target     prot opt source               destination         

Chain ufw-after-input (1 references)
target     prot opt source               destination         
ufw-skip-to-policy-input  17   --  0.0.0.0/0            0.0.0.0/0            udp dpt:137
ufw-skip-to-policy-input  17   --  0.0.0.0/0            0.0.0.0/0            udp dpt:138
ufw-skip-to-policy-input  6    --  0.0.0.0/0            0.0.0.0/0            tcp dpt:139
ufw-skip-to-policy-input  6    --  0.0.0.0/0            0.0.0.0/0            tcp dpt:445
ufw-skip-to-policy-input  17   --  0.0.0.0/0            0.0.0.0/0            udp dpt:67
ufw-skip-to-policy-input  17   --  0.0.0.0/0            0.0.0.0/0            udp dpt:68
ufw-skip-to-policy-input  0    --  0.0.0.0/0            0.0.0.0/0            ADDRTYPE match dst-type BROADCAST

Chain ufw-after-logging-forward (1 references)
target     prot opt source               destination         
LOG        0    --  0.0.0.0/0            0.0.0.0/0            limit: avg 3/min burst 10 LOG flags 0 level 4 prefix "[UFW BLOCK] "

Chain ufw-after-logging-input (1 references)
target     prot opt source               destination         
LOG        0    --  0.0.0.0/0            0.0.0.0/0            limit: avg 3/min burst 10 LOG flags 0 level 4 prefix "[UFW BLOCK] "

Chain ufw-after-logging-output (1 references)
target     prot opt source               destination         

Chain ufw-after-output (1 references)
target     prot opt source               destination         

Chain ufw-before-forward (1 references)
target     prot opt source               destination         
ACCEPT     0    --  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED
ACCEPT     1    --  0.0.0.0/0            0.0.0.0/0            icmptype 3
ACCEPT     1    --  0.0.0.0/0            0.0.0.0/0            icmptype 11
ACCEPT     1    --  0.0.0.0/0            0.0.0.0/0            icmptype 12
ACCEPT     1    --  0.0.0.0/0            0.0.0.0/0            icmptype 8
ufw-user-forward  0    --  0.0.0.0/0            0.0.0.0/0           

Chain ufw-before-input (1 references)
target     prot opt source               destination         
ACCEPT     0    --  0.0.0.0/0            0.0.0.0/0           
ACCEPT     0    --  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED
ufw-logging-deny  0    --  0.0.0.0/0            0.0.0.0/0            ctstate INVALID
DROP       0    --  0.0.0.0/0            0.0.0.0/0            ctstate INVALID
ACCEPT     1    --  0.0.0.0/0            0.0.0.0/0            icmptype 3
ACCEPT     1    --  0.0.0.0/0            0.0.0.0/0            icmptype 11
ACCEPT     1    --  0.0.0.0/0            0.0.0.0/0            icmptype 12
ACCEPT     1    --  0.0.0.0/0            0.0.0.0/0            icmptype 8
ACCEPT     17   --  0.0.0.0/0            0.0.0.0/0            udp spt:67 dpt:68
ufw-not-local  0    --  0.0.0.0/0            0.0.0.0/0           
ACCEPT     17   --  0.0.0.0/0            224.0.0.251          udp dpt:5353
ACCEPT     17   --  0.0.0.0/0            239.255.255.250      udp dpt:1900
ufw-user-input  0    --  0.0.0.0/0            0.0.0.0/0           

Chain ufw-before-logging-forward (1 references)
target     prot opt source               destination         

Chain ufw-before-logging-input (1 references)
target     prot opt source               destination         

Chain ufw-before-logging-output (1 references)
target     prot opt source               destination         

Chain ufw-before-output (1 references)
target     prot opt source               destination         
ACCEPT     0    --  0.0.0.0/0            0.0.0.0/0           
ACCEPT     0    --  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED
ufw-user-output  0    --  0.0.0.0/0            0.0.0.0/0           

Chain ufw-logging-allow (0 references)
target     prot opt source               destination         
LOG        0    --  0.0.0.0/0            0.0.0.0/0            limit: avg 3/min burst 10 LOG flags 0 level 4 prefix "[UFW ALLOW] "

Chain ufw-logging-deny (2 references)
target     prot opt source               destination         
RETURN     0    --  0.0.0.0/0            0.0.0.0/0            ctstate INVALID limit: avg 3/min burst 10
LOG        0    --  0.0.0.0/0            0.0.0.0/0            limit: avg 3/min burst 10 LOG flags 0 level 4 prefix "[UFW BLOCK] "

Chain ufw-not-local (1 references)
target     prot opt source               destination         
RETURN     0    --  0.0.0.0/0            0.0.0.0/0            ADDRTYPE match dst-type LOCAL
RETURN     0    --  0.0.0.0/0            0.0.0.0/0            ADDRTYPE match dst-type MULTICAST
RETURN     0    --  0.0.0.0/0            0.0.0.0/0            ADDRTYPE match dst-type BROADCAST
ufw-logging-deny  0    --  0.0.0.0/0            0.0.0.0/0            limit: avg 3/min burst 10
DROP       0    --  0.0.0.0/0            0.0.0.0/0           

Chain ufw-reject-forward (1 references)
target     prot opt source               destination         

Chain ufw-reject-input (1 references)
target     prot opt source               destination         

Chain ufw-reject-output (1 references)
target     prot opt source               destination         

Chain ufw-skip-to-policy-forward (0 references)
target     prot opt source               destination         
DROP       0    --  0.0.0.0/0            0.0.0.0/0           

Chain ufw-skip-to-policy-input (7 references)
target     prot opt source               destination         
DROP       0    --  0.0.0.0/0            0.0.0.0/0           

Chain ufw-skip-to-policy-output (0 references)
target     prot opt source               destination         
ACCEPT     0    --  0.0.0.0/0            0.0.0.0/0           

Chain ufw-track-forward (1 references)
target     prot opt source               destination         

Chain ufw-track-input (1 references)
target     prot opt source               destination         

Chain ufw-track-output (1 references)
target     prot opt source               destination         
ACCEPT     6    --  0.0.0.0/0            0.0.0.0/0            ctstate NEW
ACCEPT     17   --  0.0.0.0/0            0.0.0.0/0            ctstate NEW

Chain ufw-user-forward (1 references)
target     prot opt source               destination         

Chain ufw-user-input (1 references)
target     prot opt source               destination         
ACCEPT     6    --  0.0.0.0/0            0.0.0.0/0            tcp dpt:80
ACCEPT     6    --  0.0.0.0/0            0.0.0.0/0            tcp dpt:443
ACCEPT     17   --  0.0.0.0/0            0.0.0.0/0            udp dpt:443
ACCEPT     6    --  0.0.0.0/0            0.0.0.0/0            tcp dpt:22
ACCEPT     6    --  0.0.0.0/0            0.0.0.0/0            tcp dpt:443
ACCEPT     6    --  0.0.0.0/0            0.0.0.0/0            tcp dpt:21438
ACCEPT     6    --  0.0.0.0/0            0.0.0.0/0            tcp dpt:32675

Chain ufw-user-limit (0 references)
target     prot opt source               destination         
LOG        0    --  0.0.0.0/0            0.0.0.0/0            limit: avg 3/min burst 5 LOG flags 0 level 4 prefix "[UFW LIMIT BLOCK] "
REJECT     0    --  0.0.0.0/0            0.0.0.0/0            reject-with icmp-port-unreachable

Chain ufw-user-limit-accept (0 references)
target     prot opt source               destination         
ACCEPT     0    --  0.0.0.0/0            0.0.0.0/0           

Chain ufw-user-logging-forward (0 references)
target     prot opt source               destination         

Chain ufw-user-logging-input (0 references)
target     prot opt source               destination         

Chain ufw-user-logging-output (0 references)
target     prot opt source               destination         

Chain ufw-user-output (1 references)
target     prot opt source               destination  

Before submitting

• I read the Wiki and searched existing issues.
• This is a usage question, not a bug report.
• This question is written in English.

[Ynetanaki]

I forgot wrote that I`m from Russia. I know about DPI bans, but 3x-ui works normally for 6 months and everything was ok....

[github-actions]

Your logs make the problems quite clear — there are two separate issues stacked on top of each other.

---

Issue 1 — Port 443 is already in use (blocks all Xray clients)

Every few seconds the logs show:

ERROR - XRAY: Failed to start: ... listen tcp 0.0.0.0:443: bind: address already in use
ERROR - Failure in running xray-core: exit status 255

Xray has an inbound configured on port 443, but something else on the server has already bound that port. Until this is resolved, none of your VPN clients can connect because Xray never starts successfully.

Find the conflicting process:

ss -tulnp | grep ':443'

Common culprits: nginx, apache2, caddy, another x-ui instance, or the mozaroc/x-ui-pro installation you mentioned. Once identified, either stop/remove that service or change your Xray inbound to a different port inside the 3x-ui panel.

---

Issue 2 — Two conflicting x-ui installations

Your logs show:

Starting x-ui 2.9.4

But you stated the installed version is 3.2.6 (official). The systemd unit at /usr/local/x-ui/x-ui is still pointing to the mozaroc 2.9.4 fork binary, not the official 3x-ui. Running two installations side-by-side means they share the same database (/etc/x-ui/x-ui.db) and systemd service name, causing conflicts.

Check which binary is actually running:

/usr/local/x-ui/x-ui --version
systemctl cat x-ui | grep ExecStart

To cleanly reinstall the official version and overwrite the fork:

bash <(curl -Ls https://raw.githubusercontent.com/mhsanaei/3x-ui/master/install.sh)

---

Issue 3 — ERR_SSL_PROTOCOL_ERROR / SSL_ERROR_RX_RECORD_TOO_LONG on the panel

The panel is running HTTPS on port 21438 (confirmed: INFO - Web server running HTTPS on [::]:21438), and you did log in successfully from localhost at 17:30:08. The SSL errors from your browser most likely have one of these causes:

1. You are typing http:// instead of https:// — the panel only speaks HTTPS once a certificate is configured. Make sure your URL is https://<server-ip>:21438/<basepath>.

2. Self-signed certificate — if the certificate stored in the panel settings is self-signed, browsers will refuse to connect with these exact errors. You must either:

   • Accept the certificate warning by clicking "Advanced → Proceed" in your browser, or
   • Replace it with a valid certificate (e.g. from Let's Encrypt via the x-ui management menu → SSL Certificate).

3. Your IP may be blocked by Fail2ban — the logs show dozens of failed TLS handshake attempts from your external IP (94.253.102.102) during the crash loop. Fail2ban (enabled by default via XUI_ENABLE_FAIL2BAN=true) may have banned your IP. To unban:

   x-ui
   # → IP Limit menu → option 3: Unban Everyone

   Or directly:

   fail2ban-client reload --restart --unban 3x-ipl

---

Recommended fix order

1. ss -tulnp | grep ':443' → identify and stop the process holding port 443
2. Reinstall official 3x-ui to clear the mozaroc fork conflict
3. systemctl restart x-ui → confirm Xray starts without the port 443 error
4. Connect to the panel with https:// and accept/replace the cert if needed
5. Unban your IP via the x-ui management menu if still blocked

[Ynetanaki]

Yes, it works! I can connect to panel. But now I have another problem, I can't use it. I made first client (vless reality) but when I tryed start use it as a client it has -1 ping. Panel shows that I'm online and has traffic. It's server logs, and yes there anoter error. Unfortunately, I didn't find the IP limit menu and when I tried use om my server this command fail2ban-client reload --restart --unban 3x-ipl it says that file or directory not found and than I used x-ui banlog it says that fail2ban service is not running, but I didn't disable it. Thank you so much
Server logs:

Jun 05 21:20:05 VM-999436 systemd[1]: Started x-ui.service - x-ui Service.
Jun 05 21:20:05 VM-999436 x-ui[16458]: 2026/06/05 21:20:05 Starting x-ui 3.2.6
Jun 05 21:20:05 VM-999436 /usr/local/x-ui/x-ui[16458]: INFO - Web server running HTTPS on [::]:51028
Jun 05 21:20:05 VM-999436 /usr/local/x-ui/x-ui[16458]: INFO - custom geo startup: no custom geofiles configured
Jun 05 21:20:05 VM-999436 /usr/local/x-ui/x-ui[16458]: INFO - Sub server running HTTPS on [::]:2096
Jun 05 21:20:05 VM-999436 /usr/local/x-ui/x-ui[16458]: INFO - XRAY: infra/conf/serial: Reading config: &{Name:bin/config.json Format:json}
Jun 05 21:20:05 VM-999436 /usr/local/x-ui/x-ui[16458]: WARNING - XRAY: core: Xray 26.6.1 started
Jun 05 21:20:54 VM-999436 /usr/local/x-ui/x-ui[16458]: INFO - W4sTJjSO39 logged in successfully, Ip Address: 94.253.102.102
Jun 05 21:20:54 VM-999436 /usr/local/x-ui/x-ui[16458]: INFO - W4sTJjSO39 logged in successfully
Jun 05 21:22:35 VM-999436 /usr/local/x-ui/x-ui[16458]: INFO - XRAY: infra/conf/serial: Reading config: &{Name:bin/config.json Format:json}
Jun 05 21:22:35 VM-999436 /usr/local/x-ui/x-ui[16458]: WARNING - XRAY: core: Xray 26.6.1 started
Jun 05 21:28:48 VM-999436 /usr/local/x-ui/x-ui[16458]: INFO - Received SIGHUP signal. Restarting servers...
Jun 05 21:28:48 VM-999436 /usr/local/x-ui/x-ui[16458]: INFO - WebSocket hub stopped
Jun 05 21:28:48 VM-999436 /usr/local/x-ui/x-ui[16458]: INFO - Web server running HTTPS on [::]:51028
Jun 05 21:28:48 VM-999436 /usr/local/x-ui/x-ui[16458]: INFO - custom geo startup: no custom geofiles configured
Jun 05 21:28:48 VM-999436 x-ui[16458]: 2026/06/05 21:28:48 Web server restarted successfully.
Jun 05 21:28:48 VM-999436 /usr/local/x-ui/x-ui[16458]: INFO - Sub server running HTTPS on [::]:2096
Jun 05 21:28:48 VM-999436 x-ui[16458]: 2026/06/05 21:28:48 Sub server restarted successfully.
Jun 05 21:35:37 VM-999436 x-ui[16458]: 2026/06/05 21:35:37.821594 [Warning] infra/conf: REALITY: Listening on non-443 ports may get your IP blocked by the GFW
Jun 05 21:35:48 VM-999436 /usr/local/x-ui/x-ui[16458]: INFO - XRAY: infra/conf/serial: Reading config: &{Name:bin/config.json Format:json}
Jun 05 21:35:48 VM-999436 /usr/local/x-ui/x-ui[16458]: WARNING - XRAY: infra/conf: REALITY: Listening on non-443 ports may get your IP blocked by the GFW
Jun 05 21:35:48 VM-999436 /usr/local/x-ui/x-ui[16458]: WARNING - XRAY: core: Xray 26.6.1 started
Jun 05 21:39:48 VM-999436 /usr/local/x-ui/x-ui[16458]: INFO - XRAY: infra/conf/serial: Reading config: &{Name:bin/config.json Format:json}
Jun 05 21:39:48 VM-999436 /usr/local/x-ui/x-ui[16458]: WARNING - XRAY: core: Xray 26.6.1 started
Jun 05 21:49:32 VM-999436 x-ui[16458]: 2026/06/05 21:49:32 http: TLS handshake error from 94.253.102.102:50362: read tcp 163.5.16.253:2096->94.253.102.102:50362: read: connection reset by peer