[bug] Reloading on /main/friends page results in white page / Logged out users cannot log into Akkoma at all #429
Labels
No Label
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#429
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Your setup
Docker
Extra details
Docker image: teslamint/akkoma:develop
Version
b98fe4476cPostgreSQL version
12-alpine
What were you trying to do?
Press the Chrome's Refresh button while viewing /main/friends page to see latest posts.
What did you expect to happen?
Screen to be redrawn with latest posts updated on the Akkoma webpage.
What actually happened?
Screen goes fully white and stays white. Multiple attempts to reload result in the same thing. The one workaround I've discovered is if I am logged in and delete /main/friends from the URL and just go to the URL for my Akkoma installation, it will redirect to /main/friends and this time will refresh properly.
Logs
Severity
I cannot use it as easily as I'd like
Have you searched for this issue?
I decided to try this under Firefox to see if this is a Chrome-specific issue. I was planning on logging into the instance as I had never used Firefox with my Akkoma instance, however I am unable to use Akkoma under Firefox at all whatsoever. Going to my instance URL redirects me to /main/public which is blank, just like reloading the /main/friends page was under Chrome.
Log output from Firefox:
This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. public
Cyclic depenency in topoSort, ignoring 2 theme_data.service.js:120:14
Content Security Policy: The page’s settings blocked the loading of a resource at inline (“style-src”). pinch-zoom.es.js:20:9
Content Security Policy: The page’s settings blocked the loading of a resource at inline (“style-src”). pinch-zoom.es.js:26:10
Service worker registration succeeded:
ServiceWorkerRegistration { installing: null, waiting: null, active: ServiceWorker, navigationPreload: NavigationPreloadManager, scope: "https://social.zerojay.com/", updateViaCache: "imports", onupdatefound: null, pushManager: PushManager }
main.js:58:14
Cookie “userLanguage” 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.mjs:75:28
Content Security Policy: The page’s settings blocked the loading of a resource at inline (“style-src”). index.es.js:458:16
Can't load stickers after_store.js:243:12
SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data after_store.js:244:12
Uncaught (in promise)
Object { name: "StatusCodeError", statusCode: 403, message: "403 - {"error":"Invalid credentials."}", error: {…}, options: {…}, response: Response, stack: "" }
2
Content Security Policy: The page’s settings blocked the loading of a resource at inline (“style-src”). style_setter.js:12:2
Uncaught (in promise) TypeError: i is null
p style_setter.js:15
setTheme instance.js:218
style_setter.js:15:2
Uncaught TypeError: t[o] is undefined
determineVisibleStatuses timeline.js:209
timeline.js:209:16
Chrome in Incognito mode (not logged in) shows the same behavior as Firefox - fully white screen on /main/public resulting in Akkoma being unusable. Logs:
social.zerojay.com/:1 Refused to apply style from 'https://social.zerojay.com/static/font/css/animation.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
social.zerojay.com/:1 Refused to apply style from 'https://social.zerojay.com/static/font/css/fontello.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
pinch-zoom.es.js:20 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'self' 'nonce-Pn9b6T0ZeWyJDXX'". Either the 'unsafe-inline' keyword, a hash ('sha256-47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU='), or a nonce ('nonce-...') is required to enable inline execution.
(anonymous) @ pinch-zoom.es.js:20
pinch-zoom.es.js:26 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'self' 'nonce-Pn9b6T0ZeWyJDXX'". Either the 'unsafe-inline' keyword, a hash ('sha256-ckBjfoG7kslbgdFGbtLBGmAanswNCGTikvkqitngKfs='), or a nonce ('nonce-...') is required to enable inline execution.
(anonymous) @ pinch-zoom.es.js:26
index.es.js:458 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'self' 'nonce-Pn9b6T0ZeWyJDXX'". Either the 'unsafe-inline' keyword, a hash ('sha256-MBVp6JYxbC/wICelYC6eULCRpgi9kGezXXSaq/TS2+I='), or a nonce ('nonce-...') is required to enable inline execution.
(anonymous) @ index.es.js:458
/api/v1/mutes/:1 Failed to load resource: the server responded with a status of 403 ()
/api/v1/announcements:1 Failed to load resource: the server responded with a status of 403 ()
/api/v1/announcements:1 Failed to load resource: the server responded with a status of 403 ()
/api/v1/pleroma/admin/reports:1 Failed to load resource: the server responded with a status of 403 ()
after_store.js:243 Can't load stickers
(anonymous) @ after_store.js:243
after_store.js:244 SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON
(anonymous) @ after_store.js:244
errors.js:12 Uncaught (in promise) q
errors.js:12 Uncaught (in promise) q
style_setter.js:12 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'self' 'nonce-Pn9b6T0ZeWyJDXX'". Either the 'unsafe-inline' keyword, a hash ('sha256-47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU='), or a nonce ('nonce-...') is required to enable inline execution.
p @ style_setter.js:12
style_setter.js:15 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'toString')
at p (style_setter.js:15:14)
at instance.js:218:13
timeline.js:209 Uncaught TypeError: Cannot read properties of undefined (reading 'getBoundingClientRect')
at Proxy.determineVisibleStatuses (timeline.js:209:39)
main.js:58 Service worker registration succeeded: ServiceWorkerRegistration
public:1 Refused to apply style from 'https://social.zerojay.com/static/font/css/fontello.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
public:1 Refused to apply style from 'https://social.zerojay.com/static/font/css/animation.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
[bug] Reloading on /main/friends page results in white pageto [bug] Reloading on /main/friends page results in white page / Logged out users cannot use Akkoma at all[bug] Reloading on /main/friends page results in white page / Logged out users cannot use Akkoma at allto [bug] Reloading on /main/friends page results in white page / Logged out users cannot log into Akkoma at allupdate your frontend