Panel producing /api/auth/ping errors in MAMP environment

Kirby 4 Issues 🪲
1

I’m running the latest version of K4 under MAMP for my local development environment.

In general practice, I have two tabs open in my browser when working locally on a site. One is open to a page on the site and the other is usually the “System” page of the Panel.

After a period of time, the System page produces the following request, resulting in an “Internal Server Error”.

https://website-dev:8890/api/auth/ping

Looking at the local apache_ssl_access.log, this POST ping occurs at regular five minute intervals, until it generates a 500 response and then performs an unsuccessful GET request.

::1 - - [24/May/2024:21:47:37 -0600] "POST /api/auth/ping HTTP/1.1" 200 41
::1 - - [24/May/2024:21:52:38 -0600] "POST /api/auth/ping HTTP/1.1" 200 41
::1 - - [24/May/2024:21:57:39 -0600] "POST /api/auth/ping HTTP/1.1" 200 41
::1 - - [24/May/2024:22:02:40 -0600] "POST /api/auth/ping HTTP/1.1" 200 41
::1 - - [24/May/2024:22:07:41 -0600] "POST /api/auth/ping HTTP/1.1" 200 41
::1 - - [24/May/2024:22:12:42 -0600] "POST /api/auth/ping HTTP/1.1" 200 41
::1 - - [24/May/2024:22:17:43 -0600] "POST /api/auth/ping HTTP/1.1" 200 41
::1 - - [24/May/2024:22:22:44 -0600] "POST /api/auth/ping HTTP/1.1" 200 41
::1 - - [24/May/2024:22:27:45 -0600] "POST /api/auth/ping HTTP/1.1" 200 41
::1 - - [24/May/2024:22:32:46 -0600] "POST /api/auth/ping HTTP/1.1" 200 41
::1 - - [24/May/2024:22:37:58 -0600] "POST /api/auth/ping HTTP/1.1" 500 528
::1 - - [24/May/2024:22:38:32 -0600] "GET /api/auth/ping HTTP/1.1" 500 528

I’m assuming this has something to do with checking for updates regarding plugins or the Kirby installation itself.

This error does not occur on the live site.

Any clue as to what is going on here or how to prevent it?

2

This request occurs every 5 minutes to keep the session alive. No idea why you get a GET request in the end, is the user logged out at the time this happens. Might be a problem with the two browser tabs.

3

This request occurs every 5 minutes to keep the session alive.

That makes sense.

The user (me) is still logged in when this occurs. Reloading any page of the panel into the browser tab where the error appears works fine. The error does not appear in the tab where I’m viewing a web page on the local site itself, only in the tab where the panel was open.