Too many redirects when trying to access Jackett

[arjones85]

If you are new to Docker or this application our issue tracker is ONLY used for reporting bugs or requesting features. Please use our discord server for general support.

---

Expected Behavior

Browse to Jackett page in Chrome browser works

Current Behavior

Chrome reports "Too many redirects"

Steps to Reproduce

1. Browse to Jackett in Chrome - get too many redirects error

Environment

OS: Windows 10
CPU architecture: x86_64

This used to work fine but no longer does. I've cleared all chrome browsing history but it has not fixed the issue. I can visit Jackett just fine in Firefox, so it seems to be a Chrome issue.

Anyone else experience this problem and have any tips on how to fix it?

[ashtonian]

same issue, running on a swarm host, it keeps trying between /UI/Dashboard and http://10.0.0.3:9117/UI/Login?ReturnUrl=%2FUI%2FDashboard

[dphildebrandt]

Same issue

[ashtonian]

I think this was a temp issue that is resolved with the latest version, try latest image ?

[andregu]

this is happening to me when trying to plug jacket (running on FreeNAS jail) into an Organizr tab

[arjones85]

I solved this by just moving to linuxserver.io's Docker implementation

…

On May 10, 2020, 7:02 PM, at 7:02 PM, "André Guerreiro" ***@***.***> wrote: this is happening to me when trying to plug jacket (running on FreeNAS jail) into an Organizr tab -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #100 (comment)

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jaycollett]

getting the same issue when I just deployed to K3s behind an haproxy an nginx ingress. Version v0.19.84

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[thelamer]

When it comes to simple containers this really is the definition we basically just put dotnetcore blob run some simple permission changes and execute.

I do not believe there is anything docker level that we could do to alleviate this issue. I would try our discord https://discord.gg/YWrKVTn or a community for the orchestration service you are using. I cannot replicate this in plain docker.