SakabaRihiro

Fixed my issue below by changing to 1.29.1 per https://community.n8n.io/t/not-able-to-login-to-either-docker-or-npm-version-of-n8n-via-local-network/42120/2 Might work for you as well. Looks like there's a bug with the n8n docker that affects Unraid.

When I log into my container (been using it for a couple of years now, and did the migration a year ago when it was needed) I now receive the following screen (note I did the chown command noted above): Navigating to Settings presents the following error The personal page loads, and I tried to change my password but also get a 401.

I forwarded 5900 to 5901, connecting internal to the network from another machine. TightVNC Settings: Error: For Remote Ripple, I tried it on Windows as well. I wasn't sure whether it was an issue with a custom setting you have for the VNC server on the Docker containers, or whether it's an issue with Remote Ripple. Since RealVNC works I'm not too fussed.

No dice with TightVNC on my end with Windows. "Error in TightVNC Viewer: No security types supported. Server sent security types, but we do not support any of their." Remote Ripple is the successor to TightVNC, TightVNC is now just getting security and bug fixes. No settings for Remote Ripple are available other than IP and Port for connections, and for the application side, setting whether it should automatically check for updates. RealVNC does work though.

Connecting to the JDownloader VNC server (port 5900) with Remote Ripple works, but the connection lasts for less than a second then says "Disconnected". The docker logs don't say anything, and the Remote Ripple logs state the following: Is this something that can be fixed?

Is it possible to disable warnings due to outdated plugins and/or docker containers? I check these manually on a regular basis, but get alerts constantly when an update comes out 12 hours after the check. I'd prefer not to receive the warning, and instead just check manually later. Due to how often I get warnings due to this, I rarely check what the warning notification is for, as I assume it's due to a plugin or docker container, so if there's any actual issues I likely won't notice for quite a while due to thinking it's just something needing an update.

Is it possible to cancel a pending action? I've started a move for a share after changing the Share split level, but then notice some of the folders that will be moved are on the cache drive, which will move them to the desired location with the mover script anyway. Is it possible to cancel these pending moves before they are processed?

Thank you for all your work on the templates. For the Mango template in particular, I'd like to suggest the following changes to make installation a bit easier: Default value for the WebUI (9000, same as is used internally). For the /root/mango mapping: Map to /mnt/user/appdata/Mango/Appdata, as the db, plugins, cache etc are stored here and it is empty and mandatory by default Rename to 'Data', currently it is named 'Config', but this is a mistake, as the name Config is already used for another mapping Change description from 'Mangas' to 'Mango appdata' Change the description on the /root/.config/mango mapping to 'Mango config', as currently it is 'Mango appdata', but this description is inaccurate Add a mapping for the Manga library, possibly empty by default Add a variable mapping for 'library_path', for the Manga library mapping Thank you. Example of the changes

The dev stated "Setting the following env variables might fix it? Honestly not sure with this one." but has also closed the issue stating "Web concurrency now defaults to a single worker. I'm unsure if this changes the Unraid template."

Mealie has a known bug that causes an endlessly large backup file. The dev has stated that he will not address the issue unless someone else provides a PR, as they will not take on the additional burden to support Unraid. Link to said issue.