-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Too Many Redirects #742
Comments
To provide a small update to this. Looks like I was able to access the app and login (kinda) by going to Still getting some strange behavior, like my username didn't get loaded in and the app doesn't load correctly on refresh. So I am still investigating. Still open to any ideas. |
Sorry I haven't been able to reply sooner (I'm at the airport), but I promise to get back to this soon. If I don't, just @ me |
I also have a list of behavior that I find strange, is maybe a bug, or just missing. It's difficult for me to tell if it is a configuration error or just a bug. Anyway, here's the list.
I wasn't sure if I should make different tickets for this stuff so I just stuck it here. Thanks! |
Okay wow, that's a lot that I somehow never encountered. For each issue, would appreciate a repro/logs. |
I do not see this in my own deployment. Without the HA/reverse proxy setup, I cannot reproduce this issue or even attempt to solve it. Please feel free to provide it and I will reopen it. |
I am getting a similar issue in my deployment as well. Have you figured it out? |
Hi, no reproduction has been provided by either you or the original poster. I cannot just "guess" what could be wrong with your setups, or where the problem might lie, when I don't know anything about how it is set up and being used, or how I can reproduce the problem myself. |
Is there anything in Specific I could provide to help? |
I'd need an exact, minimal reproduction (meaning I can reproduce it myself) of how you get that error in a consistent manner so that I can investigate. Just posting your setup with a billion configuration isn't going to help me figure out exactly what has gone wrong and what caused it. |
I am using EasyPanel.io, which is just A docker management Panel, it uses Traefik as a reverse proxy with a Lets Encrypt SSL Images Used Using a FQDN with Https in the ENV I am getting all the same errors above |
You seem to be very new to this, so try to think of it from my perspective - what would it take for me (you) to diagnose the problem? "I am using EasyPanel.io" -> tells me nothing about how the Docker container is actually being run, with what network and DNS configurations, with what volumes, with what environment variables, with what databases setup in which way, etc. "uses Traefik as a reverse proxy" -> again, tells me nothing about traefik setups or redirects or routing... and so on and so forth (not to mention the fact that the way you're doing it, I cannot even reproduce your setup on my own). Furthermore, even if you "dump" your reproduction, since there will be a million variables at play (given those variables would be specific to your setup), I cannot narrow it down to anything beyond "it doesn't work". Start from the bottom - what is the smallest and simplest config (i.e. with the fewest external moving parts, such as your DNS setup and traefik and your hosting provider) that causes you to have such errors? |
Greetings-
I am attempt to deploy this into production and getting
ERR_TOO_MANY_REDIRECTS
when I attempt to go to the homepage in my browser.I am deploying to a Docker Swarm cluster behind an HA Proxy load balancer. Do you have any thoughts on how to fix this? Here is my docker stack file:
Blink docker logs:
I attempted to set more verbose logging by setting
LOG_LEVEL
in the blink environment variable section above todebug
but that didn't seem to change any output.I attempted to set the
HOMEPAGE
variable tohttp://my_docker_node.tld:3000
and bypass my proxy and I am still getting similar behavior, so I don't think the HA Proxy is messing with it. Seems like either a Blink configuration error on my part or a bug.The text was updated successfully, but these errors were encountered: