Question Webtrees 2.0.16 no graphical layout of the home page

Hello

What could be the reason that when I type kowalewski.ct8.pl it's textual - as if without a layout?
This wasn't there until recently. I didn't change anything on the page.
On the other hand, when I click on e.g. ‘Default individual’ or ‘Default chart’, the normal appearance loads
kowalewski.ct8.pl/index.php?route=%2Ftre...%2FMaciej-Kowalewski

Regards

The css style sheet won't load.
The problem is protocol http versus https.
On the server the file config.ini.php should have a variable 'base_url'.

See www.webtrees.net/index.php/forum/help-fo...do-i-implement-https

Thank you very much for your helpful reply.
In this file is
>>base_url="http:// ... etc."<<
I changed it to >>base_url="https:// ... etc."<<
Now it works.

Why was this not needed before (a few months ago) and the page loaded normally?

Well, your hosting provider may have switched off http. The whole internet is supposed to be https these days.

http is like sending postcards. Any one working in postal services can read it.
https is like sending sealed letters. Only the receiver has access.

http still works.
There are other sites at this provider that work via http:
maksymilian-domeracki.ct8.pl/
grzegorj.ct8.pl/lingwpl/migracje.html
emsoft.ct8.pl
genealogia.ct8.pl/obrazki/Rogozinski-Antoni/
etc.
My site still goes in via http too, just without the layout.
It's a bit strange.

The site is public, so it's like a postcard or a newspaper - anyone can read it.
Of course, the login to the site should be encrypted.

simply replace the setting. (from http to https). that has nothing to do with the reachibility.

Yes, that's already changed.
I'm just wondering why up until a few months ago the site would load normally via http with the layout, but now it won't.
Only the change to base_url="https:// ..."
caused it to load via https and http.
Previously this change was not needed.

ask your provider, what he changed.

I asked my domain maintenance provider if anything had changed from his side.
He stated that the problem is on my side because the site is mixed http with https.
Such situations are currently blocked by browsers.
I checked this.
In fact, in older browsers the page loads normally.
That is, it is webtrees using both http and https on the site.
It used to be that browsers accepted this, but now it doesn't.
So the problem is not with the provider, but with Webtrees.

This is not just a webtrees problem, but mainly a server config problem.

webtrees runs fine on pure http, but then the base_url must be specified as http.
webtrees also runs fine on pure https, but then the base_url must be specified as https.

The common approach to prevent mixing http with https, is to force all request go via https. If you are on a Apache server, then this can be done with the following .htaccess file:
This will make any visitor that requests via http to be redirected to the same page on https.

This is interesting. The creator of webtrees says it's the server provider's fault, the provider says it's the website's fault, i.e. Webtrees.
That is to say, there are no culprits, and in my case it stopped working.

How do you explain the fact that nothing has been changed on the server and an older browser e.g. Firefox 70 loads the page fine and the new 135 does not?

Do you want to only look back and argue until the cows come home, or look forward and simply have it fixed?

It's a combination of things: using a web application is a delicate dance between the browser, the server config and the php application. Sometimes while dancing toes get stepped upon, which happens not on purpose but is the risk of dancing. Usually not worth a big drama or investigation.

Mikeko wrote:

This is interesting. The creator of webtrees says it's the server provider's fault, the provider says it's the website's fault, i.e. Webtrees.
That is to say, there are no culprits, and in my case it stopped working.

How do you explain the fact that nothing has been changed on the server and an older browser e.g. Firefox 70 loads the page fine and the new 135 does not?

there is nothing more to explain.
do like Bert said at  www.webtrees.net/index.php/forum/help-fo...the-home-page#110567

For sure your provider changed the handling of mixed content, when your site worked ok formerly. And the solutions by Bert works. Alternative your provider could make handle that situation on a higher level than you can do. But if the provider is not willing to do (and help you) do as Bert proposed or change your provider.

Thanks to you, I know how to fix it: change http to https, for which I thank you very much.

I would also love to know what the problem is and who is telling the truth.
On the one hand there is the claim that it is the server's fault, but if I use an older browser it works.
On the other side is the claim that it's not the server's fault, but the site, which uses both http and https.

However, assuming that my provider has changed support for mixed content, which they don't admit and deny, then why does the site work in older browsers?
When I use an older browser and have base_url='http:// ... etc.' it works.
It does not work on the new browser.
However, when I change to base_url='https:// ... etc.' it works on the new browser.

I would like to find out the truth. To find out what the causes were. Just out of curiosity and to find out something I don't know.
After all, it's not some magic and it can be explained in an understandable way.

ask the browser developers.
security is the magic word.

@Mikeko
Neither your base_url configuration nor your rewrite rule seem to be effective.
For https your base_url needs to be precisely: For the rewrite rule @bertkoor suggested: I am using a slightly different one:
Furthermore make sure you are using an appropriate (no longer supported) php version for your no longer supported webtrees 2.0.16, see webtrees.net/download - if your provider updated your php version then some things might no longer work as expected. Better upgrade all components to supported versions. Otherwise you might suffer from code rot.

So it is the browser that is causing the problem after all.
It follows that webtrees uses http and https in a mixed way all the time.
Of course I know that I can force the use of https.
My point is that as it used to be, it still is.
So it is not my provider (server space and domain) that has contributed to the fact that the webtrees page with my family tree now displays badly.

I've had PHP version 8.1 since 2023 and it worked fine with webtrees 2.0.16 for all that time.

Mikeko wrote:

It follows that webtrees uses http and https in a mixed way all the time.

because you most probably misconfigured something a long time ago, but the old browser was more tolerant than the new browser. The only one who can fix that is you.

EDIT: One more thing. webtrees CANNOT be run successfully with both http and https. You MUST decide for one or the other. Because providers usually offer both protocols it is better to only use https and configure webtrees as suggested, i.e. base_url and a rewrite rule.

> Why was this not needed before (a few months ago) and the page loaded normally?

1) I guess that until now, you only visited your site using http:, even though your webhost also provides HTTPS.

Now, you visited your site with https: and it does not work because you have the wrong URL in your configuration. The page is in HTTPS, but all the CSS and JS are sent using HTTP.

2) webtrees sends a HTTP header that sas "if you load this page once using HTTPS, then you must use HTTPS on future visits".

Specifically, it sends this HTTP header:

So, now you cannot go back to HTTP due to browser security rules.

Have I configured something wrong?
The webtrees installer is very simple. You enter a few details and that's it.
I don't think there is any way to configure anything there, including http/https.
Am I mistaken?
I haven't changed anything after that

Do I understand correctly that it is as below?

I installed webtrees in 2021. I accessed the web site via HTTP.
I didn't change anything in the webtrees configuration.
In 2025, I entered this web page via HTTPS and the web page displays wrong.
Can I now only enter via HTTPS on subsequent visits?

It's a bit strange, because over HTTP it still works correctly, but over HTTPS it doesn't.
Furthermore, when I change base_url=‘http...’ to base_url=‘https...’, it loads the page correctly, both over http and over https.

I would add, what I wrote about, that older browsers, despite the base_url=‘http...’ being set, display the page correctly via both http and https.