Node MineOS on Ubuntu, short login timeout

Im on git commit: 9e33128

After logging in everything works as expected, however a short time later (5mins?), none of the features work, but it all still looks the same. If I reload the page it takes me to the login screen and once again, everything works after login.

How can I increase the session time (assuming that’s the issue)?

What does your /var/log/mineos.log look like?

I think I found the point at which logins are logged, below is the latest from between two logins. Don’t worry about the rdiff error, I have fixed that.

    {"level":"info","message":"[WEBUI] mcserver connected from removed","timestamp":"2015-12-17T14:20:22.640Z"}
    {"level":"info","message":"[WEBUI] Downloading official profiles.","timestamp":"2015-12-17T14:20:22.735Z"}
    {"level":"info","message":"[Survival] mcserver (removed) joined server namespace","timestamp":"2015-12-17T14:20:23.205Z"}
    {"level":"info","message":"[test] mcserver (removed) joined server namespace","timestamp":"2015-12-17T14:20:23.568Z"}
    {"level":"info","message":"[Survival] transmittting existing file contents: logs/latest.log (154818 bytes)","timestamp":"2015-12-17T14:20:23.732Z"}
    {"level":"info","message":"[test] transmittting existing file contents: logs/latest.log (6681 bytes)","timestamp":"2015-12-17T14:20:23.759Z"}
    {"date":"Thu Dec 17 2015 09:30:00 GMT-0500 (EST)","process":{"pid":24833,"uid":0,"gid":0,"cwd":"/","execPath":"/usr/bin/nodejs","version":"v5.2.0","argv":["/usr/bin/nodejs","/usr/games/minecraft/webui.js","start"],"memoryUsage":{"rss":109416448,"heapTotal":31250720,"heapUsed":26678648}},"os":{"loadavg":[0.25439453125,0.3173828125,0.34228515625],"uptime":146348},"trace":[{"column":11,"file":"util.js","function":"exports._errnoException","line":856,"method":"_errnoException","native":false},{"column":32,"file":"internal/child_process.js","function":"Process.ChildProcess._handle.onexit","line":179,"method":"ChildProcess._handle.onexit","native":false},{"column":16,"file":"internal/child_process.js","function":"onErrorNT","line":345,"method":null,"native":false},{"column":9,"file":"node.js","function":"nextTickCallbackWith2Args","line":455,"method":null,"native":false},{"column":17,"file":"node.js","function":"process._tickCallback","line":369,"method":"_tickCallback","native":false}],"stack":["Error: spawn /usr/bin/rdiff-backup ENOENT","    at exports._errnoException (util.js:856:11)","    at Process.ChildProcess._handle.onexit (internal/child_process.js:179:32)","    at onErrorNT (internal/child_process.js:345:16)","    at nextTickCallbackWith2Args (node.js:455:9)","    at process._tickCallback (node.js:369:17)"],"level":"error","message":"uncaughtException: spawn /usr/bin/rdiff-backup ENOENT","timestamp":"2015-12-17T14:30:00.037Z"}
    {"level":"info","message":"[Survival] Discovered server","timestamp":"2015-12-17T14:30:03.804Z"}
    {"level":"info","message":"[Survival] Created tail on logs/latest.log","timestamp":"2015-12-17T14:30:03.806Z"}
    {"level":"error","message":"[Survival] Create tail on server.log failed","timestamp":"2015-12-17T14:30:03.807Z"}
    {"level":"info","message":"[Survival] Watching for file generation: server.log","timestamp":"2015-12-17T14:30:03.807Z"}
    {"level":"error","message":"[Survival] Create tail on proxy.log.0 failed","timestamp":"2015-12-17T14:30:03.830Z"}
    {"level":"info","message":"[Survival] Watching for file generation: proxy.log.0","timestamp":"2015-12-17T14:30:03.830Z"}
    {"level":"info","message":"[test] Discovered server","timestamp":"2015-12-17T14:30:03.885Z"}
    {"level":"info","message":"[test] Created tail on logs/latest.log","timestamp":"2015-12-17T14:30:03.885Z"}
    {"level":"error","message":"[test] Create tail on server.log failed","timestamp":"2015-12-17T14:30:03.885Z"}
    {"level":"info","message":"[test] Watching for file generation: server.log","timestamp":"2015-12-17T14:30:03.885Z"}
    {"level":"error","message":"[test] Create tail on proxy.log.0 failed","timestamp":"2015-12-17T14:30:03.886Z"}
    {"level":"info","message":"[test] Watching for file generation: proxy.log.0","timestamp":"2015-12-17T14:30:03.886Z"}
    {"level":"info","message":"Starting up server, using commit: 9e33128 update readme to reflect FreeBSD changes\n","timestamp":"2015-12-17T14:30:03.962Z"}
    {"level":"info","message":"[Survival] eula.txt detected: ACCEPTED (eula=true)","timestamp":"2015-12-17T14:30:04.355Z"}
    {"level":"info","message":"[test] eula.txt detected: ACCEPTED (eula=true)","timestamp":"2015-12-17T14:30:04.359Z"}
    {"level":"info","message":"[Survival] autostart = true","timestamp":"2015-12-17T14:30:08.923Z"}
    {"level":"error","message":"[Survival] Aborted server startup; condition not met: !up","timestamp":"2015-12-17T14:30:09.042Z"}
    {"level":"info","message":"[test] autostart = false","timestamp":"2015-12-17T14:30:09.044Z"}
    {"level":"error","message":"[test] Aborted server startup; condition not met: true","timestamp":"2015-12-17T14:30:09.045Z"}
    {"level":"info","message":"[Survival] committing world to disk every 10 minutes.","timestamp":"2015-12-17T14:31:03.836Z"}
    {"level":"info","message":"[test] committing world to disk every 10 minutes.","timestamp":"2015-12-17T14:31:03.887Z"}
    {"level":"info","message":"[WEBUI] mcserver connected from removed","timestamp":"2015-12-17T14:31:20.262Z"}
    {"level":"info","message":"[WEBUI] Downloading official profiles.","timestamp":"2015-12-17T14:31:20.362Z"}
    {"level":"info","message":"[Survival] mcserver (removed) joined server namespace","timestamp":"2015-12-17T14:31:20.633Z"}
    {"level":"info","message":"[test] mcserver (removed) joined server namespace","timestamp":"2015-12-17T14:31:20.937Z"}

I would really appreciate help extending the time, even if this is intended behaviour, I’m comfortable editing scripts and settings.

This isn’t about session time–there isn’t a timeout, or if there is one, it’s a default and it goes at least an hour (because I’ve never experienced it).

Your log, however, seems greatly edited so it isn’t of much use. When you say everything “works as expected”, exactly what works? Because according to your logs, you are doing exactly zero actions before the webui crashes.