Skip to content
This repository has been archived by the owner on Apr 25, 2018. It is now read-only.

GCMPlayground doesn't load #18

Open
azaman2204 opened this issue Oct 24, 2015 · 9 comments
Open

GCMPlayground doesn't load #18

azaman2204 opened this issue Oct 24, 2015 · 9 comments

Comments

@azaman2204
Copy link

I can't seem to get GCMPlayground to load on my chrome browser using the my server IP as per docker server IP i.e in my case http://192.168.100.99:3000 although I can see the server output on the terminal. I can register from Android and Chrome.

@silvolu
Copy link
Contributor

silvolu commented Oct 26, 2015

@azaman2204 do you see any lines like:

web_1    | [BS] Access URLs:
web_1    |  ------------------------------------
web_1    |        Local: http://localhost:3000
web_1    |     External: http://172.17.0.24:3000
web_1    |  ------------------------------------
web_1    |           UI: http://localhost:3001
web_1    |  UI External: http://172.17.0.24:3001
web_1    |  ------------------------------------
web_1    | [BS] Serving files from: .tmp
web_1    | [BS] Serving files from: app

In the terminal where you started the playground?

@azaman2204
Copy link
Author

Hi Silvano
Yes I saw that and try access using listed urls. I also tried replacing the
localhost with my local ip but not successful too.

In the terminal, I started playgroud from Applications/docker terminal

Kind regards;
Hj Azaman Hj Suleiman

On Tue, Oct 27, 2015 at 3:43 AM, Silvano Luciani [email protected]
wrote:

@azaman2204 https://github.com/azaman2204 do you see any lines like:

web_1 | [BS] Access URLs:
web_1 | ------------------------------------
web_1 | Local: http://localhost:3000
web_1 | External: http://172.17.0.24:3000
web_1 | ------------------------------------
web_1 | UI: http://localhost:3001
web_1 | UI External: http://172.17.0.24:3001
web_1 | ------------------------------------
web_1 | [BS] Serving files from: .tmp
web_1 | [BS] Serving files from: app

In the terminal where you started the playground?


Reply to this email directly or view it on GitHub
#18 (comment)
.

@azaman2204
Copy link
Author

Hi
this is what i got when launched docker


Then I got this


When I go to http://192.168.99.100:3000, I got blank page. Viewing the
source form the browser it actually call the page correctly but didnt
display/i cant see anything on screem

When I go to http://192.168.99.100:3001 for the UI i got error


When run the Android APP, It registers ok, i can send and saw the message
on terminal but not to the mobile.


Cant figure out why it didnt display the option on the web for me to send
message to mobile thru GCM

Kind regards;
Hj Azaman Hj Suleiman

On Tue, Oct 27, 2015 at 3:43 AM, Silvano Luciani [email protected]
wrote:

@azaman2204 https://github.com/azaman2204 do you see any lines like:

web_1 | [BS] Access URLs:
web_1 | ------------------------------------
web_1 | Local: http://localhost:3000
web_1 | External: http://172.17.0.24:3000
web_1 | ------------------------------------
web_1 | UI: http://localhost:3001
web_1 | UI External: http://172.17.0.24:3001
web_1 | ------------------------------------
web_1 | [BS] Serving files from: .tmp
web_1 | [BS] Serving files from: app

In the terminal where you started the playground?


Reply to this email directly or view it on GitHub
#18 (comment)
.

@silvolu
Copy link
Contributor

silvolu commented Oct 28, 2015

@azaman2204 I asked if you could see those lines just to make sure that the UI was serving, but you shouldn't use those IPs. If your IP is 192.168.99.100, then the UI should be served at http://192.168.99.100:3000.
Which version of Chrome are you using? If you open the Developer Console on the blank page, do you see any errors?

@azaman2204
Copy link
Author

Yes I use my ip as per docker info when it booted up my defult container.
i.e t http://192.168.99.100:3000. whuch I didnt get any UI. it's just a
blank page.

I'm using this version of Chrome Version 46.0.2490.80 (64-bit)
when I open teh Developer Console I just got blank page, no errors

Kind regards;
Hj Azaman Hj Suleiman

On Wed, Oct 28, 2015 at 9:06 AM, Silvano Luciani [email protected]
wrote:

@azaman2204 https://github.com/azaman2204 I asked if you could see
those lines just to make sure that the UI was serving, but you shouldn't
use those IPs. If your IP is 192.168.99.100, then the UI should be served
at http://192.168.99.100:3000.
Which version of Chrome are you using? If you open the Developer Console
on the blank page, do you see any errors?


Reply to this email directly or view it on GitHub
#18 (comment)
.

@wjarek-zz
Copy link
Contributor

have you tried deploying on GCP or AWS?

@timbremer
Copy link

I have exactly the same problem. The browsersync ui shows correctly but when I try to open the playground I only see a blank page.
My terminal shows

web_1    | [BS] Access URLs:
web_1    |  -----------------------------------
web_1    |        Local: http://localhost:3000
web_1    |     External: http://172.17.0.2:3000
web_1    |  -----------------------------------
web_1    |           UI: http://localhost:3001
web_1    |  UI External: http://172.17.0.2:3001
web_1    |  -----------------------------------
web_1    | [BS] Serving files from: .tmp
web_1    | [BS] Serving files from: app

Test system is Ubuntu 15.10 64bit in a VM

What is strange too is that when I use just ./start.sh I get this error:

Couldn't connect to Docker daemon at http+docker://localunixsocket - is it running?

If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.

When I do sudo ./start.sh it works fine.

@georgianst
Copy link

I had the same problem. I ran the commands from the start.sh manually and then it worked. The problem was that because of some unknown error your start.sh shell script did not run entirely and your bower was not installed(that is why you were not seeing anything on google chrome).

@silvolu
Copy link
Contributor

silvolu commented Mar 16, 2016

#34 should fix this by moving all the requirements to the docker image, let me know if you have any opinions on the change!

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

No branches or pull requests

5 participants