I have a user who is getting this message when they try to log into my Pickaxe studio. This is happening after multiple password reset attempts. They are on IOS and Chrome.
Everything is working for other users.
Hi @dougfresh ,
Thank you for the details and for the screenshot.
I tested jpmanna.com on my side, and the page loads normally, so this looks like an issue isolated to your users’ setup.
In most cases, “ERR_TOO_MANY_REDIRECTS” happens when the browser gets stuck in a redirect loop due to cached site data or an outdated login cookie.
Could you please tell your user to try the steps below and then attempt to log in again?
- Clear site data for jpmanna.com (cookies and cache) and then close and reopen Chrome.
- Try in an Incognito window after clearing cookies.
- Temporarily disable any VPN, iCloud Private Relay, and any content blockers, then retry.
- If you have any browser extensions enabled, please disable them temporarily and test again.
- Try a different browser or a different device to confirm whether it is tied to the current browser session.
Please let me know how it goes after trying these steps.
Hi @dougfresh ,
I wanted to follow up to see if your user has had a chance to try clearing their cookies, browser cache, and site data, and whether any of the suggested troubleshooting steps helped resolve the problem.
Our engineering team has recently deployed a change intended to address this issue. However, since it seems to occur only for certain users, it can be difficult to fully eliminate.
If your user is still experiencing the problem, please let us know. Any additional details you can share will help us continue our investigation.
I have no additional details. The user is 78 years old. It would be very difficult to get more info ![]()
HE is using another computer as a solution. I believe it is a chrome setting issue.
Hi @dougfresh ,
Thank you for your update. Since using a different computer resolves the issue, it is likely related to cookies or browser data on the original device. Our engineering team has pushed a fix intended to address this error and prevent it from recurring.
If your user experiences the problem again, please let us know, and we will continue to investigate further. Thank you for your patience as we work to improve this experience.

