error: redirect_uri_mismatch
See original GitHub issueoops! something went wrong
error: redirect_uri_mismatch error_description: redirect_uri did not match any of the client's registered redirect_uris state: kjkmdskdmsmmsmdslmdlsm
OAuth with Swan is not working and throws a redirect_uri_mismatch
error instead.
Steps To Reproduce
- Log in to specter desktop, e.g. ‘http://umbrel.local:25441’
- Click on ‘+ Choose plugins’
- Click on ‘Swan’
- Click on ‘Existing Swan users’
- Click on ‘Link your account’
- New tab opens presenting the error shown in the screenshot
https://api.swanbitcoin.com/oidc/auth?client_id=specter&redirect_uri=http://umbrel.local:25441/svc/swan/oauth2/callback&response_type=code&response_mode=query&code_challenge=<redacted>&code_challenge_method=S256&state=kjkmdskdmsmmsmdslmdlsm&scope=offline_access%20v1%20write:vendor_wallet%20read:vendor_wallet%20write:automatic_withdrawal%20read:automatic_withdrawal&prompt=consent
Expected behavior This has worked at least once at some point in a version of specter desktop prior to updating to 1.13.1. I don’t know exactly in which version this regression was introduced though. Auto-withdrawals from Swan to Specter had been working for this account for quite some time. Eventually the auto-withdrawal stopped working which is why I attempted to re-connect the plugin.
Screenshots
- Where is your node running: umbrel
- Where is your specter running: umbrel
- If you’re running a binary, which OS: I don’t think it matters, but I’m also running specterd hwibridge on macOS since I access specter remotely
- Browser: any, I tried Chrome, Brave, Safari and Edge
- Specter Version: 1.13.1
Issue Analytics
- State:
- Created 10 months ago
- Comments:18 (7 by maintainers)
Top Results From Across the Web
Google OAuth 2 authorization - Error: redirect_uri_mismatch
Go to the console for your project and look under API Access. You should see your client ID & client secret there, along...
Read more >Error 400: redirect_uri_mismatch (Google Single Sign-On)
This error typically means the Client Redirect URL was not properly added to the OAuth Web Application in the Google Cloud Console. To...
Read more >Google OAuth2: How the fix redirect_uri_mismatch error. Part ...
The redirect_uri_mismatch error message is quite common when working with the Google APIs. Google APIs support authorization to private user ...
Read more >400 redirect_uri_mismatch Error
This happens when the URL to your site is not typed in exactly right in the API console to the newly created Client...
Read more >Google OAuth 2 Error 400: redirect_uri_mismatch but redirect ...
Google OAuth 2 Error 400: redirect_uri_mismatch but redirect uri is compliant and already registered in Google Cloud Console. 3110 views.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@aphex3k we’ve identified the issue, it is on the Swan server side. I will tag you here, once it is resolved. Thanks for your patience and for bringing it to our attention!
I’ve been using the same specter desktop instance on my umbrel. I’ve not moved it or anything. I just updated the docker containers to whatever was latest at the time and set up the Swan extension on the first version that it had available in a non-pre version.