linuxserver.io Posted September 27, 2020 Share Posted September 27, 2020 Application Name: Synclounge Application Site: https://github.com/samcm/synclounge Docker Hub: https://hub.docker.com/r/linuxserver/synclounge/ Github: https://github.com/linuxserver/docker-synclounge Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, rather use the linuxserver.io forum for support. Quote Link to comment
BlueLight Posted October 21, 2020 Share Posted October 21, 2020 Hey linuxserver Thanks for this. I've managed to set up the container without any issues. In the template, I entered my reverse proxy url for synclounge (under 'EXTERNAL URL', and left all the optional stuff blank. So, now I'm in the webuil but after I login and select a client, I cannot move past Step 2:Join a Room. Seems synclounge can login and see my server, but cannot connect. It connects fine if I use the actual synclounge website..but the point was to self host synclounge in the first place. My log at startup: Quote ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-config: executing... Fixing permissions. FYI, you don't need to set the PUID env var because this app is stateless [cont-init.d] 30-config: exited 0. [cont-init.d] 99-custom-files: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-files: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. > [email protected] server /app/synclounge > node server.js SyncLounge Server successfully started on port 8089 Running with base URL: /slserver servers/SERVERS must be an Array of JSON objects. Attempting to convert it for you. - Done. SyncLounge WebApp successfully started on port 8088 Running with base URL: /slweb Access URL is sl.xxxxxx.xxx/slweb Servers List: [ { name: 'LSIO Server', location: 'Self-Hosted', url: 'http://sl.xxxxxxxxx.xxx/slserver', image: 'https://avatars3.githubusercontent.com/u/12324908?s=200&v=4' After starting, my log keeps repeating this: Quote Catch all: /slserver/health Catch all: /slserver/health Catch all: /slserver/socket.io/?EIO=3&transport=polling&t=NL8lQ1g Catch all: /slserver/health Catch all: /slserver/health Catch all: /slserver/socket.io/?EIO=3&transport=polling&t=NL8lQuE Catch all: /slserver/health Catch all: /slserver/socket.io/?EIO=3&transport=polling&t=NL8lRH5 Catch all: /slserver/socket.io/?EIO=3&transport=polling&t=NL8lRH5 Any support on this would be greatly appreciated! Quote Link to comment
disbedan015 Posted October 21, 2020 Share Posted October 21, 2020 I had this same error. I solved it by filling in the "EXTERNAL_SERVER_PORT #optional" with the correct server port number 8089. Quote Link to comment
BlueLight Posted October 21, 2020 Share Posted October 21, 2020 Thanks @disbedan015 I had so much hope.. I added 8089 as EXTERNAL SERVER PORT, and at first, it seemed to be working. I can pick up all 3 devices from step 1 (selecting the client), and when I get to step 2, it will attempt to connect, but fails with the same message after 20-30 seconds. This time the error on the bottom of the page shows: 'Failed to connect to http://sl.xxxxxxxxx.xxxx:8089/slserver' I was hopeful because it would instantly show the error message before I added the external server port. After adding it, it stopped showing the Ping or Load, yet when I clicked 'connect', it showed the loading circle, which led me to think it was working... but i got juked. Any additional suggestions to try? Quote Link to comment
disbedan015 Posted October 21, 2020 Share Posted October 21, 2020 Only other thing i did was have port forwarding setup for both 8088 and 8089 so the sever is accessible from the outside web since it defaults to public ip address access. Quote Link to comment
constellation Posted November 30, 2020 Share Posted November 30, 2020 (edited) Tried using this and I'm only getting connect_error no matter what I try. May just revert to the other one i had working via dockerhub. EDIT: OK, got it working by using the sample nginx config straight from SyncLounge instead of the one from LSIO/SWAG. Edited November 30, 2020 by constellation Quote Link to comment
constellation Posted October 26, 2021 Share Posted October 26, 2021 Can no longer select subs or audio tracks... Quote Link to comment
beep Posted June 1, 2022 Share Posted June 1, 2022 Had it running for a week, no longer running and logs now showing after update: Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: /usr/lib/node_modules/synclounge/node_modules/url-join/lib/url-join.js require() of ES modules is not supported. require() of /usr/lib/node_modules/synclounge/node_modules/url-join/lib/url-join.js from /usr/lib/node_modules/synclounge/node_modules/syncloungeserver/dist/socketserver/index.js is an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which defines all .js files in that package scope as ES modules. Instead rename url-join.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from /usr/lib/node_modules/synclounge/node_modules/url-join/package.json. at new NodeError (internal/errors.js:322:7) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1102:13) at Module.load (internal/modules/cjs/loader.js:950:32) at Function.Module._load (internal/modules/cjs/loader.js:790:12) at Module.require (internal/modules/cjs/loader.js:974:19) at require (internal/modules/cjs/helpers.js:101:18) at Object.<anonymous> (/usr/lib/node_modules/synclounge/node_modules/syncloungeserver/dist/socketserver/index.js:15:39) at Module._compile (internal/modules/cjs/loader.js:1085:14) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10) at Module.load (internal/modules/cjs/loader.js:950:32) { code: 'ERR_REQUIRE_ESM' } 1 Quote Link to comment
DazedAndConfused Posted June 4, 2022 Share Posted June 4, 2022 Having the same issue as above. Quote Link to comment
pengsloth Posted June 4, 2022 Share Posted June 4, 2022 I have the same issue. I think I read that updating docker version will work but that isn't really an option for us is it? Quote Link to comment
Heinami Posted June 7, 2022 Share Posted June 7, 2022 If you would like it to keep working you need to specify the version. Set this as your repository on the SyncLounge image for now: lscr.io/linuxserver/synclounge:5.1.113 Here is the release for then. https://github.com/synclounge/synclounge/releases/tag/v5.1.113 Quote Link to comment
pengsloth Posted June 7, 2022 Share Posted June 7, 2022 That worked! Thank you very much. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.