This sample post shows how a bug fix entry looks. The "Fix" category is for resolved bugs, regressions, and crashes — short, clear descriptions of what was broken and what now works. Like the other two sample posts, this one is already published so your public changelog isn't empty — edit or delete it whenever you'd like.

Here's another sample post, this time tagged as an Improvement. Use this category for tweaks, polish, performance wins, and UX upgrades — anything that makes the existing product better without being a brand-new feature. Edit or delete this post whenever you're ready.

This is a sample post we created so your changelog widget has something to show right away. We've already published it so your public changelog has content from day one. Feel free to edit it or delete it whenever you're ready. Posts in the "New Feature" category are great for announcing the big stuff you're shipping.

v2rayN on Windows is reliable once the subscription list is healthy. When every server shows timeout, the problem is usually the update path, not a broken client. This guide covers updating the subscription, running a real delay test, and fixing the common “all nodes timeout” case.

1. Update the subscription the right way

1. Open Subscription group → Subscription group settings.
2. Confirm the URL matches the one on your provider dashboard (log in to your provider's dashboard and copy it fresh). Do not reuse an old link if you rotated the token.
3. Save, then click Update subscription (without proxy). Updating through a dead proxy often fails silently and leaves stale servers.
4. Wait until the status shows success and the server count looks right.

If the update fails, try a phone hotspot, or paste the URL into a browser: you should get a long config payload, not an HTML error page.

2. Run a real delay test

1. Select the servers in that subscription group.
2. Use Test real delay — prefer a real-connection test over ICMP ping. Many nodes block ping but still proxy traffic.
3. Sort by latency and set the fastest responding node as active.
4. Enable the system proxy and open a site that shows your public IP.

Re-test every few days. Latency drifts, and dead nodes drop out after a fresh update.

3. Fix “all nodes timeout”

Work through these checks in order:

A. Subscription never refreshed
Update without proxy, as above. If the dashboard shows a new URL, replace the old one entirely.

B. Client time is wrong
TLS-based protocols fail when the Windows clock is skewed. Sync time automatically, then re-test.

C. Local firewall or antivirus
Allow v2rayN and its core. Corporate filters sometimes block outbound ports used by the nodes.

D. Wrong outbound for the test itself
If “update via proxy” or “test via proxy” points at a dead active server, every check fails. Clear the active server, update without proxy, then test again.

E. Quota or plan limits
Most providers cap free or cheap plans by time or traffic. Hitting a daily free window or a monthly cap can look exactly like a timeout even when the subscription URL is valid, so check your dashboard before you start reinstalling anything.

F. Network blocks the protocol
Try another region or protocol from the same subscription. Some Wi‑Fi networks block uncommon ports; a hotspot test isolates that quickly.

4. Keep the list healthy

• Update weekly so removed servers disappear.
• Keep a second group as backup; switch with one click when the primary goes dark. A free tier works well for this, for example Roxi gives 30 minutes a day at full speed, which is enough to get you back online while you fix the main node.
• Never post your subscription URL in public chats — it is a bearer token.

5. Quick verification after a fix

One node with non-zero real delay, browser IP in that node’s region, and HTTPS loading without certificate warnings. Still stuck? Contact your provider's support with the approximate failure time and whether update-without-proxy succeeded.

Written by the small independent team behind Roxi.