Closed JoshMcCullough closed 5 years ago
Are you using http or https? I suspect your problem is you are using http and the MAGE_SESSION_COOKIE_SECURE environment variable is not set to false.
Good call. I did set MAGE_SESSION_COOKIE_SECURE
tofalse
because we're proxying requests to the server so we don't use HTTPS internally. Are you suggesting I have to set MAGE up initially without this env var set tofalse
but can re-set it afterward?
Yeah, all good here. Thanks.
where to you find MAGE_SESSION_COOKIE_SECURE ?
@fm-davidcraig It's used in env.js
, but you declare it when you're starting MAGE e.g. MAGE_SESSION_COOKIE_SECURE=false; npm start
FYI setup seems to be broken on
master
. I accidentally grabbed master instead of 5.2.5, and noticed that during first run / setup, after entering the initial device id/uid, I get a 401.Unfortunately I am having the same issue with 5.2.5 -- fresh install on a fresh Mongo v3.4.20 instance. Here is the log: