[v4] Randomly unauthenticated error about kirby HOT 6 CLOSED

@bnomei Could you please post this as a new issue. It's hard to keep track of closed issues and I think mixing up topics a bit. Thank you 🙏

decided to post final findings here since the issue is resolved for me now.

from kirby.

I tried a lot but cannot reproduce the issue. May be need more information about your enviorement.

from kirby.

Closing for now. Feel free post new replicate info when you find more clues 👍

from kirby.

osx 14.1.2, laravel herd, php8.2
did not verify in live production server.

i have a tab with sections of pages and if i keep clicking the tab head "articles" or if i navigate to the page it hapend seemingly at random

that the sections fail to load

the responses for repeated clicking of the tab "articles" look like this

1. the current panel view get redirected to something like http://XXX.test/api/site/sections/articles_drafts?page=1

{"status":"error","message":"Unauthenticated","code":401,"exception":"Kirby\\Exception\\AuthException","key":"error.auth","file":"..\/kirby\/config\/api\/authentication.php","line":15,"details":[],"route":"site\/sections\/([a-zA-Z0-9\\.\\-_%= \\+\\@\\(\\)]+)"}

2. or rarely a 30 sec php timeout even though only 2 seconds have passed.
3. or a could not write to file (could not trace which file since tracing all f::writes until i could reproduce was too much for ray.app)

from kirby.

@bnomei Could you please post this as a new issue. It's hard to keep track of closed issues and I think mixing up topics a bit. Thank you 🙏

from kirby.

the sections themself are simple and each extending this one only changing the status

base

headline: Articles
type: pages
layout: list
image: false
parent: site.find('articles')

one section

      articles_drafts:
        label: Drafts (hidden)
        extends: sections/articles
        status: drafts

changing the section type from pages to files or info does not prevent the issue from appearing. nor does removing all other tabs and fields from the site blueprint fix it.

an totally empty site blueprint (yielding the info section in the panel) does successfully avoid the issue.

a single to level fields: definition seems to avoid the issue as well.

a long time later digging code...
i think i found it. classical dev error. seems like i had a site()->index() call deep down in my code on the route:after hook with $final === true and that applied to the multiple requests in the panel. like 5 for refreshing that one view. thus the heavy load and the php fpm stopping processes and causing errors.

from kirby.