Blog

  • Mac Offline After Quitting a Proxy App: Clearing Leftover Settings

    On macOS a proxy app sets proxy fields on your active network service. If it crashes or is force-quit, those fields can stay behind and everything appears offline.

    Find the source

    System Settings → Network → (your Wi-Fi or Ethernet) → Details → Proxies. Look for Web Proxy (HTTP), Secure Web Proxy (HTTPS), SOCKS Proxy or Automatic Proxy Configuration pointing to 127.0.0.1 or a local PAC URL.

    Clear them one by one

    Untick each enabled proxy type and click OK. Note that settings are per network service: if you use both Wi-Fi and a USB Ethernet adapter, check both.

    From Terminal

    networksetup -listallnetworkservices lists services, and networksetup -getwebproxy "Wi-Fi" shows what’s set. networksetup -setwebproxystate "Wi-Fi" off (and the matching secure web, SOCKS and auto-proxy commands) turns them off.

    Check DNS and TUN

    If you used enhanced or TUN mode, a utun interface or custom DNS may linger. Reopening the app and quitting it from its own menu usually removes them cleanly.

    Step-by-step with all the commands:

    https://roxi.cc/macnet26.html

    Written by the small team behind Roxi.

  • How to update a subscription and fix “all nodes timeout” in v2rayN

    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 (for example Roxi after login). 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

    Providers are not unlimited. On Roxi the free tier is 30 minutes per day at full speed; VIP is 3.57 USD / 30 days (200GB) and SVIP is 7.14 USD / 30 days (500GB). New users get an exclusive offer plus a free trial. Hitting the daily free window or monthly cap can look like timeout even when the URL is valid.


    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.

    • 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? Email support@roxi.cc with the approximate failure time and whether update-without-proxy succeeded.


    Written by the small independent team behind Roxi.

  • Hello world!

    Welcome to blog5.click blog hosting Sites. This is your first post. Edit or delete it, then start writing!