Drıftstack docs
Docs

Page didn’t load in the session (proxy slow, DNS, 403/404/429, TLS)

You might be here because: “Page didn’t load” · “the site won’t open in the phone” · “Couldn’t find this site’s address” · “Secure connection failed” · “Access to this page was denied (403)” · “The site is rate-limiting requests” · “The site took too long to respond” · “Start page couldn’t load” · “website won’t load” · “blank page” · “site is blocked in the session”

Short answer

The page failed to load inside the session. The banner names the reason: the site’s address could not be found, the secure connection failed, the site answered with an error, or it timed out. The session goes out through the proxy you chose, so a slow or blocking proxy is the first thing to test.

Check first

  • Does the same page load a second time? Tap reload.
  • Is the profile’s proxy saved and did its test pass? A proxy that is slow or blocked shows up here first.
  • Does a different well-known site load? If nothing loads, it is the connection, not the site.

Likely causes and fixes

The sentences below are the app’s own wording.

  1. “Page didn’t load — the proxy may be slow or blocking it.” Shown when the session runs through your proxy. Fix: test the proxy in the Proxies tab, try another proxy, or wait and reload.

  2. “Couldn’t find this site’s address.” DNS failed. Part of these are on our side, so do not assume the address is wrong; reload, then try another site to compare.

  3. “Secure connection failed — the site, your network, or the proxy may be the cause.” Reload; try through a different proxy.

  4. HTTP errors: “This page wasn’t found (404)”, “Access to this page was denied (403)”, “This page requires you to sign in (401)”, “The site is rate-limiting requests — try again shortly (429)”, “The site is having problems right now (HTTP 5xx)”. These come from the site itself. 403 and 429 often mean the site is refusing your proxy’s address; try a different proxy or wait.

  5. “The site took too long to respond.” / “Network error while loading the page.” Slow proxy or site. Reload; test the proxy.

  6. “This older session has no proxy of yours, and its connection isn’t working, so pages can’t load. This is on our side — a new session goes through one of your own proxies.”. Launch a new session.

If it still fails

Press Talk to a person in this chat (or open Help) and include the exact banner text, the site, the proxy type and whether other sites load. Support does not troubleshoot a third-party site’s own errors (403/429/5xx) beyond confirming the session’s connection works.