12-09-2020 21:32
12-09-2020 21:32
When I run my application, it works up until the point where the page needs to redirect to another page and grab the url from the current page and use that token to authenticate.
At that point unfortunately, I receive an SSL error, page looked something like this:
I'm creating this application with NodeJS in Firefox
12-10-2020 17:30
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
12-10-2020 17:30
Hi @StevenCopeland,
Are you using localhost as your redirect URI for users? The redirect URI you're using is fine for testing purposes, but won't work in a production environment. Localhost is not a URL that is external to the internet world that the public can access. You'll need to provide a valid redirect URI to your application to redirect your users back to after they grant consent to your application.
I hope this helps. Let me know if you have any additional questions.
Best Answer08-19-2025 23:59
08-19-2025 23:59
The error SSL_ERROR_RX_RECORD_TOO_LONG usually happens when the server is listening on port 443 but not properly configured for SSL/TLS. In your case, since the redirect breaks during token authentication, it’s likely the HTTPS setup is missing or misconfigured. Make sure your NodeJS server is serving with valid SSL certificates and not using plain HTTP on the HTTPS port. Also, check if your reverse proxy (like Nginx/Apache) is forwarding requests correctly to your Node app. Fixing the SSL configuration should resolve the redirect and token issue. In addition to cleaning your cache and restarting your browser, you could also try upgrading your proxy settings and altering your TLS preferences. Hope it helps!
Best Answer