PhAzE

Does anyone know how to add chromium node to this docker easily? Trying to allow N8N to download stuff remotely from chrome headless.

Just did an update on the zwaveJSUI docker and zwaveJSUI won't start anymore. Anyone seen this before? node:internal/modules/esm/resolve:283 throw new ERR_MODULE_NOT_FOUND( ^ Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/usr/src/app/server/lib/jsonStore' imported from /usr/src/app/server/bin/www.js at finalizeResolution (node:internal/modules/esm/resolve:283:11) at moduleResolve (node:internal/modules/esm/resolve:952:10) at defaultResolve (node:internal/modules/esm/resolve:1188:11) at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:642:12) at #cachedDefaultResolve (node:internal/modules/esm/loader:591:25) at ModuleLoader.resolve (node:internal/modules/esm/loader:574:38) at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:236:38) at ModuleJob._link (node:internal/modules/esm/module_job:130:49) { code: 'ERR_MODULE_NOT_FOUND', url: 'file:///usr/src/app/server/lib/jsonStore' } Node.js v20.19.0 Press ANY KEY to close this window

Just want to reply back here - BOTH of the shares used between this container and the Plex container need to be set to read/write - shared. I think the Riven symlink mount directory is set to read/write in the template by default, while the other is set correctly. After this, other docker containers can view the rclone mount.

I think I'm almost there with this docker, but rclone doesn't appear to be mounting the external share, and there aren't any errors in the logs even when set to debug... should I be able to CD into the /mnt/debrid/riven directory that it mounts and see the remote files in there?

Hey Squid, i'm getting what appears to be a false positive on a file i created on my USB: /boot/config/usb-rules.cfg corrupted Your flash drive has possible corruption on /boot/config/usb-rules.cfg. This is the contents of that file (which just maps the zwave and zigbee controller from my HUSBZ-1 to static device entities on boot): SUBSYSTEMS=="usb", DRIVERS=="cp210x", ATTRS{interface}=="HubZ Z-Wave Com Port", SYMLINK+="zwave" SUBSYSTEMS=="usb", DRIVERS=="cp210x", ATTRS{interface}=="HubZ ZigBee Com Port", SYMLINK+="zigbee" There doesn't appear to be any corruption in the file, i've recreated it just to be sure, so i'm thinking there is some sort of string of characters that the scan is detecting as corruption.

Was there ever anything dicovered with this? Mine has done the same now since the 6.8.2 upgrade. Wouldn't reboot, then after a few tries it started but the array controls were missing from the GUI, just the powerdown and reboot buttons remained. Edit: after a third reboot, the start button returned.

Hey there! I'm hoping someone can give me a hand with this. New to Nextcloud, trying to set it up using this guide: https://blog.linuxserver.io/2017/05/10/installing-nextcloud-on-unraid-with-letsencrypt-reverse-proxy/ I setup MariaDB, edit the cfg file to uncomment the bind command, log into the db, create the user, db, add permissions, exit, restart the db container. I start up the nextcloud container, access the webGUI, fill it in and click finish, and it seems to just hang there for a while then i get a 504 gateway timeout. Not much data to go on from here. This is on my nginx error.log /mnt/cache/AppData/Nextcloud/log/nginx# cat error.log 2019/08/05 20:44:57 [error] 338#338: *4 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 192.168.1.x, server: _, request: "POST /index.php HTTP/2.0", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.1.y:10002" Where 192.168.1.x is the computer i'm setting this up from, and 192.168.1.y is my NAS IP. I can't seem to figure out why a fresh install isn't working, is there a step i'm missing? I'm not even at the Letsencrypt steps yet, this is just a local setup that's failing. EDIT: I guess moving the log file off the share, and restarting the container got it going.

Yea, this was more to prove that I had the correct docker as the culprit. I just nuked the image and set an extra param path.

Aw man, this saved me. I had a docker with a port binding issue, I guess it was filling logs constantly, but after repairing the bind problem, i didn't know what was eating up the docker image file... logs. *shakes fists into air*

Guess they're totally dealing with a sev1 over there at the moment.

Will this docker end up being the final one when it exits beta, or will the team make another docker for the final version?

Ombi will check Plex directly to see if movies exist in your library vs PlexRequests which checks the movie manager (CP, Radarr, etc). Ombi is based on .net vs PlexRequests which is based on Meteor. Ombi has full user management and collects user info from plex.tv that are friends with your account, to make login easy for them (aka use their plex credentials to log in) It started off as just a fork but has grown a lot faster than PlexRequests.

Hmmm, seems you're right but what's interesting is we actually followed the scheme here and specify the cache dir on startup. Unless I'm missing something. It would seem the cache dir does not follow the data-dir switch. Luckily manually setting it seems to work.

On a fresh install of this docker im getting the followig error: Nginx: [emerg] BIO_new_file("/config/keys/fullchain.pem") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/config/keys/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file) Any ideas? Edit: my conf mistake. Nvm

Every restart of the mylar docker seems to wipe the /app/mylar/cache folder (since its inside the docker and refreshed on each reboot). This cache directory holds the images used by the app, and are not re-downloaded on reboot. I recommend having /app/mylar/cache folder mapped into the config directory, say /config/mylar/cache, after each git clone command. Is it possible to update that so the images cache isn't lost every reboot? EDIT: cache_dir = /app/mylar/cache/ can be set to /config/mylar/cache by default so new installs won't run into this. Doesn't look like its configurable from the Mylar GUI.