Not able to open login page on https

Saket · May 23, 2022, 9:43am

When I try to open panel/login page on https it shows the following error.

Mixed Content: The page at ‘https://my-domain-name/panel/login’ was loaded over HTTPS, but requested an insecure stylesheet ‘http://my-domain-name/media/panel/f9335d6b469643eb39665df09fba0be2/css/style.css’. This request has been blocked; the content must be served over HTTPS.

Rest all the pages are running fine.

Saket · May 23, 2022, 10:11am

If i change config with hardcoded url options
then the following error appears

index.js:1 DOMException: Failed to execute ‘pushState’ on ‘History’: A history state object with URL ‘http://my-domain-name/panel/login’ cannot be created in a document with origin ‘https://my-domain-name’ and URL ‘https://my-domain-name’.

Saket · May 23, 2022, 10:52am

@ahmetbora @texnixe Any idea?

ahmetbora · May 23, 2022, 11:32am

Could this problem you are experiencing be related to this?

github.com/getkirby/kirby

Url overwrite config doesn't overwrite protocol

opened 12:42PM - 27 Mar 22 UTC

ChristophLabacher

type: bug 🐛

## Description After upgrading to 3.6(.3.1) I experience a behavior similar to …the one described in https://github.com/getkirby/kirby/issues/3645, when I try to access the panel, only for me it’s not the port, but the entire domain: ``` DOMException: Failed to execute 'pushState' on 'History': A history state object with URL 'http://localhost/panel/site' cannot be created in a document with origin 'https://ourdomain.com' and URL 'https://ourdomain.com/panel/site'. ``` The frontend of our website with Kirby works as expected. We run Kirby in a Docker setup with two containers: An nginx container that handles the incoming requests and forwards them to a php-fmt container, which runs Kirby. I assume the described behavior happens because within this setup the Kirby server is actually running on localhost (within its container), as it gets its requests directly from the nginx container. In the frontend we observed a similar behavior, where one would be forwarded to `localhost/de` when loading the page, but there we could fix it simply by setting `'url' => "ourdomain.com"` in `config.php`. **Expected behavior** The user should be forwarded to `https://ourdomain.com/panel/site`. Like the frontend, the Panel should prefer the domain given in`config.php` rather than try to extract the domain from the server’s information (I assume `HTTP_HOST`?) Edit: While `Server::get('HTTP_HOST')` returns the correct host, `Server::host()` returns `localhost`. ## Your setup **Kirby Version** Everything above 3.6 **Console output** ``` DOMException: Failed to execute 'pushState' on 'History': A history state object with URL 'http://localhost/panel/site' cannot be created in a document with origin 'https://ourdomain.com' and URL 'https://ourdomain.com/panel/site'. ```

Saket · June 6, 2022, 5:16pm

When will this resolve? @texnixe

texnixe · June 6, 2022, 5:26pm

Should get solved in 3.7.0

Saket · June 30, 2022, 7:49am

I am not able to apply kirby license if I am opening panel through the IP @texnixe

Adspectus · June 30, 2022, 8:00am

How about to solve the root cause (if I get it right), namely

and make sure the site is completely accessible via https and only via https?

Topic		Replies	Views
Panel Blocked attempt to use history.pushState() Error Solved ✅ panel	12	1407	May 21, 2022
Failed to fetch http vs. https Solved ✅	2	148	December 18, 2023
Mixed content issues with panel Kirby 3 panel	5	932	April 29, 2022
Panel isn't working properly Issues 🐛	13	1699	April 4, 2017
Failed to execute 'pushState' on 'History' Kirby 3	9	2955	December 23, 2021

Not able to open login page on https

Related Topics