Activity feed issues after the latest update

[privaty 4]

Hello everyone

Since the most recent update (4.9.3.0) I have been experiencing an issue where user activities are not being displayed correctly. When users log in their status is not properly recorded in the activity feed. It seems that the system is no longer tracking these logins in real time.

Furthermore there is a specific bug regarding video playback. When a user is currently watching a video the activity feed incorrectly states that they have finished watching it even though the video is still running.

Has anyone else encountered these problems or is there a known fix to ensure activities are tracked accurately again?

I did not have this problem in the previous version 4.9.1.90. 

Thank you for your assistance.

[brothom 177]

@privatymight it be the case that your issue relates to this one: 

If you're viewing the feed from within the same network as the server, try viewing it from outside of that network instead.

[privaty 4]

@brothomIt sounds similar in itself. When a user reports they are online, I don't see them authenticated in real-time on the server in the dashboard, or what is playing on the server. It's very strange; I see my (local) feeds, but not those of outside users.

Edited January 27 by privaty

[brothom 177]

1 hour ago, privaty said:

@brothomIt sounds similar in itself. When a user reports they are online, I don't see them authenticated in real-time on the server in the dashboard, or what is playing on the server. It's very strange; I see my (local) feeds, but not those of outside users.

Perhaps you can try logging into your server via your mobile internet to see if that helps the issue. if it does, your issue is similar to the bug I reported before.

If that doesn't help, we'll have to look elsewhere.

[privaty 4]

@brothomWhether I log in via app or web interface, I see the same activity view in dashboard. I will soon enable the debug log protocol to see if it causes an error message. I use a reverse proxy with HTTPS. As I said, the previous version has everything logged cleanly. 

[Luke 42077]

3 hours ago, privaty said:

@brothomWhether I log in via app or web interface, I see the same activity view in dashboard. I will soon enable the debug log protocol to see if it causes an error message. I use a reverse proxy with HTTPS. As I said, the previous version has everything logged cleanly. 

Maybe you are blocking something that is needed for it to work. I would suggest comparing your reverse proxy settings to this: 

 

[privaty 4]

@LukeVery interesting article, also to read about NPM, which I use. I'll do these advanced settings there. Thank you for the quick response. 

[Luke 42077]

Please let us know how things go. Thanks.

[privaty 4]

@LukeOkay, great. Yes, as soon as I've tested it, I'll give you an update.

Just a quick update regarding the GPU transcoding: Since the new update, I had to adjust the GIDLIST in the Docker configuration from 2 to 44, 105.
Previously, the logs showed 'Driver: empty' because the container lacked the necessary permissions to access the hardware interface.

After updating the group IDs, transcoding is stable again, which I verified via SSH using intel_gpu_top.
I assume this permission requirement is a known issue for Docker setups on this platform.

[privaty 4]

@LukeI've tried everything in NPM (on/off/advanced) , but I can only see locally when I log in or via the web browser. However, when users log in via LG TV Emby (Android 3.5.28, Emby for LG 1.0.50), I can't see it.

With this settings, I can at least see when the user has started and finished a video, but nothing more.
Before the update, I could see how users authenticated themselves.

With these settings, I can at least see that they have started and finished a video.
Do you have a better idea, or should we wait for the new update?
 

Setting	Status
Websockets Support	ON
Block Common Exploits	OFF
HTTP/2 Support	OFF

 

Setting	Status
Force SSL	ON
HSTS Enabled	OFF
HTTP/2 Support	OFF
HSTS Subdomains	OFF

Edited February 3 by privaty
translate

[Luke 42077]

How does your config compare to the one I linked to?

[privaty 4]

@LukeYes, I tried it too. Much of it is unnecessary. For example, Gzip is enabled by default, but it does not affect login activities.
I added a few, but it doesn't matter. I can only see the user's activities when they start and finish a movie, but I can't see the login authentication where you can also see the IP address of the login. Before the update, I had few settings and it worked. It's only since the update that the real-time activities no longer work when a user logs into the server.

I have now fine-tuned the most important ones, but nothing is the way it was before:

location / {     tcp_nodelay on;     sendfile off;     proxy_buffering off;          proxy_connect_timeout 1h;     proxy_send_timeout 1h;     proxy_read_timeout 1h;     proxy_set_header Range $http_range;     proxy_set_header If-Range $http_if_range;     proxy_hide_header X-Powered-By;      proxy_http_version 1.1;     proxy_set_header Upgrade $http_upgrade;     proxy_set_header Connection "upgrade";     proxy_set_header Host $host;     proxy_set_header X-Real-IP $remote_addr;     proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;     proxy_set_header X-Forwarded-Proto $scheme;     proxy_redirect off;     add_header 'Referrer-Policy' 'origin-when-cross-origin';     add_header X-Frame-Options "SAMEORIGIN" always;     add_header X-Content-Type-Options "nosniff" always;     add_header X-XSS-Protection "1; mode=block" always;     proxy_pass http://192.168.1.111:8096; }

 

[Neminem 1516]

Try this.

 

[Luke 42077]

Maybe your proxy is configured correctly. Did they actually login and authenticate? That's when you would see that activity. If they authenticated in the past and they're just returning to that previous session, then you won't see it.

[privaty 4]

@LukeAh, if they have authenticated in the past, it will no longer be displayed . Thank you guys, but even so, these additional settings certainly provide greater stability and security.

[Luke 42077]

1 hour ago, privaty said:

@LukeAh, if they have authenticated in the past, it will no longer be displayed . Thank you guys, but even so, these additional settings certainly provide greater stability and security.

If they logout then they will have to reauthenticate and you will see it again.

So yes this was changed although it didn't happen recently. I'm pretty sure it's been a couple years since we did that. The problem before is that it was just filling the activity log needlessly every time restart an app, load a new browser tab, etc.

[privaty 4]

@LukeIt makes sense not to overload the activity log unnecessarily