Server side keeps breaking every few hours

[ranasats]

Hi,

I'm using the latest docker image. Every few hours the server side of things keeps breaking. The only error I get in logs is this:

Catch all: /slserver/socket.io/?EIO=3&transport=polling&t=N65ptcV

What other info can I provide once this happens again to help troubleshoot? I have to delete the image and rebuild for it to work, simply restarting doesn't do anything, that error still pops up again.

Also with the latest image I get this when starting up now:

ErrorWarningSystemArrayLogin


sh: : unknown operand
Rebuilding Webapp for custom options support. This can take a minute or two.
npm WARN [email protected] No repository field.
npm WARN [email protected] No license field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

audited 11620 packages in 8.946s
found 623 vulnerabilities (159 low, 17 moderate, 447 high)
run `npm audit fix` to fix them, or `npm audit` for details

> [email protected] build /opt/synclounge
> node build/build.js

authentication/AUTHENTICATION must be a JSON object. Attempting to convert it for you.
- Unable to parse '[object Object]'
- Please check your syntax. Reverting to default.
- Done.
Production settings {
webroot: '',
webapp_port: '8088',
accessUrl: '',
autoJoin: 'true',
autoJoinServer: 'https://<domain here>.com/slserver',
autoJoinRoom: '',
autoJoinPassword: '',
authentication: '[object Object]',
customServer: '',
servers: '',
serverroot: '/slserver',
server_port: '8089'
}

[nrgbistro]

I'm having this issue as well.

[MagicalCodeMonkey]

Something is causing your server to forget that the server base is /slserver. I haven't been able to reproduce it with either container I run SyncLounge through or locally. Is there anything else when you run docker logs synclounge (assuming your container is called synclounge) that would point to what is happening? Is something else interacting with your container?

Also, the below error doesn't matter when building, only if it comes up when running the webapp or server. So, you can ignore it.

authentication/AUTHENTICATION must be a JSON object. Attempting to convert it for you.
- Unable to parse '[object Object]'
- Please check your syntax. Reverting to default.
- Done.