Material checked on 2026-11-14. Error strings are quoted verbatim so you can match them against your own log.
Judge by the exact error, not by the symptom
| Log or symptom | Which step to judge | Do not do this |
|---|---|---|
Failed to build TLS config immediately followed by allowInsecure has been removed | An old TLS field is incompatible with the current core's configuration format | Do not keep re-testing latency, and do not declare every node dead |
Configuration loads, then x509, a certificate name mismatch, or a TLS handshake failure | The certificate or handshake stage — check SNI, the certificate and the device clock | Do not file it as the removed-field parsing error |
Only dial tcp ... timeout | A connection attempt was made; check address, port and network path | Do not touch TLS toggles to make a timeout disappear |
| Node connects, but specific sites fail | DNS, routing and egress | Do not rewrite every node in the subscription |
Issue #6141 in the v2rayNG repository records one case: Android 16, v2rayNG 2.3.5 from F-Droid, Xray-core 26.7.28. Several TLS nodes reported -1 ms and the log rejected allowInsecure while loading the configuration. A maintainer closed the issue and pointed at the related explanation. That is a specific environment report — it does not prove every v2rayNG version and every TLS node behaves the same way.
Safe handling order
- Keep minimal evidence. Note the v2rayNG app version, the core version, the node protocol, the exact error text and when it happened. Redact the subscription URL, password, UUID and server address before sharing a screenshot. Keep the original subscription and a copy of the node configuration.
- Decide whether the configuration loaded at all. Open the log for a single node and look for
Failed to build TLS configtogether withallowInsecure. If those two lines are absent, go back to the table above; the steps here do not apply. - Check where the configuration came from. If the node arrived through an automatic subscription update, check whether the source still emits
allowInsecure,insecure=1, or a "skip certificate verification" flag. Locate the field only in your own copy, and do not send a private subscription to a public conversion site. - Ask the source for a compatible configuration. For a paid service, the provider should check the certificate, SNI, subscription output and the fields the current client supports. If you run the server yourself, fix the server-side certificate and domain configuration. Changing
allowInsecure=truetofalseand declaring victory is not a fix: if the node depended on skipping verification, you will simply meet a real certificate error next. - Verify client and core versions from the official channel. The v2rayNG Releases page carries version and compatibility notes. Back up the configuration before upgrading or downgrading. An older build that still accepts insecure fields is not a security fix.
- Re-verify. After updating the configuration, confirm the original error is gone and the node entry still exists, then test a single connection, an ordinary HTTPS page, and your egress IP. If the error becomes
x509or a timeout, keep diagnosing from that new error — the old message disappearing is not the same as the whole chain working.
Why you should not simply disable certificate checks
allowInsecure concerns verification of the proxy server's identity. Skipping the certificate check lowers the strength of that verification, and public nodes in particular are unsuitable for sensitive accounts. The v2rayNG release notes point towards certificate pinning or a server-side change instead.
A certificate fingerprint has to come from a channel you can independently verify; do not copy one out of the same untrusted connection. If you cannot verify the server certificate or the provider's identity, stopping use of that node is a better outcome than switching verification off.
Scope and evidence boundary
This page is built from an official user report and the project's release notes. It was not reproduced across every Android version, core, subscription format and carrier. The detail in #6141 that the same subscription worked on a desktop client describes the reporter's comparison only; it does not prove Android is the sole failing point. If the log only contains the words allowInsecure without surrounding context, record the complete error chain first. TLS and REALITY parameters are not interchangeable between protocols.
Checked 2026-11-12 against v2rayNG issue #6141, the v2rayNG Releases page, and the maintainer-linked discussion on migrating away from allowInsecure.
Frequently asked questions
All nodes show -1 ms. Is that this error?
No. -1 is the result of a failed test and can come from configuration parsing, networking, certificates, DNS or the test method itself. Only when the log explicitly contains Failed to build TLS config and allowInsecure has been removed should you use this page.
If I delete the allowInsecure field, will it connect?
Not necessarily. Removing the old field may let the configuration reach the next stage; if the server certificate cannot be validated, a certificate error follows. The provider should supply a trusted certificate or a configuration you can verify, and you should still make a real HTTPS request.
Can I just install an older v2rayNG?
Only as a short-term comparison. Treating acceptance of an insecure field as a fix is wrong. Get builds from official Releases and back up your configuration; do not install modified builds from unknown sources.
The error returns after a subscription update. Why?
The source is probably still emitting the old field, or the client overwrote your local change during the update. Keep a redacted error and ask the provider to change the subscription output instead of editing your only copy again and again.
The same subscription works on my computer but not on my phone. Does that prove the nodes are fine?
It only proves they worked on that computer with that client, core and network at that moment. On the phone you still need the app version, the generated configuration and the full log before drawing a conclusion.
Continue reading
failed to open geosite.dat in v2rayN · Hiddify WARP: netip.ParsePrefix with an empty IP · Full error string index