Skip to content
Choose a tag to compare


@bastianallgeier bastianallgeier released this
· 3739 commits to master since this release
Choose a tag to compare

While we are busy working on 3.4, this release is a security patch for a minor issue related to .dev domains and reverse proxies.

About our registration block

In order to protect new installations on public servers that don't have an admin account for the Panel yet, we block account registration there by default. This is a security feature, which we implemented years ago in Kirby 2. It helps to avoid that you forget registering your first admin account on a public server.

In this case – without our security block – someone else might theoretically be able to find your site, find out it's running on Kirby, find the Panel and then register the account first. It's an unlikely situation, but it's still a certain risk.

To be able to register the first Panel account on a public server, you have to enforce the installer via a config setting. This helps to push all users to the best practice of registering your first Panel account on your local machine and upload it together with the rest of the site.

The issue

As noted by Jukka Rautanen, this installation block still assumed that .dev domains are local domains, which is no longer true. In the meantime, those domains became publicly available. This means that our installation block is no longer working as expected if you use a .dev domain for your Kirby site. We've also used the chance to improve the local installation check if your site is behind a reverse proxy.

Am I affected?

You are only affected if:

  1. you use a .dev domain or your site is behind a reverse proxy &
  2. you have not yet registered your first Panel account on the public server &
  3. someone finds your site and tries to login at before you register your first account.

You are not affected if you have already created one or multiple Panel accounts (no matter if on a .dev domain or behind a reverse proxy).