Plex Friend not being imported about ombi HOT 15 CLOSED

That’s helpful, thank you.

from ombi.

That is odd.

I would have expected some logs when running the importer to tell you why it didn’t import.

Can you run the importer manually and check the logs?

from ombi.

There are no logs at all generated when I run the User Importer.

This is the last entry of the logs before and after I run the importer, just for reference now it is 15:05. This is unrelated with the import and no extra logs are generated.

2023-07-25 13:37:51.522 +02:00 [ERR] Could not test Plex
System.Net.Http.HttpRequestException: Connection refused (192.168.0.231:17878)
---> System.Net.Sockets.SocketException (111): Connection refused
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
[...]

I've also intercepted the request I'm doing with a proxy:

POST /ombi/api/v1/Job/plexUserImporter/ HTTP/2
Host: ombi.estebanell.com
Cookie:
Content-Length: 187
Sec-Ch-Ua: "Not/A)Brand";v="99", "Google Chrome";v="115", "Chromium";v="115"
Accept: application/json, text/plain, /
Content-Type: application/json
Sec-Ch-Ua-Mobile: ?0
Authorization:
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36
Sec-Ch-Ua-Platform: "macOS"
Origin: https://ombi.estebanell.com
Sec-Fetch-Site: same-origin
Sec-Fetch-Mode: cors
Sec-Fetch-Dest: empty
Referer: https://ombi.estebanell.com/ombi/Settings/UserManagement
Accept-Encoding: gzip, deflate
Accept-Language: en-ES,en;q=0.9,ca-ES;q=0.8,ca;q=0.7,es-ES;q=0.6,es;q=0.5,en-GB;q=0.4,en-US;q=0.3

{"headers":{"normalizedNames":{},"lazyUpdate":[{"name":"Content-Type","value":"application/json","op":"s"}],"headers":{},"lazyInit":{"normalizedNames":{},"lazyUpdate":null,"headers":{}}}}

And what I get in response is:

HTTP/2 200 OK
Server: nginx/1.25.1
Date: Tue, 25 Jul 2023 13:02:58 GMT
Content-Type: application/json; charset=utf-8
Content-Length: 4
Access-Control-Allow-Credentials: true
Access-Control-Allow-Origin: https://ombi.estebanell.com
Vary: Origin
Strict-Transport-Security: max-age=31536000

true

from ombi.

I have the same problem. No logs too

from ombi.

same problem here have it for a few days now reinstalled everything on docker even have used new configs for plex and ombi but it will not import new registerd users that have signed up the last 3 months or so checked users in yml no difference with other users only thing making them differend is there sign up date

from ombi.

from ombi.

Can someone send me the output from this call either via email [email protected] or on Discord

https://plex.tv/api/users?X-Plex-Token=PLEX_TOKEN

You can find your PLEX_TOKEN here: https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/

from ombi.

I have the same issue, no logs are generated when the importer function is called.
I can still see the missing users using this link: https://plex.tv/api/users?X-Plex-Token=PLEX_TOKEN

from ombi.

same issue. super weird. wife was in my ombi until some seemingly random point a day or two ago. only things i recall changing in the last few days was removing some items from her watchlist on plex. (watchlist request is set up)

now she's not there and no matter how many times or ways i try to run the importer she isnt coming back lol.

everyone else seems untouched which leads me to believe it has to have something to do with having removed those watchlist items from my tvs plex client.

already tried removing/re-adding the server thinking maybe some kinda token thing but it found the same server, same token, no bueno.

have a few errors in my logs but unsure which if any are relevant. gonna pastebin em momentarily.

so there was a whole lot of this

https://privatebin.net/?477f25e8cdf5c5b4#HFRvaiY2DmwfdisNLqPQ1vsM7xkNoLwG2HZjDWMwAEjP

and this

https://privatebin.net/?8deb8f1b64b6fd47#9W8xVUgAxGmkEFHuVge8HBbVxmCQb83x2u61z8TXukFV

followed by these errors

1. https://privatebin.net/?69a50b71bb5150d4#7mENyTVXz6qBsCjgk9ZYyssoPMTGmii2KwfYV3dju6Gm

2. https://privatebin.net/?5b45133605fcce00#D3CuhLwiZSEBN3daNwPipN1cZuKSL2eh5k8Kn7XwXHaB

3. https://privatebin.net/?a5fdcbacf99a676a#FVMAMvY4PFrrQJ7bViXrmJBfEhWwvLnVgZw8HmH3Jjde

with any luck something there will be helpful. also worth mentioning I ran that call and it listed everyone in my plex. 3 people are not imported into ombi. All 3 are my family members. my 2 kids which are managed users so they were already not being imported by design. my wife however we created a plex account for her intentionally to replace the managed one she had. she was imported fine until... she wasnt :p

am on windows
4.43.2 being started ala scheduled task. updated a few times in a few days though as releases were made available. at one point to address the admin user being purged bug, then i believe there was another release after that before the current. she could have poofed at any point in there, i wasnt checking unfortunately.

looking at old database backups apparently it happened at 12:00AM on the 21st. unsure if that coincided with 4.43.2 perhaps. maybe i ought to try a roll back and re import. I'm waaaaay too stupid to edit her back in manually without probably blowing the db to bits im sure.

UPDATE: so i downgraded to 4.43.1 and the importer worked fine, brought her back. its something introduced in 4.43.2. disabled plex user cleanup but afraid to roll back up in the meantime just in case it has zero to do with that setting.

from ombi.

Can someone try the new build?

from ombi.

Hey, just tried the new build and the problem is still there. Also still no logs.

from ombi.

@klepp0906 are you able to send me the output from the API call?

from ombi.

sure, sent it over in disc

from ombi.

Ok, found the issue.

The Plex API can report users as "Home" users if they were a pure home user and then converted to a non-managed account.
I recently added a check to not add home users by checking the HomeUser attribute from the API, thinking that it would only be true for pure home users.

I've now removed that check and it will all work as it previously did.

from ombi.

Hey @tidusjar, I can confirm that it works, I'll close the issue. Thank you very much!

from ombi.