Upgraded jellyfin container, broke SSO and cannot upgrade SSO

[alaricljs]

Describe the bug
I upgraded my jellyfin container to 10.11.0 from something in the region of 10.8, I don't know because I didn't write it down and it's nowhere to be found in the logs.

SSO plugin 3.5.2.4 shows "Unsupported" and hitting Install on 4.0.0.3 gives only "An error occurred while installing the plugin" at the top of the page after confirming installation.

To Reproduce
Covered above I think?

Expected behavior
Useful logs at least.

Configuration

<?xml version="1.0" encoding="utf-8"?>
<PluginConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <SamlConfigs />
  <OidConfigs>
    <item>
      <key>
        <string>authentik</string>
      </key>
      <value>
        <PluginConfiguration>
          <OidEndpoint>https://auth.enlj.com/application/o/jellyfin/.well-known/openid-configuration</OidEndpoint>
          <OidClientId>redacted3</OidClientId>
          <OidSecret>redacted4</OidSecret>
          <Enabled>true</Enabled>
          <EnableAuthorization>true</EnableAuthorization>
          <EnableAllFolders>true</EnableAllFolders>
          <EnabledFolders />
          <AdminRoles>
            <string>jellyfin_admin</string>
            <string>jellyfin_admins</string>
          </AdminRoles>
          <Roles>
            <string>jellyfin_user</string>
            <string>jellyfin_users</string>
          </Roles>
          <EnableFolderRoles>false</EnableFolderRoles>
          <EnableLiveTvRoles>false</EnableLiveTvRoles>
          <EnableLiveTv>false</EnableLiveTv>
          <EnableLiveTvManagement>false</EnableLiveTvManagement>
          <LiveTvRoles />
          <LiveTvManagementRoles />
          <FolderRoleMappings />
          <RoleClaim> groups</RoleClaim>
          <OidScopes>
            <string>["groups"]</string>
          </OidScopes>
          <DefaultProvider>authentik</DefaultProvider>
          <SchemeOverride>https</SchemeOverride>
          <NewPath>true</NewPath>
          <CanonicalLinks>
            <item>
              <key>
                <string>redacted</string>
              </key>
              <value>
                <guid>25086c2a-9f3a-4b27-9c07-5c34b74754ee</guid>
              </value>
            </item>
            <item>
              <key>
                <string>redacted2</string>
              </key>
              <value>
                <guid>4b41f0a6-7c97-4244-a681-c1c1a355270b</guid>
              </value>
            </item>
          </CanonicalLinks>
          <DisableHttps>false</DisableHttps>
          <DoNotValidateEndpoints>false</DoNotValidateEndpoints>
          <DoNotValidateIssuerName>false</DoNotValidateIssuerName>
        </PluginConfiguration>
      </value>
    </item>
  </OidConfigs>
</PluginConfiguration>

Versions (please complete the following information):

• OS: Debian 13 (the docker host) Arch (my desktop)
• Browser: Firefox
• Jellyfin Version: 10.11.0
• Plugin Version: 3.5.2.4 / 4.0.0.3

[9p4]

Please check your browser console logs when attempting to install the plugin.

[alaricljs]

Looks like a 404 response to: https://jellyfin/Packages/Installed/SSO-Auth?assemblyGuid=505ce9d1d91642fa86ca673ef241d7df&version=4.0.0.3&repositoryUrl=https://raw.githubusercontent.com/9p4/jellyfin-plugin-sso/manifest-release/manifest.json

curl from the docker host and within the container does not 404 against the repository URL.

[9p4]

Please uninstall the plugin, delete the plugin folder, then restart Jellyfin. Do not delete the configuration. Then install the plugin.

[indykoning]

I have the same issue, it seems to also happen to the ODPS extension for me which oddly enough is in the Jellyfin plugin repo itself.
Feels like it may be a Jellyfin bug

[alaricljs]

That did the thing for me, thanks

[tuetenk0pp]

I also had to delete the empty plugin folder manually for the update to work - hope this helps

[Externalnet]

I also had to delete the empty plugin folder manually for the update to work - hope this helps

Can you please be a bit more specific how I can fix this. What are the exact steps I have to take ?

[tuetenk0pp]

I also had to delete the empty plugin folder manually for the update to work - hope this helps

Can you please be a bit more specific how I can fix this. What are the exact steps I have to take ?

I had to uninstall the Plugin from the Web UI and remove the plugin folder (for some reason there remained an empty plugin folder in /config/plugins). The path for the plugin folder varies depending on your Jellyfin installation. Since I use Docker, I also deleted the container (just to be sure).

After this, I was able to install the SSO plugin through the web UI on the new Container.

[Diagonet]

I manage to install by deleting it too but has anyone managed to make it work with Authelia? It seems to swap 'token_endpoint_auth_method' between 'client_secret_post' and 'client_secret_basic'. When I set it to 'client_secret_post' on Authelia it fails right away, when I set it to 'client_secret_basic' it gets to the consent screen then errors. Not sure if I should open an issue for this but it seems to be using both auth methods atm.
EDIT: Disabling Pushed Authorization works I suppose.

[9p4]

Please refer to #305 for Authelia issues.

[9p4]

I'll close this issue in a few weeks once everyone's upgraded to 10.11.

[Porthorion]

Okay maybe I am illiterate or something, but I genuinely don't understand how to fix this problem.

It keeps taking me to a page that says
Error processing request.
and the URL looks like this:
https://jellyfin.domain.com/sso/OID/start/pocketid?

I don't know what to do

EDIT:

I forgot to mention I already tried the Plugins folder trick (but I have many plugins installed so I couldn't just delete the entire folder either, I confirmed there was no ghost folder for the SSO plugin)

If I am missing something I am open for suggestions.

EDIT 2:
okay I changed nothing, kept the plugin installed, went to sleep, woke up, now it works flawlessly... What??

Well, I am not complaining. It works.