Panel blank, www-Subomain, IONOS Hosting

Kirby 3 Solved ✅
1

I run a Kirby 3.6.2 (PHP 8.0) in a IONOS webspace. Both Domain and www-Subomain point to the Kirby folder.

With https://domain.tld everything works fine.

With https://www.domain.tld I get cross-origin errors, which is understandable since assets load from https://domain.tld.

So, when I add ‘url’ => ‘https://www.domain.tld’ to the confiq.php the website works fine again under https://www.domain.tld.

But the panel throws an error:

“Uncaught (in promise) DOMException: The operation is insecure.” for index.js and vendor.js.

The .htaccess is the Kirby standard from the plain kit + RewriteBase /

I tried to redirect the https://domain.tld to https://www.domain.tld in the domain settings but it didn’t help.

Any ideas? Thanks!

2

Could you try with 3.6.3.1? It seems to me that URL detection isn’t working properly and we made a couple fixes with that release that could help.

3

Works! Thanks, Bastian! :beers:

1 Like
4

I’m running into the same problem with IONOS. Just updated to Kirby 3.6.5 because I remembered reading about URL detection problems in the release notes but it didn’t fix it for me. I redirect the non-www url to the www url. The the non-www domain gets detected leading to the noted cross-origin errors.

Edit: the hardcoded www-URL in config.php helped. The domain specific config without the www didn’t work. Note that IONOS needs the RewriteBase / turned on.

Edit-2: the URL-list solves it the best for now since I can have both my local development and the live url in there and it picks the correct one.

1 Like
5

For me it’s not working…

config.www.example.com.php and config.example.com.php both have url set to https://www.example.com, assets still want to be loaded from https://example.com

RewriteBase is turned on and I’m on Kirby 3.6.6

Any ideas?

//EDIT

Ok, wenn I add the url parameter with www to the general config.php it works on the remote server… assets are now loaded from www.example.com

BUT on localhost it STILL wants to load the assets from www.example.com even with config.localhost.php url set to http://localhost

Something’s not right here: It seems like the url setting in the domain specific configs is not considered…?! I tried setting url in config.www.example.com.php to https://www.google.de and it didn’t change anything.