Before you submit
PasarGuard version
v5.3.0
Installation type
Other
What happened?
Confirming this still happens on the latest release, v5.3.0. Editing the "Verify peer cert by name" field on an inbound's TLS settings still crashes the dashboard / triggers a client-side error, and directly saving verifyPeerCertByName as an array (old format) also fails since Xray-core now expects it as a plain string. Had to bypass the UI entirely and edit the raw core JSON to work around it.
Screenshot attached below.
Steps to reproduce
Confirming this still happens on the latest release, v5.3.0. Editing the "Verify peer cert by name" field on an inbound's TLS settings still crashes the dashboard / triggers a client-side error, and directly saving verifyPeerCertByName as an array (old format) also fails since Xray-core now expects it as a plain string. Had to bypass the UI entirely and edit the raw core JSON to work around it.
Screenshot attached below.
Expected behavior
Confirming this still happens on the latest release, v5.3.0. Editing the "Verify peer cert by name" field on an inbound's TLS settings still crashes the dashboard / triggers a client-side error, and directly saving verifyPeerCertByName as an array (old format) also fails since Xray-core now expects it as a plain string. Had to bypass the UI entirely and edit the raw core JSON to work around it.
Screenshot attached below.
Logs and error messages
Confirming this still happens on the latest release, v5.3.0. Editing the "Verify peer cert by name" field on an inbound's TLS settings still crashes the dashboard / triggers a client-side error, and directly saving verifyPeerCertByName as an array (old format) also fails since Xray-core now expects it as a plain string. Had to bypass the UI entirely and edit the raw core JSON to work around it.
Screenshot attached below.
Environment
OS:
Database: SQLite / MySQL / PostgreSQL / TimescaleDB
Python version:
Node.js version:
Browser:
Reverse proxy / CDN:
Relevant configuration
Screenshots or videos
No response
Additional context
Before you submit
PasarGuard version
v5.3.0
Installation type
Other
What happened?
Confirming this still happens on the latest release, v5.3.0. Editing the "Verify peer cert by name" field on an inbound's TLS settings still crashes the dashboard / triggers a client-side error, and directly saving verifyPeerCertByName as an array (old format) also fails since Xray-core now expects it as a plain string. Had to bypass the UI entirely and edit the raw core JSON to work around it.
Screenshot attached below.
Steps to reproduce
Confirming this still happens on the latest release, v5.3.0. Editing the "Verify peer cert by name" field on an inbound's TLS settings still crashes the dashboard / triggers a client-side error, and directly saving verifyPeerCertByName as an array (old format) also fails since Xray-core now expects it as a plain string. Had to bypass the UI entirely and edit the raw core JSON to work around it.
Screenshot attached below.
Expected behavior
Confirming this still happens on the latest release, v5.3.0. Editing the "Verify peer cert by name" field on an inbound's TLS settings still crashes the dashboard / triggers a client-side error, and directly saving verifyPeerCertByName as an array (old format) also fails since Xray-core now expects it as a plain string. Had to bypass the UI entirely and edit the raw core JSON to work around it.
Screenshot attached below.
Logs and error messages
Environment
OS:
Database: SQLite / MySQL / PostgreSQL / TimescaleDB
Python version:
Node.js version:
Browser:
Reverse proxy / CDN:
Relevant configuration
Screenshots or videos
No response
Additional context