Disconnected - Something happened to Gekko or ...
Hi All,

Hoping somebody can help me with a networking issue.

I have Gekko working on an Amazon Ubuntu Instance.

I am able to use winSCP to browse the virtual server so I know its all running ok.

I am able to use Amazon AWS Powershell from windows to access the amazon ubuntu instance.

Once connected to Amazon AWS in powershell I am able to run this command
ssh -i C:\Users\User_Name\.ssh\AWS.pem -L3000:localhost:3000 ubuntu@18.my.ip.here

which was taken from - https://github.com/askmike/gekko/issues/1896

The result of this is that Gekko appears to start and run in the powershell window Smile yay

Gekko reports
Serving Gekko UI on https://18.my.ip.here:3000/

Now comes the problem -

If I open a browser window with localhost:3000 the Gekko Background appears but instantly changes to "Disconnected"

This is now driving me nuts, is anybody able to give me a pointer as to whether this is likely to be a setting on my pc? and how do i find out what is causing the disconnection...


Do I need to use the nginx setup?

This is my config -

// This config is used in both the
// frontend as well as the web server.

// see https://github.com/askmike/gekko/blob/stable/docs/installing_gekko_on_a_server.md

const CONFIG = {
 headless: true,
 api: {
   host: '',
   port: 3000,
   timeout: 72000000 // 2 minutes
 ui: {
   ssl: true,
   host: '18.my.ip.here',
   port: 3000,
   path: '/'
 adapter: 'sqlite'

if(typeof window === 'undefined')
 module.exports = CONFIG;
 window.CONFIG = CONFIG;

This is deffo a security thing between ssh and AWS.

If I set ssl = 'false' I can access the gekko on its ip address and it runs well, but of course this is exposing gekko to the internet Sad

When I set ssl to 'true' in the UIconfig then although Gekko is running and I can browse to the Gekko localhost page, I cannot see any activity in the ssh window. Im expecting to see some Get and Post, but nothing happens.

Im getting there slowly.......
Ok All Sorted now,

Had a battle with nginx and now have it working Smile Yay

If it helps anybody else the problem I had was two fold.

Firstly I had not configured AWS ports properly, make sure that inbound HTTP traffic is allowed as well as SSH.

Secondly when setting up nginx, you cannot execute this command "printf "username:`openssl passwd -apr1`\n" >> /etc/nginx/.htpasswd" without chmod the nginx directory to add write access. dont forget to change it back again.

Thanks to AskMike for an excelent program.

Forum Jump:

Users browsing this thread: