Shaw
October 25, 2022, 3:20pm
1
This is definitely a hosting issue.
I have a barebones test Kirby setup (protected via .htpasswd
) on my previous host that works fine, but when I migrated to the new host (NearlyFreeSpeech.net ) yesterday I’m no longer able to login.
At first I couldn’t even reach the login screen, as I got an error telling me the site/sessions
folder isn’t writable. I have to set permission to 777 using Filezilla before I can enter my credentials.
However once I entered my credentials it briefly flashed the following screen
…before booting me to test site’s 404/error page.
I have debug turned on in the config.php but I got nothing.
I checked using phpinfo()
to make sure all required extensions are turned on, and I’m using PHP 8.1.
Anyone got an idea?
Have you checked the php error logs/server error logs? Or is there anything more useful in the dev tools console?
Shaw
October 25, 2022, 5:42pm
3
I tried clearing the error_log produced by NearlyFreeSpeech (to weed out previous unrelated errors) and trigger the login issue again.
No new entry has been recorded.
This is the dev console error received during the flash that I screenshotted in my opening post:
Does Kirby keep its own error logs?
Does barebones mean a Plain- or Starterkit without any extensions?
Shaw
October 25, 2022, 6:31pm
5
Plain kit, no extensions.
What about the browser’s network tab? Any API requests with garbage responses (HTML)?
Shaw
October 25, 2022, 6:47pm
7
See network tab below, it shows 404 for the testsite/panel/login
route:
Shaw
October 25, 2022, 7:50pm
8
I will try to ask in their support forum.
Yes, might make sense. What settings do you have in your config.php?
Shaw
October 25, 2022, 8:14pm
10
Their support suggest I seek help over at CMS vendor haha…
Anyways, I only have debug turned on in the config.
Shaw
October 26, 2022, 5:26am
11
Edit: continuing my troubleshooting over in new thread:
It looks like my new host - NearlyFreeSpeech - is causing Kirby to not properly detect the base URL when used in a subfolder.
I initially thought it was a mod_rewrite issue, but I think now it’s a base URL issue.
To troubleshoot, I tried to manually set the base URL in config.php to 'url' => '/starterkit'.
However, I get this in the home page source:
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width,initial-scale=1.0">
<…