kricker

Thanks for taking the time to look at it. I was brain dead and didn't even think to test locally first. I'll do that!

So I didn't want to come back and post here, but I have reached my limit trying to find an answer. I have setup ProFTP on another Unraid box. Everything is setup exactly as mine. Once again I am having issues trying to connect to it. I am once again stuck at retrieving a directory listing. It never populates and eventually times out. All the ports, active and passive are setup in the config file and forwarded properly in the router which is the exact router I have. I've turned on logging and these are the last lines where it just times out. Is there any clue in this? Aug 2 23:48:26 Houston proftpd[11973]: 127.0.0.1 (24.158.124.213[24.158.124.213]) - in dir_check_full(): path = '/', fullpath = '/mnt/user/' Aug 2 23:48:26 Houston proftpd[11973]: 127.0.0.1 (24.158.124.213[24.158.124.213]) - dispatching LOG_CMD command 'PORT 24,158,124,213,201,65' to mod_log Aug 2 23:48:26 Houston proftpd[11973]: 127.0.0.1 (24.158.124.213[24.158.124.213]) - dispatching PRE_CMD command 'MLSD' to mod_tls Aug 2 23:48:26 Houston proftpd[11973]: 127.0.0.1 (24.158.124.213[24.158.124.213]) - dispatching PRE_CMD command 'MLSD' to mod_rewrite Aug 2 23:48:26 Houston proftpd[11973]: 127.0.0.1 (24.158.124.213[24.158.124.213]) - dispatching PRE_CMD command 'MLSD' to mod_core Aug 2 23:48:26 Houston proftpd[11973]: 127.0.0.1 (24.158.124.213[24.158.124.213]) - dispatching PRE_CMD command 'MLSD' to mod_core Aug 2 23:48:26 Houston proftpd[11973]: 127.0.0.1 (24.158.124.213[24.158.124.213]) - dispatching CMD command 'MLSD' to mod_facts Aug 2 23:48:26 Houston proftpd[11973]: 127.0.0.1 (24.158.124.213[24.158.124.213]) - in dir_check_full(): path = '/', fullpath = '/mnt/user/' Aug 2 23:48:26 Houston proftpd[11973]: 127.0.0.1 (24.158.124.213[24.158.124.213]) - ROOT PRIVS at inet.c:409 Aug 2 23:48:26 Houston proftpd[11973]: 127.0.0.1 (24.158.124.213[24.158.124.213]) - ROOT PRIVS: ID switching disabled Aug 2 23:48:26 Houston proftpd[11973]: 127.0.0.1 (24.158.124.213[24.158.124.213]) - RELINQUISH PRIVS at inet.c:483 Aug 2 23:48:26 Houston proftpd[11973]: 127.0.0.1 (24.158.124.213[24.158.124.213]) - RELINQUISH PRIVS: ID switching disabled

I am running into this quite a lot lately. Did you ever look into this more? I am working with a couple other freelancers and we are all using my FTP to access files. When one of them uploads files to the server and I then go to manage said files, I get permission issues. I have to login to login to the tower terminal and run chown and chmod commands so that I can manage the files. I just change the umask to 000, so I'll be interested to see how that fairs. It would be great if somehow the ownership could default to nobody like unRaids defaults.

Based on that, I upgraded to 6.7.0-rc3 today as well. ProFTP seems to be working just fine for me as well.

Good to know, I'll be staying off 6.7.x until then. Thanks for the heads up @d2dyno. And thanks @SlrG for taking a look when you can.

Thanks. I already stumbled through the thread and found some info. That will be a task for another day. Now I am refreshing myself on folder/file/user access limits. I had it setup years ago, but then when I removed the plugin and reinstalled trying to fix my issue, I nuked my original .conf file, so I am re-learning all those configurations I am getting there! I appreciate all the assistance.

I have others that connect to my server, that don't need VPN access. I got it working using a different external port that is forwarded to ProFTP's port set in the config file. It is working good now. When connecting now though, Filezilla gives a warning: This server does not support FTP over TLS. if you continue, your password and files will be sent in clear over the internet.

Thanks. I did a lot of reading last night and added this to my config last night but never had success. # using a DNS name MasqueradeAddress ######.####.### # NAT ports PassivePorts #### #### My actual DNS and ports are inserted above. The port range has been added to my Google router properly (I believe). Using a port checker I only ever get a response if I use the default port 21 (when I have that forwarded as well on the Google router). If I use any other port and forward it to 21, I get no response. I also get no response when using any of the ports in the passive range. I am turning on the debug logging now to see what I can learn. EDIT: Well, it is working now. I'm not sure what I did different besides turning on logging. It was late and I was tired, maybe I had a typo or the ports were not quite right. Anyhow, Thanks for all the help. I believe all is good now.

I don't understand what most of that meant, bit I'll look it up! Thanks!

I am having issues now connecting to ProFTP remotely. It works fine using the local IP. I recently bought the Google Wifi mesh system and in doing so I needed to get a different DynamicDNS form the Asus one I was using. So I am using the DuckDNS Docker for Unraid and have it up and running. All my dockers are accessible just fine using the DynamicDNS. But I keep getting erros when trying to connect to ProFTP. FileZilla shows the following: Status: Logged in Status: Retrieving directory listing... Status: Server sent passive reply with unroutable address. Passive mode failed. Command: PORT 24,158,124,213,211,191 Response: 500 Illegal PORT command Error: Failed to retrieve directory listing With each failed connection, the log shows: Jan 4 15:13:07 TOWER proftpd[30779]: 127.0.0.1 (192.168.0.1[192.168.0.1]) - Refused PORT 24,158,124,213,212,223 (address mismatch) I have my router sending port #### to the internal port 21.

Do you still have these? If so would $60 buy them?

When I first installed this Docker it was setup with networking in Host mode. I tried switching to Bridge mode, but when I do that nothing will play and I get streaming errors in the myMedia webGUI. I did setup my router to pass ports 52050 and 52051 to my tower. I'll admit I don't fully understand Host vs Bridge. I keep reading about it and THINK I understand it, but when this didn't work I am no longer sure I do.

Yeah, can't hurt! I have 2 slots, I can swap and get two 4gig sticks for 8 gig total, or two 8gb sticks for 16gb. Would 16 be a waste?

I have 4gigs of RAM. I have 5 docker apps running. I have thought about getting more RAM. Do you think that is all it is? Any other oddities in the log?

I have been having this issue for quite a while now. I believe it started after upgrading to 6.5.0. All my docker apps become unresponsive randomly. When accessing Unraid webGUI the Docker tab takes a few minutes to populate if ever. All the other webGui tabs work fine. Looking at the log I see I am having memory issues, but I do not know if that is the cause of the problem or another one. I've seen other threads with memory issues and docker problems, but none have them have provided any solutions for me. tower-diagnostics-20181204-1335.zip

I get odd files in my database folder. DLL files and ~ files. I can remove them, but they always come back. MariaDB doesn't need these files to work, so I am not sure what they are or where they come from. I am only using Kodi with MariaDB. Does anyone else get these files?

So 9 days and 5 hours later my tower is stable as ever. Somehow turning off VMs helped keep it stable.

So after turning off VMs completely (I noticed that it was enabled a while back, but never worried about it) my unRaid tower has been running stable.

I believe these are logs right before my upgrade. tower-diagnostics-20180426-0707.zip

Here are my current logs tower-diagnostics-20180426-0832.zip FCPsyslog_tail.txt

I have FCP in troubleshooting mode again. Once again it is running fine. If I turn off troubleshooting mode and it crashes, it is at a state that I can't pull any logs.

It just happened again right after I upgraded to v 6.5.1. It had barely run for 10 minutes before it became unresponsive. Once again I could not grab any logs only a screenshot of a remote KVM session. This is getting really frustrating. It works fine when FCP plugin is running in troubleshooting mode.

My unRaid server has become increasingly unstable. It has random lockups. It is unresponsive to anything. I can't pull diagnostics when it gets in the state. The best I can do is grab logs after a forced shutdown and a screenshot of a remote KVM session while it is locked up. I've attached it. If I run "Fix Common problems" in troubleshooting mode, it never seems to lock up. I am going to try again, but this is getting frustrating. It seems to have all started after upgrading from 6.3.5. I am currently on 6.5.0. tower-diagnostics-20180422-0854.zip

The unBalanced plugin calls it a "server", so I just referred to it as that. Since I wasn't currently using it for anything I figured I might has well "turn it off". I understand it doesn't run all the time and it may very well be a coincidence. I'm just reporting what is currently happening.