Ombi: ERR_TOO_MANY_REDIRECTS after login as admin

[Unimatrix0]

Plex Requests.Net Version:

PlexRequests v1.9.2

Operating System:

Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-38-generic x86_64)

Mono Version:

Mono JIT compiler version 4.6.0 (Stable 4.6.0.245/746756c Wed Sep 21 14:16:42 UTC 2016)

Applicable Logs (from /logs/ directory or the Admin page):

No applicable logs exist

Reproduction Steps:

Log in as admin.

Note: I do normally access PlexRequests through an nginx reverse ssl proxy, but this behavior persists even when connecting directly.

[tidusjar]

That's unusual, can you try and clear your browsers cache or try a different browser to see if it still happens?

[Unimatrix0]

I was able to reproduce the issue on multiple browsers and multiple machines. Clearing cache has no effect. Clearing cookies allows the login page to load again, but the issue reoccurs after login as admin.
Note: Logging in as a non-admin user does not cause the issue.

[csy7550]

I've also had this problem a few times on my Windows setup.. stopped using "remember me" to solve it temporary until I have time to look at solutions and how to reproduce to post here

[csy7550]

Only the two latest versions has given me problems when I think of it

[loeschj]

I am also having this issue with the same scenarios as described above. I didn't have this on the previous version, only 1.9.2

It looks like something is occurring with the search page after login, you are unable to click any of the navigation links, however you can go directly to the /admin url and then settings will load.

[tidusjar]

So just logging in will try and redirect you and then you get the error?

Is this using the /UserLogin or /login page?

[tidusjar]

I cannot seem to reproduce this behaviour.

Can someone please share their Authentication Settings and give me some reproduction steps?

e.g.

• Navigate to /userlogin login with username and password as server admin
• we are now on the search
• Press the admin button
• make sure remember me is not selected
• login as admin

[loeschj]

one additional thing that i just noticed, if you login as a plex user first, then login as admin it appears to be fine.

Steps to recreate redirect loop (have tried in chrome, in-cognito chrome, ie 11, ie 11 in-private browsing, android stock browser)
1) Load Web Page
2) User login landing page appears (http://10.61.15.200:3579/userlogin)
3) Click Admin
4) Admin login page appears (http://10.61.15.200:3579/login?redirect=/userlogin)
5) Enter admin credentials and click login
6) Redirects occur

Workaround Steps
1) Load Web Page
2) User login landing page appears (http://10.61.15.200:3579/userlogin)
3) Login as plex user
4) Search page appears (http://10.61.15.200:3579/search)
5) Click user name drop down then admin
6) Admin login page appears (http://10.61.15.200:3579/login?redirect=/search)
7) Login as admin
8) Navigation and usability not hindered.

I've attached the network debugging

[tidusjar]

I am not seeing this 😠
Can you send me your database please as there might be something there?
[email protected]

[loeschj]

on it's way shortly, just need to transfer and zip

[Unimatrix0]

I can confirm that @loeschj's workaround is successful for me.
@tidusjar, do you just want PlexRequests.sqlite, or are there other files you want?

[Starbix]

I also have this problem and @loeschj 's solution also works for me, do you need more .sqlites?

[fenichelar]

Same here. @loeschj 's solution also worked.

[tidusjar]

Is everyone in a reverse proxy situation?

[Starbix]

I am but it also occured before. I just setup a reverse proxy yesterday

[csy7550]

I'm not..

[fenichelar]

@csy7550 @Starbix do you have a base url set for Plex Requests? If yes, what url? I have a base url of 'request'.

[fenichelar]

These steps provided by @loeschj:
1) Load Web Page
2) User login landing page appears (http://10.61.15.200:3579/userlogin)
3) Click Admin
4) Admin login page appears (http://10.61.15.200:3579/login?redirect=/userlogin)
5) Enter admin credentials and click login
6) Redirects occur

This is how I always access Plex Requests. I would say 90% of the time it works fine. It almost seems like the problem is occuring when I login while someone else is logged in making a request but maybe not.

[tidusjar]

Thanks for the updates guys, Still cannot reproduce in my dev environment (If I can't reproduce it it's difficult to fix). But i'll see what I can do

[Starbix]

@fenichelar I have the same base url

[fenichelar]

@tidusjar Just a hunch, try adding the base url 'request'. And login to admin without already being logged in as a user. If possible, login as a user on another browser. Fingers crossed.

[csy7550]

I'm not using base url

[Unimatrix0]

My base url is 'plexrequests', so it's clearly unrelated to what your base url is.

[ghost]

Hi first thanks for the app :D
2nd. I've had the same issue after upgrading to 1.9.2 so I did a clean install. (same server but deleted the entire folder)
I downloaded the PlexRequests.zip extracted and ran it.
Went to the website and got to the initial setup.
Added the token, setup what you can request. and created an admin account.
After that I got ERR_TOO_MANY_REDIRECTS
Mono V: Mono JIT compiler version 4.6.0 (Stable 4.6.0.245/746756c Wed Sep 21 14:16:42 UTC 2016)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: __thread
SIGSEGV: altstack
Notifications: epoll
Architecture: amd64
Disabled: none
Misc: softdebug
LLVM: supported, not enabled.
GC: sgen

I tested by just logging in as a user. That works fine.

[jamjop]

Happens to me as well. Does not occur if I login as a plex user first, as others have said

[codaamok]

Sorry to add the to the pile of me toos, but me too. @loeschj efforts helped me get in with the workaround

[tidusjar]

Did anyone have this problem on 1.9.1? Trying to narrow down what could have caused it

[codaamok]

Reloading v1.9.1 now using same Plex srv and I'll also try same db files too. I have a feeling I remember seeing it in 1.9.1 but not 100% sure.

[codaamok]

Problem repeatable in v1.9.1 in new directory /opt/plexrequests.net2/ so blank db but linked to same PMS, anything else I can do let me know

[tidusjar]

What about 1.9.0? :)

[codaamok]

Problem does not exist in 1.9.0.

I thought it may have been an authentication thing between plex account & admin account so I tried creating in 1.9.0 and 1.9.2 admin account with same credentials as plex account but made no difference - I'm sure you'll have better understanding of how that works but it was something I tried.

[tidusjar]

Thanks, that does help a lot.

[Cylae]

Same issue here :(
Debian 8.5 - Nginx

[jamjop]

Ok so I was having this issue and some other issues. I did some investigating and my installed mono version was 4.6. I downgraded to 4.2.3 and all the issues went away, including the redirect issue. The other issue I was having was that CP requests weren't going through, I was getting some sort of API error. I think it's safe to say that Plexrequests.net 1.9.2 is not compatible with mono 4.6. I'm extremely pleased with the performance of plex requests now

I'm on Ubuntu 16.0.4

[tidusjar]

Wow. It didn't even cross my mind that mono could have been an issue here. I wonder why that is... It must be a mixture of my recent changes with mono's new version causing the issue and why I couldn't reproduce it! (Running windows so no need for mono)...

[codaamok]

Nice work @noahruss

[ghost]

yes confirmed. going back to 4.2.3 works.
for those who don't know. On Debian Wheezy +
remove Mono and edit your source list file.
use this entry
deb http://download.mono-project.com/repo/debian wheezy/snapshots 4.2.3/main
deb http://download.mono-project.com/repo/debian wheezy-libjpeg62-compat main
and install again.

Let us know if you are able to make it work on a newer mono version :D

[rogueosb]

Docker container should be reverted to 4.2.3 now.

[tidusjar]

Thanks!

[Majawat]

I am running Windows and have the issue. Not sure if that supports the Mono idea.

[Unimatrix0]

Rolling back to Mono 4.2.3 worked for me.
@TheBlackDrak3's instructions are not quite correct.
Most significantly, the first apt source should be:
deb http://download.mono-project.com/repo/debian wheezy snapshots/4.2.3/main
not
deb http://download.mono-project.com/repo/debian wheezy/snapshots 4.2.3/main
and the 2nd source depends on your linux flavor.
Follow the instructions here.

Also, if you've previously installed mono-complete, you'll need to manually uninstall the higher versioned dependencies before you'll be able to install mono 4.2.3.

[ghost]

Actually @Unimatrix0 I could not install with that rep. That is why I changed mine to 4.2.3 instead of /4.2.3
This was my experience with Debian Jessie at least.
I was not able to run apt-get update successfully with the info from Mono site.
If I remember correctly i got an error saying "expected snapshots/4.2.3, got wheezy" more or less.
So using deb http://download.mono-project.com/repo/debian wheezy/snapshots 4.2.3/main worked for me.

[porksandwich]

@Auwen I am also running on Windows and have this issue.

[csy7550]

Also running Windows and got this issue.

[tidusjar]

@csy7550 and @porksandwich you guys behind a reverse proxy?

[csy7550]

No reverse proxy.. I think it has something to do with not logging out correctly (just closing the browser and not using the logout button) on multiple devices, but I could be wrong! I can reproduce this every time by selecting "remeber me", not logging out with the button on the gui and trying to login from another device at another location

[fenichelar]

@csy7550 I think you are onto something. Signing in with different URLs on the same device (remote and local address) seems to be the same. This makes sense as the browser separates the cookies, cache, etc. which is like signing in with a new device.

[loeschj]

I assume you expected this but it's still occurring with 1.9.3, I even wiped the directory and extracted the Zip.

[porksandwich]

@tidusjar I am behind a reverse proxy.

[KamakaziSanne]

Same Problem here on windows, temp fix by deleting cookies, and not signing in anymore with "remember me".

[Starbix]

Thanks so much for the fix!!

[tidusjar]

No problem, I guess you guys can upgrade your mono again, not sure how that 'fixed' it now I have found the culprit in the code!