zarkoff

Sorry, I didn’t have time to check before. I deleted an old MariaDB container, removed the syncin container, and tried again. It worked a little further, but I got this message in the MariaDB container and I’m not sure what it means: 2026-02-13 21:59:35 3 [Warning] Aborted connection 3 to db: 'syncindb' user: 'syncinuser' host: '192.168.1.56' (Got an error reading communication packets) I think I might have to give up. Thank you for your help. EDIT 15/02/2026: I finally got it working by following this tutorial, but I used your existing container instead of creating a new one from the template. Here’s what I did differently this time: Deployed the MariaDB container first, using these extra parameters: --user=99:100 --memory=4G --memory-swap=-1 (with a dedicated IP on br0 and keeping the default port) Deployed a Redis container—I’m not sure if it was necessary, but I did it anyway. (with a dedicated IP on br0 and keeping the default port) Uploaded the environment.yaml file before deploying the Sync-in container. Deployed the Sync-in container (with a dedicated IP on br0 and keeping the default port). I did not install OnlyOffice, as it is optional. Now it works! I’m still not sure what the game changer was: the extra MariaDB parameters, adding Redis for caching, or simply uploading environment.yaml before deploying the Sync-in container.

Thank you for taking the time to help me. Here is the docker command (I just changed the HOST_HOSTANME) /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='Sync-in' --net='br0' --ip='192.168.1.76' --pids-limit 2048 -e TZ="Europe/Paris" -e HOST_OS="Unraid" -e HOST_HOSTNAME="MyLab" -e HOST_CONTAINERNAME="Sync-in" -e 'TCP_PORT_8080'='8080' -e 'INIT_ADMIN'='true' -e 'PUID'='099' -e 'PGID'='100' -e 'CA_TS_FALLBACK_DIR'='/app/environment/environment.yaml' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8080]/' -l net.unraid.docker.icon='' -v '/mnt/user/appdata/sync_in/environment.yaml':'/app/environment/environment.yaml':'rw' -v '/mnt/user/appdata/dynamix/data':'/app/data':'rw' -v '/mnt/user/appdata/sync_in/releases':'/app/static/releases':'ro' 'syncin/server:1' But I did some additional test and: if I start WITHTOUT starting mariadb container, it starts with error of course: Error: unable to migrate database schema ! Error: connect ECONNREFUSED 192.168.1.76:3306 at createConnectionPromise (/app/node_modules/mysql2/promise.js:19:31) at connectToMySQL (/app/node_modules/drizzle-kit/bin.cjs:81027:47) at process.processTicksAndRejections (node:internal/process/task_queues:103:5) at async Object.handler (/app/node_modules/drizzle-kit/bin.cjs:93700:39) at async run (/app/node_modules/drizzle-kit/bin.cjs:93117:7) { code: 'ECONNREFUSED', errno: -111, sqlState: undefined } Error: unable to migrate database schema ! Reading config file '/app/server/infrastructure/database/configuration.js' if I start with mariadb container, it crashes immediately. I tried with official mariadb countainer or linuxserver'one, it's the same. But what's strange, is that it doesn't return an error when trying to connect, it just crashes. Thank you

I've a dedicated mariadb for sync-in, I checked db_name, db_user, and db_password is here the yaml file, all secret are generated via openssl rand -hex 32 command environment-for forum.yaml Here is the message, it closes immediately. log file of the docker says nothing, so I don't know what's wrong...

Hi, thanks for your help. I deleted the file and replaced it with the YAML file instead. Now, Unraid returns an "Execution Error: Bad parameter." I’m not sure if the issue is with what I put in my YAML file or something else, since the log doesn’t show anything. Maybe it’s the MariaDB version or something similar. Here’s what I put in my YAML file—did I miss anything? Does it work for you? mysql: url: mysql://user:[email protected]:3365/dbname auth: encryptionKey: *** generated with openssl rand -hex 32 *** token: access: secret: *** generated with openssl rand -hex 32 *** refresh: secret: *** generated with openssl rand -hex 32 *** applications: files: dataPath: /app/data collabora: enabled: false onlyoffice: enabled: false secret: *** generated with openssl rand -hex 32 ***

Hi, I’m trying to install Sync-In (maintained by @grtgbln , of course). First, thank you for the XML. According to the requirements, I’ve created a MariaDB database and an environment.yaml file. I placed this file in /mnt/user/appdata/sync_in/environment.yaml, but Sync-In can’t find it (error: not found). I didn’t change anything in the XML file except the port, which was already in use by another container. I tried moving the file to a different folder and changing its permissions, but I still get the same error: environment.yaml is not found. Just to clarify, I downloaded the yaml file from GitHub (https://github.com/Sync-in/server/releases) and edited it to add the MariaDB endpoint and encryption keys. Do you have any idea how I could fix this?

Ah super, it works which is strange because I thought OpenDNS was blocked in France (where I am). Thank you so much Edit: well in fact they are... I put other DNS than OpenDNS and it's ok. And I think this is was linked to a problem with AWS affecting a lot of web services... including Orange, my ISP.

Hi, Currently, almost all of my Docker apps are showing as "Not available." I’m running version 7.1.4. I’ve tried the following troubleshooting steps, but the issue persists: Forced an update Edited the app template Restarted my server When I went to the "Apps" tab, a pop-up message briefly appeared—something about "fix..."—but it disappeared before I could read or click on it. Do you know what I can do or where I should look to resolve this issue? Or could this be a temporary problem?

Hi, Sorry I did not notice your answer. I've changed Owner to nobody and access permission and now it works. Thank you.

I've this: /mnt/user/appdata/dumbpad

Hi, I can't get DumbPad to work. Is there any additional setup to do (create en env. or something) ? It looks like a problem of permission. Thank you. LOG

Hi, Do you know how to reset "File Size Metrics Data Panel" ? I would like to either remove some files from stat (because I ran unmanic for someone else) or reset to zero as a fresh start. (and same for Video Library Stats Data Panel) ? Thank you.

Hi, well I did exactly the same, I doesn't work for me. It seems that your solution works for some people, but unfortunately not for me, and I don't understand why. Thank you very much for taking the time to help me. I am moving to another Docker container that does not use Selkies.

Thanks, but even forcing https:// and port 3001 and JPEG, results the same (for me, at least) In log I see this do you what it means? do we have to do something with port 8082 ?

Hi, I tried but this is the same with https and 3001: waiting for stream... See the 2th line of log below is warning me about something but I don't know how to fix. Log Firefox INFO:data_websocket:Initial client settings message processed by ws_handler. WARNING:data_websocket:Initial setup: Video pipeline for 'x264enc' was expected to be started by applyclient_settings but is not. This might indicate an issue or a no-op change. WARNING:webrtc_input:No clipboard content to send INFO:data_websocket:Received START_VIDEO for encoder: x264enc INFO:data_websocket:Starting x264enc: 3386x1256 @ 60.0fps, CRF: 25, FullFrame: True INFO:data_websocket:New frame backpressure task started (current encoder: 'x264enc'). INFO:data_websocket:x264enc capture started successfully. INFO:data_websocket:Received START_AUDIO command from client for server-to-client audio. INFO:data_websocket:START_AUDIO: Server-to-client audio pipeline already reported as active. INFO:data_websocket:Frame-based backpressure logic task started. INFO:data_websocket:Client settings received, proceeding with backpressure loop. INFO:data_websocket:Cleaning up Data WS handler for ('127.0.0.1', 56436)... INFO:data_websocket:Client ('127.0.0.1', 56436) disconnected, but other clients remain. Frame backpressure task continues. INFO:data_websocket:Client from ('127.0.0.1', 56436) disconnected. Checking responsiveness of remaining 1 client(s)... INFO:data_websocket: Remaining client ('127.0.0.1', 46538) is responsive. INFO:data_websocket:Client from ('127.0.0.1', 56436) disconnected. Responsive clients (1) remain. Global pipelines will NOT be stopped by this handler. INFO:data_websocket:Data WS handler for ('127.0.0.1', 56436) finished all cleanup. INFO:data_websocket:Frame-based backpressure logic task started. INFO:data_websocket:Client settings received, proceeding with backpressure loop. INFO:data_websocket:Stats sender: WS connection closed. INFO:data_websocket:Cleaning up Data WS handler for ('127.0.0.1', 46538)... INFO:data_websocket:Last client (('127.0.0.1', 46538)) disconnected. Cancelling frame backpressure task. INFO:data_websocket:No other clients in set after ('127.0.0.1', 46538) disconnected. Marking pipelines for stop. INFO:data_websocket:Stopping global pipelines due to last client disconnect (('127.0.0.1', 46538)). INFO:data_websocket:Stopping X11 x264-striped capture... INFO:data_websocket:Frame-based backpressure logic task cancelled. INFO:data_websocket:Frame-based backpressure logic task finished. INFO:data_websocket:Backpressure task was stopped. Calling resetframe_ids_and_notify. INFO:data_websocket:Resetting frame IDs. INFO:data_websocket:Frame IDs reset, but no clients to notify. INFO:gst_app:Stopping WebSocket audio pipeline... INFO:gst_app:WebSocket audio pipeline stopped. INFO:data_websocket:Data WS handler for ('127.0.0.1', 46538) finished all cleanup. INFO:data_websocket:Frame-based backpressure logic task started. INFO:data_websocket:Client settings received, proceeding with backpressure loop. INFO:data_websocket:Stats sender: WS connection closed. INFO:data_websocket:Data WebSocket connected from ('127.0.0.1', 49196) INFO:data_websocket:Broadcasting stream resolution: {"type": "stream_resolution", "width": 3386, "height": 1256} INFO:data_websocket:Attempting to establish PulseAudio connection... INFO:data_websocket:PulseAudio connection established. INFO:data_websocket:Applying client settings (initial=True): {'videoBitRate': 16000000, 'videoFramerate': 60, 'videoCRF': 25, 'encoder': 'x264enc', 'h264_fullcolor': False, 'resizeRemote': True, 'isManualResolutionMode': False, 'manualWidth': 3386, 'manualHeight': 1256, 'audioBitRate': 128000, 'videoBufferSize': 0, 'initialClientWidth': 3386, 'initialClientHeight': 1256} INFO:data_websocket:Initial client settings processed and event set by applyclient_settings. INFO:data_websocket:Initial client settings message processed by ws_handler. WARNING:data_websocket:Initial setup: Video pipeline for 'x264enc' was expected to be started by applyclient_settings but is not. This might indicate an issue or a no-op change. INFO:data_websocket:Initial setup: Audio pipeline not yet active, attempting start. INFO:gst_app:Starting WebSocket audio pipeline... INFO:gst_app:Building WebSocket audio pipeline... INFO:gst_app:Audio pipeline state change to PLAYING is ASYNC. INFO:gst_app:WebSocket audio pipeline started. WARNING:webrtc_input:No clipboard content to send INFO:data_websocket:Received START_VIDEO for encoder: x264enc INFO:data_websocket:Starting x264enc: 3386x1256 @ 60.0fps, CRF: 25, FullFrame: True INFO:data_websocket:New frame backpressure task started (current encoder: 'x264enc'). INFO:data_websocket:x264enc capture started successfully. INFO:data_websocket:Received START_AUDIO command from client for server-to-client audio. INFO:data_websocket:START_AUDIO: Server-to-client audio pipeline already reported as active. INFO:data_websocket:Frame-based backpressure logic task started. INFO:data_websocket:Client settings received, proceeding with backpressure loop. INFO:data_websocket:Cleaning up Data WS handler for ('127.0.0.1', 49196)... INFO:data_websocket:Last client (('127.0.0.1', 49196)) disconnected. Cancelling frame backpressure task. INFO:data_websocket:No other clients in set after ('127.0.0.1', 49196) disconnected. Marking pipelines for stop. INFO:data_websocket:Stopping global pipelines due to last client disconnect (('127.0.0.1', 49196)). INFO:data_websocket:Stopping X11 x264-striped capture... INFO:data_websocket:Frame-based backpressure logic task cancelled. INFO:data_websocket:Frame-based backpressure logic task finished. INFO:data_websocket:Backpressure task was stopped. Calling resetframe_ids_and_notify. INFO:data_websocket:Resetting frame IDs. INFO:data_websocket:Frame IDs reset, but no clients to notify. INFO:gst_app:Stopping WebSocket audio pipeline... INFO:gst_app:WebSocket audio pipeline stopped. INFO:data_websocket:Data WS handler for ('127.0.0.1', 49196) finished all cleanup. INFO:data_websocket:Frame-based backpressure logic task started. INFO:data_websocket:Client settings received, proceeding with backpressure loop. INFO:data_websocket:Stats sender: WS connection closed. X Shared Memory Extension available. XShm setup complete for 3386x1256. CPU cores available: 8 Res: 3386x1256 Mode: H264 (CPU) CS_IN:I420 LR FF Stripes: 1 CRF:25 EncFPS: 6.00 EncStripes/s: 6.00 Res: 3386x1256 Mode: H264 (CPU) CS_IN:I420 LR FF Stripes: 1 CRF:25 EncFPS: 0.00 EncStripes/s: 0.00 Res: 3386x1256 Mode: H264 (CPU) CS_IN:I420 LR FF Stripes: 1 CRF:25 EncFPS: 0.00 EncStripes/s: 0.00 Capture loop stopped. X resources released. X Shared Memory Extension available. XShm setup complete for 3386x1256. CPU cores available: 8 Res: 3386x1256 Mode: H264 (CPU) CS_IN:I420 LR FF Stripes: 1 CRF:25 EncFPS: 5.00 EncStripes/s: 5.00 Res: 3386x1256 Mode: H264 (CPU) CS_IN:I420 LR FF Stripes: 1 CRF:25 EncFPS: 0.00 EncStripes/s: 0.00 Res: 3386x1256 Mode: H264 (CPU) CS_IN:I420 LR FF Stripes: 1 CRF:25 EncFPS: 0.00 EncStripes/s: 0.00 Res: 3386x1256 Mode: H264 (CPU) CS_IN:I420 LR FF Stripes: 1 CRF:25 EncFPS: 0.00 EncStripes/s: 0.00 Res: 3386x1256 Mode: H264 (CPU) CS_IN:I420 LR FF Stripes: 1 CRF:25 EncFPS: 0.00 EncStripes/s: 0.00 Capture loop stopped. X resources released.

Hello, I was using a Firefox application, specifically the one from lscr.io/linuxserver/firefox. It was working well until a recent update changed the "renderer" (I'm not sure what it's called) from VNC or KasmVNC to Selkies. However, Selkies isn't rendering anything. All I see is a message that says, "waiting for stream...", but nothing happens, and none of the available options seem to help resolve the issue. As a temporary fix, I installed an alternative Firefox ESR version that still uses the old renderer. However, I'm concerned this issue might affect other containers with web rendering capabilities, so I'd like to find a permanent solution. Do you have any suggestions on how to fix this? Is there an option I should enable or disable, either within the container or in the Docker settings? I'm on 7.1.4 version of Unraid.