Testnet faucet OAuth callback returns HTTP 500 — unable to obtain testnet funds

Tech
1

Hi Logos team,

I’ve been running a Logos Blockchain testnet node successfully for several days. The node is synchronized and reports Online, but I’m unable to obtain testnet funds because authentication to the faucet consistently fails.

Issue

When accessing the official testnet faucet and signing in with GitHub, the OAuth flow reaches:

testnet.blockchain.logos.co/oauth2/callback

but the callback returns:

500 Internal Server Error

I’ve reproduced this multiple times, including in a Chrome Incognito window.

Some Request IDs from separate attempts:

9ce58ae8-e435-4f12-a56f-60953195c3ea

500bc893-f569-42ee-acd6-d20948d107a4

10fb0cb1-e15c-4385-a190-6a50536b95d6

I also tested the faucet backend directly. It correctly returns 403 Forbidden and redirects to GitHub authentication, so the endpoint itself appears reachable; the failure occurs during/after the OAuth callback.

I previously reported this in the logos-co/logos-basecamp GitHub repository. A contributor confirmed that the OAuth callback service/reverse proxy is not part of Basecamp and suggested routing the issue to whoever maintains the callback service/reverse proxy or correlating the Request IDs with its server logs.

Additional Discord verification issue

I also tried reaching the testnet support channel through the official Logos Discord. The server requires Collab.Land verification before the other channels become accessible. The verification redirected me to collab.land-cdn.com, which Rabby Wallet explicitly flagged as a scam/dangerous website, so I did not connect or sign anything.

Could someone from the Logos team please:

  1. Check/correlate the OAuth Request IDs above with the faucet callback/reverse-proxy logs;

  2. Confirm whether the faucet authentication service is currently working for other users; and

  3. Confirm whether the collab.land-cdn.com verification flow currently shown in the Logos Discord is legitimate?

I’m happy to provide additional sanitized logs or test anything needed. No credentials/private keys will be shared.

Thanks!

1 Like
2

have you tried just requesting from the frontend of the faucet on your browser, just paste in the funding wallet you want to use

1 Like
3

This is what I’m doing

4

I can confirm this one, and the good news is it’s not on your end.

I tried the callback URL with a plain GET, no OAuth code at all, and it still returns 500. So the server crashes before it even looks at your login. Nothing about your browser or GitHub account matters here.

The sign-in step itself is fine (it redirects to GitHub correctly), it’s only the callback leg that’s broken. Someone with access to the proxy config should be able to reproduce it with a single curl.

Until it’s fixed, the workaround above is the way: paste your funding key into the faucet page directly. That path doesn’t need a sign-in at all.

One more thing I noticed while testing: the faucet accepts and queues even an invalid key (I sent a garbage one and got “queued” back). So if you mistype your key it won’t error, it just silently never funds. Double-check the key you paste.

1 Like
5

There is no Auth on the faucet, perhaps you went to a different URL? Can you try this URL here?

1 Like
6

AFAIK there is zero collabland integration in the server, ensure you are joining the right server!