Various plugins not working correctly

[Bartype 1]

Hi,

Since i don't know exactly when, but i think one of the more recent updates is have problems with various, but not all plugins. For example the podcasts plugin is only showing an [Add] button, which doesn't do anything when i press on it. All podcast added before are still there but i can't add or config any new ones. The same is true for the CoverArt plugin. There is only a non-responsive [Add] button.

Other plugins like the Server Config Backup don't show any backups which where made before and pressing on the Backup location magnifier doesn't give a response. There are few other plugins which don't work anymore, while others are still working, such as the Addi7ed and Playback reporting plugins.

Removing and re-installing the troublesome plugins doesn't solve the issues...

I am running the latest version for Qnap, 4.6.7.0.

I have added a few images to show how it looks like.

Apart from these plugins, it seems the Emby server is running fine.

Is this a known bug or problem and is there something what i could do to solve this? And hopefully something else of course as completely reinstalling everything...

[Edit] It seems like the scheduled task for the server config backup is still running and putting backups in the location which was configured before. These backups only don't show up in the plugin.

 

 

Thank you in advance,

Bartype

 

 

Edited March 6, 2022 by Bartype

[Happy2Play 9140]

Please post a server log.

How to Report a Problem

 

[Bartype 1]

hereby my server log, thank you in advance for any insights...

embyserver.txt

[Luke 38814]

Hi, you could try clearing browsing data and seeing if that helps.

[Bartype 1]

Hi, thank you for the reply. Tried to clearing browser data, this still doesn't solve the issue. Additionally, now i also can't open the Server Dashboard, while this was still working before clearing the browser data...

 

[Bartype 1]

Hi, is was a little testing around and when i log on to the server locally, all these problems are gone. It seems it's a setting within the reverse proxy... I am going to look there, but good to know there is a workaround!

 

Thank you for your help!

[Luke 38814]

Let us know what you find. Thanks.