New Sites aren’t appearing when I click the “View Site” button.
Chrome Browser opens but URL is blank on the address bar.
Mac High Sierra 10.13.3
Site Config - PHP 5.4.45, Apache Web Server, MySql 5.5.55
Changed default browser back to Safari and can now view site by clicking on “View Site” button.
@fanmany7 it’s worth fully quitting Chrome and re-openning. I know this has been frustrating for me recently with Slack and after a fully quit and reload of Chrome, it’s back in working shape.
I am also on Mac High Sierra 10.13.3 with Chrome as my default browser.
All the button links within Local Flywheel stopped working for me this morning. I thought I must have screwed up my Flywheel when I failed to shut down properly last night. I reinstalled Flywheel and restored my site and it still wasn’t working properly.
I can confirm that switching the default browser back to Safari works. I then closed Chrome and set the default browser back to Chrome and tried the button links in Flywheel again and Chrome now works properly with Local Flywheel.
This is a very strange issue. Any idea why this happens?
From what I can tell right now it’s something with Chrome and failing opening in the browser with about:blank. Others are seeing it from this thread I found. It starts as if its that app issue and others note seeing it elsewhere with Chrome specifically.
Hello, I’m new to Local by Flywheel, and I’m getting the exact same problem as the description above (with the same mac OS version & site config) except that trying Safari didn’t work & restarting Chrome (or typing chrome://restart in the browser bar) didn’t work – I still have an empty page. I have a live website that I’d like to work on in Local by Flywheel, and I just imported it.
Interestingly, when I go to the site’s admin (https://mysite.local/wp-login.php) I can log in and it looks fine (I didn’t test extensively, but it looks just like the live site’s). It’s only when I try going to https://mysite.local/ , including via Visit Site from the WP admin dashboard, that I get a blank page.
Some details in case this helps:
In Chrome DevTools, on the network tab:
Request headers on the real site (which isn't "mysite.com"):
GET / HTTP/1.1
Host: mysite.com
Connection: keep-alive
Cache-Control: max-age=0
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.9
Cookie: _tccl_visitor=1e34c96b-4758-401a-9dbb-0ca6da02439c; _tccl_visit=1f9d2711-9355-48d7-bfa5-018a16ca85a6
Response headers on the real site:
HTTP/1.1 200 OK
Date: Sat, 30 Jun 2018 21:07:57 GMT
Server: Apache
X-Powered-By: PHP/5.4.45
Link: <https://mysite.com/wp-json/>; rel="https://api.w.org/"
Vary: Accept-Encoding,User-Agent
Content-Encoding: gzip
Content-Length: 7082
Keep-Alive: timeout=5
Connection: Keep-Alive
Content-Type: text/html; charset=UTF-8
The request headers on the local site looked quite a bit different:
:authority: mysite.local
:method: GET
:path: /
:scheme: https
accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8
accept-encoding: gzip, deflate, br
accept-language: en-US,en;q=0.9
cache-control: max-age=0
cookie: wp-settings-1=editor%3Dhtml%26libraryContent%3Dbrowse%26wplink%3D1%26align%3Dcenter%26imgsize%3Dfull%26post_dfw%3Doff%26posts_list_mode%3Dlist%26urlbutton%3Dcustom; wp-settings-time-1=1530390999; wordpress_test_cookie=WP+Cookie+check
upgrade-insecure-requests: 1
user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36
Response headers on the local site:
HTTP/1.1 200 OK
Content-Length: 0
content-type: text/html; charset=UTF-8
Date: Sat, 30 Jun 2018 21:07:57 GMT
Link: <https://mysite.local/wp-json/>; rel="https://api.w.org/"
server: nginx/1.10.1
status: 200
X-Powered-By: PHP/5.4.45
And yes, I do have Apache selected as my webserver. But that may not have anything to do with anything. - Edit: I noticed in Nginx headers for Apache server? - Support - Local Community that @clay explains the reverse proxy, so I guess that explains that.