Echo Speaks Local Network Logon/Cookie Authorization Server to replace Heroku

[brad5]

Yeah.

[CAL.hub]

@vmsman Scott, I am following your ES guide (Alternate) and have hit a roadblock on my um350. ES seems to be installed but I can't get to the ip:8091. Your guide is not for a LXD container, but I am trying to adopt that as a best-practice. So, I have ventured into the unknown. I created a LXD container:

I cannot ping 10.100.243.137 which I expected to be the address for Es, e.g. 10.100.243.137:8091.

Here are my profiles. This is where I suspect there is a problem because the bridgeprofile shows it is not used by any container.

Installation of nodejs and npm inside the echospeaks container seemed to go OK. It's hard for me to say, because the verbosity is overwhelming. Not sure if this is useful, but here is the bridgeprofile:

Hints on what is wrong?

[vmsman]

@CAL.hub Is 10.100.243.137 an address on your main lan? It concerns me that you are unable to ping it. I think that we might need to do a jitsi session in order for you to screen share to me. Tag up with me on https://chat.scottibyte.com/.

[jtp10181]

@kewashi I found this on line 71 of the index.js
Is this checking the ipAddress env variable before running the built in function? I am not a node coder but that is what it looks like to me.

configFile.set("settings.ipAddress", process.env.ipAddress || getIPAddress());

[kewashi]

Yup! you are so right and I missed seeing this. I stand corrected.

[jtp10181]

For reference, anyone else finding this, found out in another thread, that it may be case sensitive depending on the host system. The other person had to use case exactly as shown ipAddress and then it worked for the IP part of the problem.

[thebearmay]

07:47 (as opposed to 19:47) is earlier than 08:21 so it looks to me that it refreshed the cookie about 36 min prior to your current time at posting.

[jshimota]

argh! I was thinking that said PM not PDT! On my android emulator the screen is really small and I didn't see it. TY!