jim80z

By way of an update I also tried to ensure that via the go boot file I add the extra user into /boot/config/vsftpd.user_list. However after boot the file does not have the extra user. Something is overwriting the /boot/config/vsftpd.user_list file post go??

Bump?

All, Is anyone else having a problem where the ftp user list (ie Settings : FTP Server : FTP User(s) ) loses its setting post a reboot? So I have three users listed (assume A B C) with spaces in between and after reboot the third user C always goes missing (first 2 users A & B remain perpetually). Note the first two users A & B have been there for a very long time (read over many years and many versions of Unraid) while the third user C is a recent addition. Im using v6.12.13. I have tried several tests: - I have entered A B C using the GUI ie under FTP Server Settings and user C vanishes after reboot - I have moved user C before A and B using the GUI ie under FTP Server Settings and user C vanishes after reboot - I have gone to the command line and edited /boot/config/vsftpd.user_list to make sure all three users are there and saved the file. This is reflected in the GUI when I checked but after reboot user C vanishes from both the file and the GUI settings - I have gone to the command line and edited /boot/config/vsftpd.user_list and moved user C before A and B and saved the file. This is reflected in the GUI when I checked but after reboot user C vanishes from both the file and the GUI settings - etc Is there another master config file somewhere that copies over the top of the vsftpd.user_list at boot time? I had a look through the forums and from what I found this issue isn't mentioned. This reminds me of having to ensure startup scrips reflected FTP to be started on boot as the server wouldn't remember the settings to restart FTP using the GUI. Anyway this isn't a big problem but it's annoying to have to remember to put the user back in post reboot. Thx

Thank you! After getting it to run and web properly I checked and found regular tests had stopped and I couldn't find the settings page but did find your post! Agree with you comment to update the template and @ZappyZap thankyou for looking into it!!

Hi Disregard the below question........however leaving it here in case someone else finds this useful. I have never had APP_KEY defined but somewhere along the line it must have become mandatory......so when I managed to check the logs (redefined port to map host=8943 to container=80 note this has never been a problem before??) the init had stopped due to the lack of APP_KEY. Once I obtained a generated APP_KEY from https://speedtest-tracker.dev and inserted it, the docker started up no problems. Thx ---------------- Hi guys Im using the following repository "lscr.io/linuxserver/speedtest-tracker:latest" for the speedtest-tracker docker. Somewhere in the last 1.5 months one of the updates broke something and now the webui does not come up "....cant connect to the server.....". Prior to that all worked flawlessly using a seperate mysql docker instance, and the last time I used the web was the end of April. When the docker starts up (successsfuly) in unraid I have the following info (nothing has changed in many months from a parameter POV): docker run -d --name='speedtest-tracker_new' --net='bridge' -e TZ="Australia/Sydney" -e HOST_OS="Unraid" -e HOST_HOSTNAME="XXXXX" -e HOST_CONTAINERNAME="speedtest-tracker_new" -e 'DB_CONNECTION'='mysql' -e 'APP_KEY'='' -e 'DB_HOST'='x.x.x.x' -e 'DB_PORT'='3306' -e 'DB_DATABASE'='YYYYYY' -e 'DB_USERNAME'='ZZZZZZZZ' -e 'DB_PASSWORD'='AAAAAAAAAAAAA' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='022' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8943]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/speedtest-tracker-logo.png' -p '8943:8943/tcp' -v '/mnt/cache/.Apps/appdata/speedtest-tracker':'/config':'rw' 'lscr.io/linuxserver/speedtest-tracker:latest' AAABBBCCCDDEEEE I have tried to: change the network from bridge to host.....no joy I have deleted the container and reinstalled it fresh......no joy changed the port just in case.....no joy I can open the docker CLI for speedtest and can ping out to other machines in my network Any thoughts? Anyone else with the same issues? Thanks