Are you sure with 755? I thought it should be 775, if the Apache user is not the owner of the file but member of the group?! But I may be wrong with that …
I’ve changed to 775 (folder and its content) and the problem still exists. It works great locally. Maybe its a host problem?
Locally I’m working with vagrant and homestead (Nginx) and the live site runs on Apache.
There are so many factors involved here, it’s very hard to debug. There also doesn’t seem to be a single cause for this but multiple different ones.
Soooooo, it works again.
I replaced the whole page (site and content folders too) with the starter kit and it worked. Then I replaced the content and site folder with my stuff and it works.
A little bit weird but… It works 
3 Likes
Great to hear that! Then it was either a permissions issue or a file was missing or corrupt.
1 Like
Had the same error today with Kirby 2.3 running locally on apache or the inbuilt php-server. Just as @maxxscho suggested I completely swapped the site/, content/, kirby/ and panel/ folders with them from the starterkit and replaced my stuff inside the folders. Then I’ve set the permissions of site/accounts/.logins to 775 and everything worked again… (The re-setting of the permissions didn’t solve the problem without the folder replacement)
This really should not be marked as “solved”.
@wottpal: When did that error occur? After updating to Kirby 2.3? If so, how did you do the update?
Nope, updated a while ago. Really no clue how this happened, maybe related to git or so 
(.logins is on gitignore, so is created individually everywhere…)
Do you guys use github to version your installs? maybe try to check if any submodules are not initalized in your git local install. This was my problem and now everything works like a charm again 
Maybe the reason: I’m using the kirby-cropper plugin as a submodule, so needed files were missing…
Hi Guys,
I’m having problems with the “too many redirects” when I try to access the panel on the server. I’m using v2.3.0 and I already checked the permissions. I have no idea what’s happening, can someone throw me a bone?
Thanks!
I also have the issue after upgrading from 2.3.1 to 2.3.2 - only on the Production server.
Can we get a troubleshooting list on this?
Turns out that turning debug off is what causes the problem. c::set('debug', false);. I downgraded to 2.3.1 again, where it doesn’t matter if debug is on or off.
Then you maybe have an error in one of your plugins somewhere. Sometimes error output can break the Panel.
But I’m turning debug off and then the infinity redirect loop occurs.
That’s interesting. To be honest I have no idea how that makes any sense.
1 Like
@Pascalmh:
Whats your real PHP version on that server?
This happens on multiple environments.
PHP Versions are: 5.6.14, 5.6.23-1 and 5.6.24-1.
@Pascalmh: Have you ever solved it?
Unfortunately not, I went back to 2.3.1 again as I said above.
Thanks for reporting back, Pascal. Would be interesting to know if it works without the debug config setting for you as well.