Connected, but one app won’t work?

Start with the app, not another full reset

If no app can reach the internet, use the connection checks. If a browser works but Telegram, Discord or another app does not, check how that app reaches the connection first.

1. Note the method (WARP, Gool, Cfon/Psiphon or Masque), Configuration (Proxy, System Proxy or TUN), and the exact action that fails. Keep the working settings so you can return to them.
2. Match the app to the mode. Proxy (labelled None in v3.11.0’s Configuration menu) needs manual settings in the app. System Proxy needs the app to use the operating system’s proxy. TUN routes traffic at the network level; it still has routing rules and does not guarantee every service will work.
3. In Network Settings, read Proxy Port and Bind Address. For a client on the same computer, use the local values below. Start Oblivion before opening the client.
4. Change one setting, reconnect Oblivion if you changed its configuration, then restart the affected app. Repeat the same action. If it still fails, restore the setting before the next comparison.

Do not use the endpoint or PAC port here. The endpoint is remote; PAC normally uses Proxy Port + 1 (8087 with the default port). Neither is the local SOCKS5 port. These examples are for an app running on the same computer, not another device or an isolated container. Desktop network controls · Port guide

Telegram: choose system proxy or manual SOCKS5

For Telegram Desktop with Oblivion in System Proxy, open Settings → Advanced → Connection type and select Use system proxy settings. Close the dialog and check whether messages refresh and a file downloads. Menu wording can differ by client version.

If that does not work, or you use Oblivion’s Proxy mode:

1. Open Telegram’s proxy settings and choose Add Proxy.
2. Select SOCKS5 and enter the host and current port from the table. Leave the credentials empty, save and select this proxy.
3. Check messages and a download separately. Test a call separately too: a successful message does not prove that calls use a working route.

If it remains on “Connecting”, check that Oblivion is still connected and that the port matches. To undo the test, select your previous connection option and remove only the proxy entry you added. When testing TUN, a stale manual Telegram proxy can still interfere; record it before returning Telegram to its normal connection setting. Telegram setup guide

Messages work, calls do not? Do not rely on an old “Use proxy for calls” tutorial: Telegram Desktop v7.4.0’s proxy code marks call support as unavailable. A working in-app SOCKS5 proxy therefore does not establish a route for calls. Compare Oblivion’s TUN mode, check Block UDP, and test a call separately; restore the previous settings if it fails. This is a diagnostic comparison, not a verified call fix. Telegram Desktop v7.4.0 proxy code

Firefox: check proxy settings, then DNS

Search Firefox Settings for proxy and open its connection settings. With Oblivion in System Proxy, choose Use system proxy settings. This does not configure Oblivion’s plain Proxy mode for you.

For a manual test, choose Manual proxy configuration, enter the local address under SOCKS Host with the actual proxy port, and select SOCKS v5. Do not put these values in HTTP Proxy instead. Enable Proxy DNS when using SOCKS v5 if you want Firefox to resolve names through that SOCKS connection, then save and reopen the failing site. The DNS option concerns SOCKS5; it does not turn an unrelated HTTP proxy into SOCKS5.

If it still fails, inspect No Proxy For for an entry matching the site, and check whether an extension controls the proxy. Also note Firefox’s separate DNS over HTTPS setting before changing it; it is a different control from SOCKS proxy DNS. Restore your previous proxy and DNS selections if the test does not help. Firefox connection settings · Desktop’s Firefox guide

Discord opens, but voice or video fails

Test three things separately: updating/signing in, joining a voice channel, and video or screen sharing. RTC Connecting or No Route after a successful login is a voice-connection problem. Discord’s voice guidance specifically calls out UDP support. Discord voice errors

• If System Proxy loads websites but Discord cannot update, sign in or connect to voice, compare TUN once, keeping the connection method unchanged. Return to the previous mode if it does not help.
• While using TUN mode, open Tunnel Settings and check Block UDP. If it is on, note its state, turn it off for a comparison, reconnect and retry the same voice channel. Re-enable it if you decide to keep your earlier setup.
• In TUN mode, Desktop v3.11.0 also has a Discord switch near the bottom of Tunnel Settings. Its generated configuration sends UDP from processes named Discord or discord directly (.exe on Windows). It is a routing bypass, not proof of voice working through the proxy. If direct voice traffic suits your setup, compare the switch on and off, reconnecting each time; restore it if it does not help. Do not assume the same process rule covers Discord in a browser or a differently named client.

Live Discord calls have not been tested for this guide. Reconnect and test a call after changing the setting. Discord routing implementation · Earlier voice report

Masque shows “datagram frame too large”

A report from Desktop v3.0.0 records this error with Masque/System Proxy while opening Discord, after the local proxy started. It does not establish a universal cause or a verified fix in v3.11.0. Save the exact log line, method and mode; compare one other method while keeping the mode unchanged. The report’s workaround through a second proxy app is not a tested recipe here. Historical Masque report

YouTube opens, but playback stops

Use the same video for comparisons and let it play beyond the point where it normally stops. Opening the homepage or seeing thumbnails is not a playback test.

1. Try a lower playback quality. If it continues, that identifies a useful playback condition; it does not prove the cause is Oblivion.
2. Compare an updated browser with extensions temporarily disabled, or a separate clean browser profile. Check its proxy settings too, so you do not accidentally compare a proxied browser with a direct one. Restore extensions after the test.
3. If needed, compare one connection method at a time and keep the browser, video and mode unchanged. Record the time playback stops and any player error. Restore the previous method if it is no better.

Older Desktop reports describe a pause around one minute. They do not establish a single cause: the symptom was reported with different apparent IP countries, and rolling back did not consistently resolve it. Embedded playback was a temporary user workaround, not a confirmed permanent fix. YouTube report #638 · YouTube playback guidance

For Spotify or another streaming service, distinguish a connection timeout from an explicit account, subscription or region message. A successful network connection cannot resolve every service restriction; see service-side limits.

Store apps, launchers and games

Check sign-in, downloading, joining a server and voice chat separately. A launcher downloading successfully does not establish that the game’s traffic follows the same route.

If a Windows Store/UWP app or launcher has no proxy setting and ignores System Proxy, a TUN comparison is the next useful test. Keep the method unchanged, reconnect, reopen the app and repeat the failing action. If it fails, restore the earlier mode. Do not start with broad loopback exemptions or firewall changes: the app’s packaging alone does not identify the fault.

For game voice, check UDP separately as in the Discord section; the Discord-specific switch is not a game-wide fix. If a specific server or anti-cheat system rejects the connection, keep the exact message and consult that service’s guidance. There is no verified universal launcher/game workaround. Desktop service troubleshooting · Historical Epic download report

The IDE connects, but Gradle or Python does not

Identify which process makes the failed request. The IDE, a Gradle build, a package manager and your running program may use different proxy settings. A successful IDE “Check connection” only verifies that request.

• PyCharm / IDE: configure its proxy under Settings → Appearance & Behavior → System Settings → HTTP Proxy. For a manual SOCKS connection, use the local host and actual port, then check the same destination. Keep the old setting for rollback. PyCharm proxy settings
• Gradle: configure the build’s proxy separately. Gradle documents systemProp.socksProxyHost and systemProp.socksProxyPort in gradle.properties for SOCKS; HTTP and HTTPS have separate properties. Use values matching the listener and retry the failed dependency download. Remove only the properties you added if it does not help. Android Studio’s IDE proxy settings can override gradle.properties for builds it launches, so compare the IDE build with the command-line build. Gradle networking · Android Studio proxy precedence
• Python / package manager: configure the networking library or tool that actually runs. For example, HTTPX reads HTTP_PROXY, HTTPS_PROXY and ALL_PROXY by default; trust_env=False disables that behavior, and NO_PROXY can exclude a destination. A PyCharm setting alone is not a runtime proxy configuration. Use the installed tool’s supported proxy type and version-specific instructions, then retry the same request and revert the change if needed. HTTPX environment settings

For an HTTPX SOCKS5 setup, install its optional SOCKS support in the environment that runs your code: python -m pip install "httpx[socks]". With the default local listener, the proxy URL is socks5://127.0.0.1:8086; replace the port if yours differs. Use the proxy option supported by your installed HTTPX version. Adding an environment variable cannot install missing SOCKS support. HTTPX SOCKS setup

A remote interpreter, container or VM has its own meaning of 127.0.0.1. If the process is not on the same host/network namespace as Oblivion, the local example above is not enough. A timeout such as httpx.ConnectTimeout or telegram.TimedOut does not by itself identify which proxy layer failed. Earlier Python report

When the service itself refuses access

Read the actual error before changing more settings. A timeout, a proxy connection refusal, a DNS error and a “not available in your country” response are different symptoms. WARP can conflict with services that enforce location-based access; Cloudflare documents this for some games and streaming services. Its official client’s behavior does not establish every route used by Desktop. Cloudflare’s known issues

The same distinction applies to AI services: an account or supported-country restriction is not a failed tunnel. Changing an endpoint is not a reliable country selector, and no method guarantees access to a particular service. See connection methods and IP location.

If just one destination fails, inspect its routing and filtering rules. If it fails across methods and networks, check the service’s status/support information. Keep the client version, OS, method, mode, exact failing action and a short log excerpt with personal data removed. The archived Desktop repository offers historical reports, not a promise of active support. Find and prepare App Log