[GH-ISSUE #252] [BUG] "The page isn’t redirecting properly" after heroku quick deploy #173

New issue

Closed

opened 2026-02-25 20:35:05 +03:00 by kerem · 3 comments

kerem commented

2026-02-25 20:35:05 +03:00

Owner

Originally created by @trumad on GitHub (Apr 1, 2021).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/252

Describe the bug
Firefox shows "The page isn’t redirecting properly", and Chrome shows "mackfindus.herokuapp.com redirected you too many times." when using my heroku instance (https://mackfindus.herokuapp.com/)

To Reproduce
Steps to reproduce the behavior:

Go to https://mackfindus.herokuapp.com/
Note the browser error

Deployment Method

[ X ] Heroku (one-click deploy)
Docker
run executable
pip/pipx
Other: [describe setup]

Version of Whoogle Search

Latest build from [source] (i.e. GitHub, Docker Hub, pip, etc)
Version [version number]
[ X ] Not sure (the beta version)

Desktop (please complete the following information):

OS: Mac OS
Browser: Firefox & Chrome
Latest

Smartphone (please complete the following information):

Device: Motorola G9
OS: Android 10
Browser: Iceraven (firefox fork for Android)
Version: Latest

Additional context

I deleted my original heroku app to deploy the beta version from scratch on the same appname/subdomain, to try to fix https://github.com/benbusby/whoogle-search/issues/249. I just left the default options as they were, and it deployed successfully, but now it's redirecting in a loop. I also installed two brand new instances using the heroku quick deploy button on https://github.com/benbusby/whoogle-search/tree/heroku-app-beta and they are behaving the same way. I installed an EU and a US version. I tried clearing cookies, and I tried adding the CONSENT cookie manually, but neither helped. I'm pretty sure the CONSENT cookie doesn't need to be added client-side on the heroku webpage, but I was desperate!

Originally created by @trumad on GitHub (Apr 1, 2021). Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/252 **Describe the bug** Firefox shows "The page isn’t redirecting properly", and Chrome shows "mackfindus.herokuapp.com redirected you too many times." when using my heroku instance (https://mackfindus.herokuapp.com/) **To Reproduce** Steps to reproduce the behavior: 1. Go to https://mackfindus.herokuapp.com/ 2. Note the browser error **Deployment Method** - [ X ] Heroku (one-click deploy) - [ ] Docker - [ ] `run` executable - [ ] pip/pipx - [ ] Other: [describe setup] **Version of Whoogle Search** - [ ] Latest build from [source] (i.e. GitHub, Docker Hub, pip, etc) - [ ] Version [version number] - [ X ] Not sure (the beta version) **Desktop (please complete the following information):** - OS: Mac OS - Browser: Firefox & Chrome - Latest **Smartphone (please complete the following information):** - Device: Motorola G9 - OS: Android 10 - Browser: Iceraven (firefox fork for Android) - Version: Latest **Additional context** I deleted my original heroku app to deploy the beta version from scratch on the same appname/subdomain, to try to fix https://github.com/benbusby/whoogle-search/issues/249. I just left the default options as they were, and it deployed successfully, but now it's redirecting in a loop. I also installed two brand new instances using the heroku quick deploy button on https://github.com/benbusby/whoogle-search/tree/heroku-app-beta and they are behaving the same way. I installed an EU and a US version. I tried clearing cookies, and I tried adding the CONSENT cookie manually, but neither helped. I'm pretty sure the CONSENT cookie doesn't need to be added client-side on the heroku webpage, but I was desperate!

kerem

2026-02-25 20:35:05 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 20:35:05 +03:00

Author

Owner

@Hunam6 commented on GitHub (Apr 1, 2021):

https://github.com/benbusby/whoogle-search/issues/243#issuecomment-811773944

@Hunam6 commented on GitHub (Apr 1, 2021): https://github.com/benbusby/whoogle-search/issues/243#issuecomment-811773944

kerem commented

2026-02-25 20:35:05 +03:00

Author

Owner

@trumad commented on GitHub (Apr 1, 2021):

My workaround for this is to deploy an old version on a US heroku instance, using this quick deploy link: https://heroku.com/deploy?template=https://github.com/benbusby/whoogle-search/tree/heroku-app

@trumad commented on GitHub (Apr 1, 2021): My workaround for this is to deploy an old version on a US heroku instance, using this quick deploy link: https://heroku.com/deploy?template=https://github.com/benbusby/whoogle-search/tree/heroku-app

kerem commented

2026-02-25 20:35:05 +03:00

Author

Owner

@benbusby commented on GitHub (Apr 1, 2021):

Fixed now on heroku-app-beta

@benbusby commented on GitHub (Apr 1, 2021): Fixed now on `heroku-app-beta`