gekko dont starting after blackout

[dark0ni]

Hello again,

in the last day I had a power blackout, after my raspberry reboot and I tryed to start gekko UI again it stuck on "Serving Gekko UI on http://192.168.0.24:3000/", no error messages.

I already redownload the repo and tryed to start the project same issue.
It is possible to get verbose output when i start the gekko ui?

Thank you for future help

[askmike]

Are you sure you were running the UI before the blackout? Because if you run node gekko --ui Gekko won't do anything until you connect to the UI.

[dark0ni]

@askmike Gekko already running before with a live trader. When i started the gekko --ui there was after "Serving Gekko UI on http://192.168.0.24:3000/" additional logs/text.

Now it shows nothing after "Serving Gekko UI on http://192.168.0.24:3000/" and when i try to start the website ERR_ADDRESS_UNREACHABLE.

I also checked the Ip address of the device it is still the same and localhost didnt work either.

[askmike]

Gekko already running before with a live trader

Unfortunately for now you need to restart the trader, Gekko will auto resume it on the next version (see #911).

ERR_ADDRESS_UNREACHABLE.

So your browser is unable to contact gekko. So you are hosting Gekko on a raspberry, but where are you running the browser?

[dark0ni]

So your browser is unable to contact gekko. So you are hosting Gekko on a raspberry, but where are you running the browser?

I use the internal browser based on Chromium in raspbian.

[askmike]

And what error do you get when trying to load "Http://localhost:3000"?

…

On 14 Aug 2017 12:24, "dark0ni" ***@***.***> wrote: So your browser is unable to contact gekko. So you are hosting Gekko on a raspberry, but where are you running the browser? I use the internal browser based on Chromium in raspbian. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#965 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA7MD_28yp3x9_MG8QFh2K218YmON72oks5sYC51gaJpZM4O2N6R> .

[dark0ni]

@askmike interesting with the config 192.168.0.24:300 and access over localhost adress, i can access the website.

But the website shows following error in a popup:

Something happened to either Gekko or the connection. Please check the terminal where Gekko is running or your network connection.

when I set the configUi to localhost i can access the website without error

[askmike]

That means that the UI is unable to estebalish a websocket connection, can you post your UIConfig?

…

On Mon, Aug 14, 2017 at 12:41 PM, dark0ni ***@***.***> wrote: @askmike <https://github.com/askmike> interesting with the config 192.168.0.24:300 and access over localhost adress, i can access the website. But the website shows following error in a popup: Something happened to either Gekko or the connection. Please check the terminal where Gekko is running or your network connection. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#965 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA7MD66_HBDWtAyBOOBzV0vOGW1YlGrJks5sYDJLgaJpZM4O2N6R> .

-- PGP key at keybase.io/mikevanrossum <https://keybase.io/mikevanrossum/key.asc>

[dark0ni]

@askmike

// 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: false,
  api: {
    host: '0.0.0.0',
    port: 3000,
  },
  ui: {
    ssl: false,
    host: '192.168.0.24',
    port: 3000,
    path: '/'
  },
  adapter: 'sqlite'
}

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

[askmike]

when I set the configUi to localhost i can access the website without error

So if you configure it to localhost everything works and you don't have any errors?

[dark0ni]

So if you configure it to localhost everything works and you don't have any errors?

@askmike thats correct, but when i try with an internal ip that the raspberri use, i cant access the website anymore, only with the localhost adress. Before the blackout everythings worked fine with this configuration

[askmike]

strange.. Nonetheless it's an issue with your rasppi setup: those errors you mentioned come from the PI telling gekko (the "error in a popup") or your browser (the "ERR_ADDRESS_UNREACHABLE") that it can't connect to gekko.

I'm glad you got it sorted!

[dark0ni]

@askmike Thanks for your time and help