[SOLVED] SameSite-related errors in pleroma-fe admin page

Support
1

Hi!

After the latest update of 2023.02 I am getting errors on the admin page of pleroma-fe. Any sub-page I want to access produces this error:

"Request failed with status code 404 - Not implemented"

Looking with the DOM inspector, I see a bunch of these other errors:

Content Security Policy: The page’s settings blocked the loading of a resource at inline (“style-src”).

Some cookies are misusing the recommended “SameSite“ attribute 2
Cookie “Admin-Token” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite js.cookie.js:92
Cookie “Auth-Host” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite

I am using Firefox dev edition v110.0b9 (64-bit) and Chromium v110.0.5481.100.

Could anyone help? :slight_smile:

2

Did you also update the front end? If not, that could explain these errors. Instructions for updating should be in the docs.

3

Yup! I updated pleroma-fe but totally forgot about admin-fe… Thanks!

1 Like
4

Sorry to resurrect this, but I’m seeing the same errors after upgrading yesterday to stable: akkoma itself, and both pleroma-fe and admin-fe.

In addition I see this error in the browser’s console:
The resource from “https://social.tenak.net/static/font/css/animation.css” was blocked due to MIME type (“text/html”) mismatch (X-Content-Type-Options: nosniff)

What can I check for to try to find the cause? Thanks!

5

Your instance seem to be offline.

6

It’s not, although I’ve been having some troubles with my DNS provider this days, so maybe it’s not resolving on your side…

I can use it right now from Husky.

Thanks

1 Like