Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Loading timeout / blank page #40

Open
rzschoch opened this issue Apr 4, 2018 · 10 comments
Open

Loading timeout / blank page #40

rzschoch opened this issue Apr 4, 2018 · 10 comments

Comments

@rzschoch
Copy link

rzschoch commented Apr 4, 2018

Hi,

the initial setup only displays a blank page and the browser timeouts while loading. The only solution I found is to use my own local proxy (via proxy setting in main.config.js).

Is there anything I could try?

System: Mac OS 10.13.4

Thanks!

@pqml pqml added the bug label Apr 4, 2018
@rzschoch rzschoch changed the title Loading timeout / Blank page Loading timeout / blank page Apr 4, 2018
@pqml
Copy link
Member

pqml commented Apr 4, 2018

I succeed to reproduce the issue once, but now it seems to work fine. Have you tried to re-start the dev-server ? Or using another browser ?

@rzschoch
Copy link
Author

rzschoch commented Apr 4, 2018

Yes, I re-started the dev server multiple times, used Chrome, Firefox, Safari and also tried different preprocessor settings (sass and less) without any change.

Do you have any idea on how I could debug the issue and provide you with helpful messages?

@rzschoch
Copy link
Author

rzschoch commented Apr 5, 2018

I also tried to use it width older versions of Kirby (2.5.9 and 2.5.8) – unfortunately that didn’t help 😞

@pqml
Copy link
Member

pqml commented Apr 5, 2018

What is your php cli version ?

Maybe it's also something related to our use of IPv6 to get the php server properly working on localhost on MacOS (see http://php.net/manual/fr/features.commandline.webserver.php#120449)
Do you have any particular network setup ?

@rzschoch
Copy link
Author

rzschoch commented Apr 5, 2018

Thanks for your time.

My php version: PHP 7.1.14 (cli) (built: Feb 7 2018 18:33:30) ( NTS )

When I start a php server manually (php -S localhost:8000) and change the proxy setting (main.config.js) to localhost:8000 everything works. The server log then shows that localhost resolves to 127.0.0.1.

Hope this helps?

@obelmont
Copy link

obelmont commented Apr 17, 2018

Hi, I seem to be having a similar issue to this one, oddly enough this only occurs when I attempt to access the panel. The server runs fine until I try to access the panel and then both the front end and panel no longer work until I reset it.

My php version: PHP 7.2.4 (cli) (built: Mar 29 2018 15:32:43) ( NTS )

Haven't been able to get the dev server working through the proxy settings. However the panel is working when I access it directly through the manual php server (php -S localhost:8000).

When I downgrade php to 7.0 (PHP 7.0.29 (cli) (built: Apr 12 2018 03:13:39) ( NTS )) it seems to work fine.

Happy to help in any way I can with this one!

Edit: I have a build that began from a fork of the repo when it was v0.7.3 that is able to access the panel using php72 .

@pqml
Copy link
Member

pqml commented Apr 17, 2018

It's a really strange behaviour and I have no issues using PHP 7.2.4 cli and macOS 10.13.4

With the latest kirby-webpack version you can try to change phpHost: 'localhost' to phpHost: '127.0.0.1' in main.config.js

You will also have to rename www/site/config/config.localhost.php to www/site/config/config.127.0.0.1.php

@obelmont
Copy link

I think my issue is actually entirely PHP install related. I am unsure if this is the same for @rzschoch.

I tried manually starting a php server and heading to the panel where I refreshed the page a few times and the php server had a segmentation fault and shut down. This only happens on php 7.2 and not 7.0. I'll post here again if I can confirm that this is the case!

@PeteCrighton
Copy link

With the latest kirby-webpack version you can try to change phpHost: 'localhost' to phpHost: '127.0.0.1' in main.config.js

You will also have to rename www/site/config/config.localhost.php to www/site/config/config.127.0.0.1.php

I think I had the same issue as @rzschoch (on Linux), and this fixed it for me.

Should this config.127.0.0.1.php be prevented from being deployed to the production server?

@pqml
Copy link
Member

pqml commented Sep 3, 2018

Interesting. On the next release I will set 127.0.0.1 as the default host instead of localhost since it seems to fix a couple of issues

I don't think you need to prevent the file from being deployed. It should not be used by your server - see https://getkirby.com/docs/developer-guide/configuration/options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants