Hi everyone, and thanks Mike for an amazing incentive to learn. Very much appreciate all you and the community have done with Gekko.
For network/ISP wonks perhaps... I have Gekko served via nginx, and it is accessible from virtually any device I point to it. So far, however, any time I attempt to access Gekko on a mobile device (on or off data, WiFi, whatever) Gekko reports that it is disconnected. Confirmed that server is up. In fact, I can watch the back end refresh GET assets when I refresh the browser. But immediately it disconnects. Any idea what is causing this? To confirm, the service runs through Firefox on the Linux box and Chrome on a Chromebook. Does not run on Chrome (mobile) or Safari (mobile).
Feels like a device limitation; do others experience this? If not, what might I have done wrong in setting up nginx?
Thanks!
02-27-2018, 08:39 AM
(This post was last modified: 02-27-2018, 08:40 AM by donkykong017.)
(02-27-2018, 08:19 AM)bradmin Wrote: Hi everyone, and thanks Mike for an amazing incentive to learn. Very much appreciate all you and the community have done with Gekko.
For network/ISP wonks perhaps... I have Gekko served via nginx, and it is accessible from virtually any device I point to it. So far, however, any time I attempt to access Gekko on a mobile device (on or off data, WiFi, whatever) Gekko reports that it is disconnected. Confirmed that server is up. In fact, I can watch the back end refresh GET assets when I refresh the browser. But immediately it disconnects. Any idea what is causing this? To confirm, the service runs through Firefox on the Linux box and Chrome on a Chromebook. Does not run on Chrome (mobile) or Safari (mobile).
Feels like a device limitation; do others experience this? If not, what might I have done wrong in setting up nginx?
Thanks!
i have a similar experience with the same setup. nginx and running on aws ec2 i cant connect from safari, other browsers work. but sometimes i see the disconnect screen after i put in the login for a short time, then it goes away. i have not found out whats going on
p.s.: i see a http warning after using nginx although i set it up like in the guide and it schuld use https
re: http warning - I elected to run certbot and the nginx plugin to generate the certificates and manage redirect. One of the options in the plug in is to redirect all traffic to https - not sure if that would resolve your issue. Is your warning a trusted certificate warning? If you follow the instructions, you end up with self-signed certificates that, at least in my experience, throw a privacy warning. Running the certbot plugin generated certkeys and code that I copied into nginx.conf in place of the default certkeys - and everything's gravy. Let me know if I can help.
(02-28-2018, 01:48 AM)bradmin Wrote: re: http warning - I elected to run certbot and the nginx plugin to generate the certificates and manage redirect. One of the options in the plug in is to redirect all traffic to https - not sure if that would resolve your issue. Is your warning a trusted certificate warning? If you follow the instructions, you end up with self-signed certificates that, at least in my experience, throw a privacy warning. Running the certbot plugin generated certkeys and code that I copied into nginx.conf in place of the default certkeys - and everything's gravy. Let me know if I can help.
Thx for your answer. i did not use certbot. instead i used a self signed certificate. i just reset the warnings an checked. you are right its a privacy warning. shit those warnings look all the same. i just wanted to be sure that nothing could go wrong when i use real money with gekko. so this should be HTTPS but with a self signed certificate its equally safe right?
thanks again for your help
Happy to help if I can.
I went with Let's Encrypt! because the certificate is recognized by most, if not all, browsers, and my entire reason for running Gekko in the cloud was to enable remote access from any device. I also use various networks and wanted to make sure that my site would be accessible from pretty much any ISP or network connection.
Thus my frustration with the mobile phone connectivity thing.
I would strongly recommend using certbot if you can. It streamlined my installation and it may make it easier for you, too. Bonus is that you get a public cert that won't throw a code when you navigate to https://.
(02-28-2018, 07:03 AM)bradmin Wrote: Happy to help if I can.
I went with Let's Encrypt! because the certificate is recognized by most, if not all, browsers, and my entire reason for running Gekko in the cloud was to enable remote access from any device. I also use various networks and wanted to make sure that my site would be accessible from pretty much any ISP or network connection.
Thus my frustration with the mobile phone connectivity thing.
I would strongly recommend using certbot if you can. It streamlined my installation and it may make it easier for you, too. Bonus is that you get a public cert that won't throw a code when you navigate to https://.
THX again.. yeah that sounds reasonable. i just went with the self signed cert because it was the first to have worked. (had some struggles setting up nginx at first). i will look into the other possibilities in the future. for now it works for me.
one thing about that mobile browser: have you tried different browser e.g. Samsung browser or opera mobile?
i cant seem to access from safari browser. maybe there is some incompatibility with the cert?
No dice on Opera Mini. Still displaying "Disconnected" after loading. Going to try on an Android device later and see what happens. In the meantime, has anyone else experienced this? Please let me know!
(02-28-2018, 10:14 PM)bradmin Wrote: No dice on Opera Mini. Still displaying "Disconnected" after loading. Going to try on an Android device later and see what happens. In the meantime, has anyone else experienced this? Please let me know!
ok so you have an iphone. i pretty curious if it will work on android, because maybe its an apple problem. i just guessing but maybe they block some certificates idk
03-03-2018, 03:44 AM
(This post was last modified: 03-03-2018, 03:46 AM by bradmin.
Edit Reason: Clarification
)
Sweet. So it is an iPhone thing. Gekko stays connected on my old LG. Same carrier and everything. I don't think it's a certificate issue though, since I am able to access the URL and input user credentials for access. Will do some homework and see what I can find...
(03-03-2018, 03:44 AM)bradmin Wrote: Sweet. So it is an iPhone thing. Gekko stays connected on my old LG. Same carrier and everything. I don't think it's a certificate issue though, since I am able to access the URL and input user credentials for access. Will do some homework and see what I can find...
The problem on iPhones is that every third party browser uses safari under the hood. Chrome, FireFox, Opera, etc all use safari webkit, only the UI is a bit different. Apple doesn't allow other implementations.
|
