kricker

Have you used the information from @DaveHavok? Mine has been rock solid since then. It is currently at 5.0.3 build date 2024-03-02.

I had the same issue and then ended up just redoing the docker container from scratch using the information above from @DaveHavok, and then the note above from me.

I have been having the connections issues now as well. I have totally started from scratch to experiment. I have found that if I remove the password as stated by @zarkoff it will connect once. If you restart the docker and try to connect again it fails. I then have to re-add the password, start the docker, stop it again, then remove the password, restart the docker then I can connect again. I seem to have to repeat this if the docker ever has to be restarted.

Yeah, that may suck, I'd keep a backup of the settings file and database files. Maybe you can swap them out once it's back up and running again.

Did you also delete its folder in your appdata share so that you re-set it all up from scratch?

I'm stumped. Maybe remove the docker and Re-install it?

How about the Docker or whatever is placing files in your media location? Maybe it has different permissions/user/group set. My umask is also set to 000, which I believe is the default. Mine just updated to 4.3.13 and is working just fine as I just did a set of renaming/moving and meta data adding.

What are your user and group IDs in the Docker setup?

It still works just fine. Just no longer being actively developed. But as they say, if it's not broke, don't fix it!

You can manually edit the movie metadata and remove what you don't want.

Are those user and group ID numbers correct? The defaults are user 99 and group 100.

@DrRooo Have you setup the MasqueradeAddress and Passive ports in your proftp.conf file? # using a DNS name MasqueradeAddress xxxxxx.xxxxx.xxx # NAT ports should be safe... PassivePorts ##### ##### Where xxxxxx.xxxxx.xxx is your DNS name (which you can use DuckDNS to get one if you don't already have a static IP or DNS name) and ##### ##### are the passive ports used to connect to the FTP server. An exampl would be something like this: # using a DNS name MasqueradeAddress myserver.duckdns.org # NAT ports should be safe... PassivePorts 50500 50525 Those passive ports then need to be added into your router's port forwarding to go to the local IP of your UnRaid server. You also need to make sure that port 21 (or whatever you changed it to) also is directed to the UnRaid server within the router's port forwarding.

I don't know the issue, but I can say that I just updated mine and it works perfectly.

Thanks. I'll check the syslog. I was out of town and things acted a bit odd but I think there were internet issues.

Is there any way that accessing the FTP server too much would cause it to restart? When not home I am trying to watch my media files remotely using the FTP server as my access. It seems to work quite well, but on occasion it seems I loose access to the server. It may just be random Internet issues, but would I see anything in logs somewhere?

@SlrG Thanks for everything you have done with this plugin. It is very much appreciated.

It is in the "show more settings" section of the docker setup.

Random I think is the key. If ProFTP thinks it has all these ports to randomly choose from but they are not ALL open in the router, then the connection can't happen. Now that I understand this, it makes sense!

So connecting to ProFTP with passive mode is flummoxing me yet again and I just can't understand why. I just made a few small edits to my conf file for folder access and things got messed up, so I started from scratch. I have this in my .conf file: # Server Settings ServerName ProFTPd ServerType standalone DefaultServer on PidFile /var/run/ProFTPd/ProFTPd.pid # using a DNS name MasqueradeAddress xxxxxx.duckdns.org # NAT ports should be safe... PassivePorts 60000 65535 When connecting from an FTP application like FileZilla I get this error and it fails to list the directories even though the user was able to log in: I have ports 60000-60005 open on my router. I had to open them each separately as Google's Home app on Android is broken and does not allow entering a range. I had this same issue in the past and never could figure out how/why it just started working when the configuration is exactly the same. Oddly enough I can use the site net2ftp.com and can connect to ProFTP without issues. EDIT: Okay. I figured out the issue but I do not know the networking voodoo behind it. Since I can only enter one port at a time in my broken Google Home App I only entered from 60000-60005. Once I changed the range in the conf to just be those ports it worked perfectly.

Not sure there is a way. Maybe a cron job that sends some commands to TinyMM if it accepts commands like that.

Happy I could actually help!

In the Docker settings for TMM, what are your USER_ID and GROUP_ID settings? I think for user "nobody" and group "users" they should be set to USER_ID 99 and GROUP_ID 100.

I just bit the bullet and rebuilt the database in the docker version. Having network paths would still be nice though. Another thing I noticed is that I can not open the path to my movies using the path link under a movie's detail page. It always give an error that it can not open the path. I will on occasion use that to quickly check the folders to make sure there are no errant files laying around and that things were renamed properly.

Is there a way to add the paths as network paths such as \\Tower\Movies instead of the local paths? I have TinyMM on my PC and would love to just copy over the database files and settings and start using it in the docker without loosing my current database. On my PC the media source paths were added as a network path.

Awesome to know how to do this!