500 on panel and subpages, thumbs not created

The CMS Questions
1

This server had a working K2 site with php 5.6.

I’ve deployed a (working locally and in another remote server) k3 site, gave me the upgrade php message.

As instructed by the hosting provider I added the following handler to .htaccess so it uses php7.2

# Kirby .htaccess

# Use PHP 7.2
AddHandler php72-fcgi .php
...

With this home loads (so htaccess is loaded) but images get 500, subpages get 500 (no thumbs under media/), and panel gets 500.

  • phpinfo shows PHP Version 7.2.24,
  • mbstring, curl, ctype, gd, enabled.
  • I assume url rewrite is enabled (because of k2 site working) but phpinfo does not show mod_rewrite explicitly.
  • Files 644, Folders 755

What else can I check ?

Thank you very much

2

Does the K2 site also run under 7.2? If not, rewriting might in fact not be enabled.

3

I’ve sent the question to the hosting provider, do you know a way of testing manually if mod_rewrite is on? I am going to google

4

I think changing file handlers shouldn’t change which apache modules are loaded.

It’s possible you don’t see mod_rewrite in your phpinfo() call because you’re running PHP as a CGI script (and not as an apache module). So the fact that you don’t see it doesn’t mean that it’s not loaded.

Do you have some access to the logs to see where the 500 errors come from? What does the error page look like? Is it the browser default error page or is it the error screen from Kirby? If it’s Kirby, enable the debug option in your config.php and see what the error says.

5

Thanks for answering

Yes, I assume mod_rewrite is probably enabled even if it does not appear.
I don’t have access to the logs.
The error page seems browser default: Internal server error

Debug is enabled (and works fine).

6

I just received a message from the hosting provider saying mod_rewrite is active for 7.2.

7

Does the site run in a subfolder or on its own (sub)domain?

8

To test if mod_rewrite is enabled while not having access to shell or logs you can insert the line RewriteEngine On BEFORE the line <IfModule mod_rewrite.c>. If the module is loaded, it will not harm. If the module is not loaded you will get an HTTP 500 error immediatly, even for your home page. Everything between <IfModule mod_rewrite.c> and </IfModule> will not be executed if mod_rewrite is not loaded.

9

That is clever, and it would seem mod_rewrite IS enabled.

@pixelijn no, it doesn’t run in a subfolder but in the public folder, right where the domain points at. The k2 site did not have a RewriteBase rule in its .htaccess neither.

I asked the provider to see php / server logs

10

Just to be sure, is this the correct way to add a php version handler to .htaccess ? after having problemas with leading whitespace on my index.php I am paranoid :slight_smile:

11

This directive alone only tells apache to associate .php files with a handler named php72-fcgi. Your hoster already defined and associated this handler with an action, apparently the execution of PHP 7.2. Since phpinfo() shows the correct version, this seems to be correct. Do you have other additional entries in your .htaccess file? Is your site public available for us?

12

Thanks for your answer.

This is the complete .htaccess file. Unless I made a mistake, It is the same file I am using locally (where the site works as expected) except for the 7.2 handler

# Kirby .htaccess

# Use PHP 7.2
AddHandler php72-fcgi .php

# rewrite rules
<IfModule mod_rewrite.c>

# enable awesome urls. i.e.:
# http://yourdomain.com/about-us/team
RewriteEngine on

# make sure to set the RewriteBase correctly
# if you are running the site in a subfolder.
# Otherwise links or the entire site will break.
#
# If your homepage is http://yourdomain.com/mysite
# Set the RewriteBase to:
#
# RewriteBase /mysite

# In some environments it's necessary to
# set the RewriteBase to:
#
# RewriteBase /

# block files and folders beginning with a dot, such as .git
# except for the .well-known folder, which is used for Let's Encrypt and security.txt
RewriteRule (^|/)\.(?!well-known\/) index.php [L]

# block text files in the content folder from being accessed directly
RewriteRule ^content/(.*)\.(txt|md|mdown)$ index.php [L]

# block all files in the site folder from being accessed directly
# except for requests to plugin assets files
RewriteRule ^site/(.*) index.php [L]

# Enable authentication header
SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1

# block direct access to kirby and the panel sources
RewriteRule ^kirby/(.*) index.php [L]

# make site links work
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*) index.php [L]

</IfModule>

# compress text file responses
<IfModule mod_deflate.c>
AddOutputFilterByType DEFLATE text/plain
AddOutputFilterByType DEFLATE text/html
AddOutputFilterByType DEFLATE text/css
AddOutputFilterByType DEFLATE text/javascript
AddOutputFilterByType DEFLATE application/json
AddOutputFilterByType DEFLATE application/javascript
AddOutputFilterByType DEFLATE application/x-javascript
</IfModule>

And this is the previous .htaccess used with k2 on php 5.6

# Kirby .htaccess

# Use PHP5.6 as default
AddHandler php56-fcgi .php

# rewrite rules
<IfModule mod_rewrite.c>

# enable awesome urls. i.e.:
# http://yourdomain.com/about-us/team
RewriteEngine on

# make sure to set the RewriteBase correctly
# if you are running the site in a subfolder.
# Otherwise links or the entire site will break.
#
# If your homepage is http://yourdomain.com/mysite
# Set the RewriteBase to:
#
#RewriteBase /

# block text files in the content folder from being accessed directly
RewriteRule ^content/(.*)\.(txt|md|mdown)$ error [R=301,L]

# block all files in the site folder from being accessed directly
RewriteRule ^site/(.*) error [R=301,L]

# block all files in the kirby folder from being accessed directly
RewriteRule ^kirby/(.*) error [R=301,L]

# make panel links work
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^panel/(.*) panel/index.php [L]

# make site links work
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*) index.php [L]

</IfModule>

# Additional recommended values
# Remove comments for those you want to use.
#
# AddDefaultCharset UTF-8
#
# php_flag short_open_tag on

I can make the site available again tomorrow. Hopefully by then I’ll get access to server logs.

Thanks again

13

It was a RewriteBase issue.

Lesson learned, even if it should not be RewriteBase, of course try RewriteBase.

Thank you all.

1 Like