Oblivion Desktop help

Choose what happens on your computer

Start with the symptom you can see. A connection label alone does not tell you whether a particular website or app can use the connection.

Before changing settings

1. Disconnect Oblivion Desktop and open a normally reachable website. If that also fails, check your Wi-Fi, Ethernet or sign-in page first. If the failure began after closing Oblivion, use the recovery check below.
2. Check the computer’s date, time and time zone. Write down your current connection method and network mode before changing either.
3. Open the app menu → About App. The version appears near the bottom; at od: in App Log also identifies it. The latest stable release checked on 5 November 2026 is v3.11.0.

For each comparison, change one setting, reconnect and retry the same website or app. If it makes no difference, disconnect and restore that setting before trying something else.

Reference: connection checklist, About screen, release v3.11.0.

Find your next step

The app won’t install or open

Check your operating system and processor against the download packages. Keep the exact installer filename and the full error message. A launch error happens before a connection can be tested; changing endpoints will not diagnose it. For Windows, start with our installation and launch guide. For macOS and Linux, use the Mac installation guide or Linux installation guide to match the specific message. If the app never opens, include the system’s message in your report instead of an unavailable App Log.

The app won’t connect

After the basic checks above, make one connection attempt and save App Log. Note whether the error mentions registration, an endpoint, the helper or a connection test. If you are using TUN, open the menu → Network Settings → Configuration and compare with System Proxy, keeping the same method. Retry the same browser page. If it works only in System Proxy, that narrows the problem to the TUN path; it does not prove that every app now uses the connection. Restore the previous mode if the comparison does not help. Continue with our step-by-step connection diagnosis.

Waiting for a scan or comparing slow connections? Follow the endpoint and speed guide.

It says connected, but websites won’t open

Try two unrelated websites, then compare with Oblivion disconnected. In Proxy mode (labelled None in v3.11.0), an app needs its own proxy configuration; System Proxy applies the operating system’s proxy settings, which some apps ignore. Check what each mode does. If ordinary browsing works but the IP display stays on “receiving information”, record both observations: failure to fetch that information is not the same as all traffic failing. If all browsing fails only while connected, save the log and the selected mode before changing anything else.

The browser works, but another app does not

Compare the failing app’s proxy setting with your selected mode. It may use a separate proxy or ignore the system proxy. Record the old value before testing a change, reopen the affected app, and restore the value if it does not help. The project has specific guides for Firefox and Telegram. If only one destination fails across several apps, also check routing or filtering rules affecting that destination.

Internet stops working after closing Oblivion

Reopen Oblivion, disconnect explicitly, then quit normally and retry a website. If access is still broken, inspect the operating system’s proxy settings. Record their current values; remove only an Oblivion proxy or PAC setting you can identify as left behind. Keep workplace or other intentional proxy settings. If removing the stale setting restores access, it was part of the problem; if it changes nothing, restore your recorded values and keep the failure details.

The developers describe leftover proxy settings after abnormal shutdown in discussion #1175. This is a possible cause, not a diagnosis of every outage.

Where to find App Log

You do not need a successful connection to collect a log. Open the main app menu → App Log. After a failed attempt, use its copy icon and paste the result into a local text file. Save it before another connection attempt: starting a new attempt clears the previous log.

Keep the metadata and the lines from the start of the attempt through the first error and shutdown. If the log is long, save a text file rather than a cropped screenshot. If it is empty, report that explicitly along with the visible error and time of the attempt.

The version lines identify different components:

• od — Oblivion Desktop, the application.
• wp — warp-plus, the WARP connection component.
• hp — oblivion-helper, used to manage Sing-Box for TUN.
• mp — masque-plus, the Masque component.

A component appearing in the version list does not mean it was the component that failed. Keep method:, proxyMode: and the surrounding error lines together.

Reference: v3.11.0 log viewer, metadata and connection startup.

Prepare a useful problem report

Include your OS version and CPU architecture, Desktop version, method, network mode, internet provider, and whether another network gives a different result. Describe what you tried, what happened and what you expected. Attach the log for that attempt, including the first error. For a keyboard or screen-reader problem, include the affected control and the assistive software/version instead.

Before sharing, review the whole file. Remove usernames and personal paths, public or private IP addresses, visited domains, license keys and tokens. The viewer replaces the current username, but that is not complete anonymization. Preserve error wording, component names and timing. For example:

[time] [info] at od: v3.11.0
[time] [info] method: warp
[time] [info] proxyMode: tun
[time] [info] userData: <PERSONAL_PATH>
[time] [error] connect to <DESTINATION>:443 failed: <EXACT_ERROR>

This is an editing example, not a captured test log. Replace sensitive values in your real log without inventing missing lines.

A short guide to the settings

Method: WARP, Gool, Cfon or Masque

Chooses how the connection is established. It is separate from the network mode. When comparing methods, keep the mode unchanged and test actual access, not just the displayed IP. Compare methods and understand IP location.

Network mode: None (Proxy), System Proxy or TUN

Find it under Network Settings → Configuration. Chooses how applications reach the connection. The None option corresponds to Proxy in the README: it leaves system settings unchanged; System Proxy uses the system proxy/PAC configuration; TUN uses Sing-Box. Use this distinction when one app works and another does not. Choose and check a network mode.

Endpoint and local port

An endpoint is a remote connection address. The local proxy port is where an app on your computer connects; its default is 8086. They are different settings. PAC uses the local proxy port plus one; the helper’s documented gRPC port is 50051. Check your actual configured port before copying a value.

Test URL and routing rules

The test URL is the destination used to check connectivity; failure there alone does not identify a network-wide outage. Routing rules change how destinations are handled. If only one destination fails, inspect its applicable rule and compare after one reversible change.

Reference: network controls, feature overview, ports, routing guide.

If there is no verified fix

Save your results and return changed settings to their previous values. If possible, compare the same setup on another network. A different result helps locate the problem; it does not establish its cause or promise a working endpoint.

The Desktop repository is archived and read-only. You can read existing reports, but cannot submit a new issue there. We do not currently list a confirmed support contact on this hub. Keep your report locally until a suitable contact is available; a closed historical issue does not guarantee a fix for your version.

Guide scope: Desktop v3.11.0 documentation and source, reviewed 5 November 2026. Connection fixes and packaged-app behavior have not been reproduced across Windows, macOS and Linux.