#Clawhub getting an error when click download or sign in with Github

1 messages · Page 1 of 1 (latest)

thick swanBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> âś… Mark Solution

gleaming latchBOT
#

That URL (clawhub.ai/?code=...) is the GitHub OAuth callback. Two quick things:

  1. Please don’t paste OAuth code= links publicly (it’s usually short‑lived, but still). If you can, edit/delete the message.

  2. That callback URL normally includes both code= and state=. Your link shows only code=... — if state is missing (or got stripped), sign-in will fail.

To debug + fix, can you tell me:

  • What’s the exact error message you see (toast/banner + any status code)?
  • Are you opening ClawHub inside Discord’s in-app browser? (That often breaks GitHub sign-in + clipboard/download.)
  • After GitHub redirects back, does your address bar show .../?code=...&state=... or only code?

Things to try (in order):

  • Open https://clawhub.ai in a full browser (Chrome/Firefox), not the Discord in-app browser.
  • Disable/allowlist blockers for auth.clawdhub.com (adblock/privacy tools sometimes block it because it contains “auth”), then retry sign-in and download.
  • If you’re on Brave/Safari: temporarily relax anti-tracking / “shields” for the site and try again.
#

If you paste the exact error text (and ideally a screenshot), I can narrow it down fast.

untold ledge
#

yes as soon as I click it; it redirects me to clawdhub.com and authorizes the app. Is that correct website? It says insecure and then site cant be reached.

gleaming latchBOT
# untold ledge yes as soon as I click it; it redirects me to clawdhub.com and authorizes the ap...

Yep — the GitHub authorize screen is the right flow, and seeing it bounce through clawdhub.com can be normal (it’s basically a redirect/legacy domain in the chain).

What’s not expected is: you authorize successfully, but then ClawHub still errors / doesn’t log you in / download fails.

A couple quick checks that usually explain this:

  1. Are you doing this inside Discord’s in-app browser?
    If yes: open https://clawhub.ai in a real browser (Chrome/Firefox) and try again. In-app browsers often break OAuth + downloads.

  2. After authorizing, what’s the final URL in the address bar?

  • Good: https://clawhub.ai/... (and you end up logged in)
  • Suspicious: it ends on clawdhub.com/?code=... (or only code without a state)
  1. Privacy blockers: please try with adblock/shields off (or allowlist) for:
  • clawhub.ai
  • auth.clawdhub.com
gleaming latchBOT
# untold ledge is clawdhub.com with the d correct?

Yes — clawdhub.com (with the “d”) is correct. It’s basically an alias/redirect domain used in the auth flow.

The main site is clawhub.ai (no “d”). So a typical flow is:

clawhub.ai → GitHub authorize → callback via clawdhub.com → back to clawhub.ai (logged in)

If you authorize and then it doesn’t land you back on clawhub.ai (or you land back but you’re not logged in / downloads error), that’s when something’s broken (often Discord in-app browser or blocked cookies).

If you tell me what the final URL is after you click “Authorize” (domain + whether it has state=), I can pinpoint the cause.

#

Also: if you can, delete/edit the message that contains ?code=... (OAuth codes are short-lived but still shouldn’t be public).

If you paste the exact error text you see (or a screenshot) + your browser (Brave/Safari/Chrome, desktop/mobile), I can tell you whether it’s cookies/ITP vs a ClawHub bug.

untold ledge
#

This site can’t be reached
The connection was reset.
Try:

Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_RESET

gleaming latchBOT
# untold ledge This site can’t be reached The connection was reset. Try: Checking the connecti...

ERR_CONNECTION_RESET usually means something on your network path is actively dropping/resetting the TCP connection (VPN/proxy/firewall/AV, corporate network, Pi-hole/NextDNS, ISP filtering). The ClawHub endpoints themselves look up from here:

  • https://clawdhub.com/ → redirects to https://clawhub.ai/
  • https://auth.clawdhub.com/api/v1/skills/duckduckgo-search returns JSON (should load in a browser)

Can you try these two quick tests and tell me which one resets?

  1. Open in a normal browser (not Discord in-app browser):
    https://clawhub.ai/

  2. Open the API directly:
    https://auth.clawdhub.com/api/v1/skills/duckduckgo-search
    (If this one resets, sign-in/download will fail because that’s the backend.)

If it resets, common fixes:

  • Disable VPN / proxy and retry
  • Temporarily disable adblock “shields” / DNS blockers (Pi-hole, NextDNS, uBlock) or allowlist auth.clawdhub.com
#
  • Try from mobile data / a different network (quick way to confirm it’s your network)
  • If you’re on a corporate network: it may be blocked by policy / TLS inspection

Also: the browser error page usually shows the exact domain that “can’t be reached” — paste that domain and your browser/OS and I’ll narrow it down.

untold ledge
#

it worked from my mobile

#

now how do i get it to work from desktop?

#

not on corporate and i tried disconnecting vpn and doing it still no go

gleaming latchBOT
# untold ledge not on corporate and i tried disconnecting vpn and doing it still no go

ERR_CONNECTION_RESET after disconnecting VPN pretty much confirms it’s local network/device/security software resetting the connection (the ClawHub domains are reachable from here).

Can you do 2 super-specific tests and tell me which exact hostname resets?

  1. Open (in a normal browser, not Discord in-app):
  1. Open this API endpoint directly:

If either one resets, try this isolation step (fastest way to pinpoint):

  • Try from your phone on mobile data (or computer using a mobile hotspot).
    • If it works on hotspot → your home ISP DNS/router/filter is the culprit.
    • If it still fails on hotspot → it’s device-level (antivirus, “secure DNS”, firewall app).

If it’s network-related, the usual fix is:

  • Temporarily set DNS to 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google)
#
  • Disable “Secure DNS / DNS over HTTPS” in the browser (it can be set to an adblocking provider)

Also helpful: what OS + browser are you on, and does the error page show it failing on clawhub.ai or auth.clawdhub.com specifically?

untold ledge
#

chrome and i tried disabling dns stll no luck

gleaming latchBOT
# untold ledge chrome and i tried disabling dns stll no luck

If you’re still getting ERR_CONNECTION_RESET in Chrome even with VPN + DNS changes, that’s almost always protocol/network-path (HTTP/3/QUIC or IPv6) or local security software resetting the socket — not an “OAuth code” issue.

Two very telling tests:

1) Does this URL load for you?

https://auth.clawdhub.com/api/v1/skills/duckduckgo-search
(If this resets, ClawHub login/download can’t work because the backend is unreachable from your machine.)

2) Disable QUIC / HTTP3 in Chrome (this fixes a surprising number of “connection reset” cases)

  • Open: chrome://flags/#enable-quic
  • Set Experimental QUIC protocol → Disabled
  • Relaunch Chrome and retry ClawHub

3) Quick IPv6 check (optional but super useful)

If you can run a terminal command, try forcing IPv4:

  • macOS/Linux:
# 
curl -4I https://clawhub.ai
curl -4I https://auth.clawdhub.com/api/v1/skills/duckduckgo-search
  • Windows (PowerShell):
curl.exe -4I https://clawhub.ai
curl.exe -4I https://auth.clawdhub.com/api/v1/skills/duckduckgo-search

If -4 works but normal doesn’t → it’s an IPv6 routing issue (common on some home ISPs/routers). Workaround: temporarily disable IPv6 on your network adapter or router.

Can you tell me:

  • Your OS (Windows/macOS/Linux) and roughly what country/ISP you’re on
  • Which exact hostname resets (clawhub.ai vs auth.clawdhub.com)
  • Whether disabling QUIC changed anything
untold ledge