Qv2ray

# General Settings

General Settings are for Qv2ray itself, including appearance, behavior and network settings.

Tips

The general settings will only change the behavior of Qv2ray itself, but will not affect the proxying behavior of the V2Ray Core.

# Appearance

Set how Qv2ray looks and feels.

  • Recent Jumplist: Set the number of recently used connections displayed in the notification icon right-click menu - recent connections list.
  • Maximum Log Lines: Set the upper limit of the number of log records in the Log pane on the right side of the Qv2ray main interface. After the set value is exceeded, the older logs will be purged automatically.
  • Others: Set up as you like~🤐

# Behavior

Set the behavior of Qv2ray.

  • Quiet Mode: When enabled, Qv2ray will not actively pop up any notifications.
  • Others: It's already very simple, why should I talk about it? 😶

# Network Settings

Set the way Qv2ray accesses the network.

  • Latency Testing Method: Set the test method for node delay.
    • TCPing: Qv2ray's default delay test method. The test result is closer to the actual user experience, but the node based on the mKCP protocol cannot be tested, since it's based on UDP instead of TCP.
    • ICMPing: The delay test method based on ICMP / UDP protocol is currently recognized and mainstream delay test method on the market, and it is also the test principle of ping command in Windows and Unix systems. The test result is much lower than TCPing and far better than the actual experience. It can be used to test nodes based on mKCP protocol.
  • User Agent: The client information declared by Qv2ray when making network requests. If you do not understand what UA is, please do not change this setting.
  • Qv2ray Proxy: The proxy settings used by Qv2ray when making network requests, not the proxy settings used by V2Ray Core for network traffic.

What is Qv2ray proxy?

If you want Qv2ray to update subscriptions or detect version updates through a proxy, please configure this.

If you want the traffic proxied by V2Ray to pass through another proxy, or your network needs to pass through a layer of proxy to connect to the Internet, then please use the Forward Proxy function and do not configure this option.

# Advanced Behavior

Set the advanced behavior of Qv2ray. Please do note that abuse of these settings may have negative effects!

  • Set AllowInsecure by Default: All new connections imported via subscription / QR code / VMess protocol link will be enabled by default to allow insecure certificates. Enabling this setting will cause the relevant nodes to lose TLS protection, and there is a risk of man in the middle attacks. Nodes added by manually filling in connection properties or editing JSON are not affected by this option. If you do not understand the actual use of this option, please do not open it!
  • Enable SessionResumption by Default: New in Qv2ray v2.6.0. When enabled, new connections imported with TLS will enable Session Resumption to reduce RTT during handshake. You will also need to enable related functions on the server side, such as 0-RTT Connection Resumption on Cloudflare and ssl_early_data on nginx. However, this will largely increase the risk of traffic being recognised.
  • Test Latency on Connect: When enabled, Qv2ray will test the latency of nodes on connect. Enabling this may make it easier for GFW to recognize your connection.
  • Test Latency Periodically: When enabled, Qv2ray will periodically test the latency of the currently connected node. Enabling this may make it easier for GFW to recognize your connection.
  • Disable System Root Certificates: When enabled, V2Ray core will only use built-in root certificates, which helps to circumvent root certificate hijacking attack. However, this can cause V2Ray core fail to recognise your valid TLS certificates, resulting in connectivity problem with your nodes.
  • (Removed) Set AllowInsecureCiphers by Default: All new connections imported through subscription / QR code / VMess protocol link will be enabled by default to allow insecure TLS algorithm option. Enabling this setting will cause related nodes to lose TLS protection, and there is a risk of man-in-the-middle attacks. Nodes added by manually filling in connection properties or editing JSON are not affected by this option. If you do not understand the actual use of this option, please do not open it!

Re-emphasis:

Misuse of the above settings may cause negative effects and even lead to security issues! If you do not understand the actual use of these options, please do not open them!

(Outdated) Notes on V2ray Core versions before 4.23.1

Updated at 2021-01-25: We believe that no one will use that old V2Ray core version. This notice is no longer effective and is only kept for historical reasons.

Updated at 2020-05-30: Due to implementation issues, V2Ray core will use hard-coded TLS cipher suites when AllowInsecureCiphers is disabled, which makes its TLS traffic highly distinguishable. Enabling AllowInsecureCiphers will ease the issue temporarily, but it will require all influenced connections to be re-imported.

⟵ Advanced Route Settings ⟶