ffhelllskjdje Posted April 6, 2021 Share Posted April 6, 2021 (edited) 39 minutes ago, MarkusMcNugen said: Are you mounting that folder to the docker host? If not then it wouldn't have persistence. There is already a volume for persistence that you can use for the container. Check out the docker hub or within pages for the container. You should have /config mounted to the docker host and your ssh key for the SFTP server should go in /config/sshd/keys. You'll probably need to be logged in as root on your Unraid server to get into that folder once you have /config mounted, its locked down pretty hard for security. I've tried both ways, by using a mapped folder and recently by just bashing into the docker container and creating the key under the docker filesystem. I see in the template that the appdata /mnt/cache/appdata/crushftp is mapped to /var/opt/CrushFTP10 in the docker, should I place it there? Edited April 6, 2021 by ffhelllskjdje Quote Link to comment
ffhelllskjdje Posted April 8, 2021 Share Posted April 8, 2021 On 4/6/2021 at 5:29 PM, ffhelllskjdje said: I've tried both ways, by using a mapped folder and recently by just bashing into the docker container and creating the key under the docker filesystem. I see in the template that the appdata /mnt/cache/appdata/crushftp is mapped to /var/opt/CrushFTP10 in the docker, should I place it there? Seems it only works with non admin users, so i just created another user and it seems to work now. Quote Link to comment
MarkusMcNugen Posted April 8, 2021 Author Share Posted April 8, 2021 9 hours ago, ffhelllskjdje said: Seems it only works with non admin users, so i just created another user and it seems to work now. You shouldn't need to create the users manually. You can just them in the config file and the container will create them automatically. If the SSH key exists for the user it will copy it to their authorized_keys file as well. I'm glad you got it figured out at least. Sorry I didn't have team to look I to it further this week. Was waiting for the weekend to test it myself. Quote Link to comment
NLS Posted June 24, 2021 Share Posted June 24, 2021 (edited) Trying to test CrushFTP, but unfortunately the container crushes (sic ) on me immediately after trying to start it. I am pretty sure there is no port conflict. I used an existing user as admin (was that bad) and used a different password than the user's (I assume CrushFTP has its own account management?). Any ideas? What should I look for? EDIT: Tried a different (non existing) user and different "FTP Folder 1". Still same issue. Edited June 24, 2021 by NLS Quote Link to comment
Transient Posted July 28, 2021 Share Posted July 28, 2021 I noticed the Docker container log shows the admin username and password on startup. Is there a way to suppress that? Quote Link to comment
Flemming Posted August 31, 2021 Share Posted August 31, 2021 (edited) On 6/24/2021 at 2:32 PM, NLS said: Trying to test CrushFTP, but unfortunately the container crushes (sic ) on me immediately after trying to start it. I am pretty sure there is no port conflict. I used an existing user as admin (was that bad) and used a different password than the user's (I assume CrushFTP has its own account management?). Any ideas? What should I look for? EDIT: Tried a different (non existing) user and different "FTP Folder 1". Still same issue. I have the same problem. Getting "Execution error, Server error" when staring. From the log I get: Aug 31 03:05:19 UnRAID kernel: device veth8760dc8 left promiscuous mode Aug 31 03:05:19 UnRAID kernel: docker0: port 12(veth8760dc8) entered disabled state EDIT: It worked after I disabled the build-in FTP-server in UnRAID Edited August 31, 2021 by Flemming Quote Link to comment
Roi Posted September 4, 2021 Share Posted September 4, 2021 Hello, I am using the CrushFTP docker container and it works very good for me here. Thank you very much for providing it. But I have one issue: How can I setup the container to write files in the correct user and group ownerships? Files and directories are created with root:root, but all other files on my shares have username:users. Problem for me is that I need to adjust the ownership before being able to rename, move, delete... through the shares. Regards, Roi Quote Link to comment
matuopm Posted April 14, 2022 Share Posted April 14, 2022 Sorry for asking probably stupid questions but I could need a little help with the sftp app. I have the container running and added one user in the /mnt/user/disk1/appdata/sftp/sshd/users.conf like mentioned on the docker page: user:pass:1001:100 When I connect with filezilla I land in this folder: Unfortunately I can not copy something in that folder: I have read permissions, I can copy that .ssh folder for example. And generally read persmissions are enough but how can I specify the folder for a user when I connect to the server. I thought about passing a folder from the host to the containerlike this: But I dont know where I can configure that. Can anyone help me ? Quote Link to comment
pbear Posted April 29, 2022 Share Posted April 29, 2022 On 3/23/2021 at 4:41 AM, Dent_ said: I probably did something to muck this up. Once installed and the container starts I cant access the ui. When looking at the log this is what I get. Is there a permission I am missing? Unzipping CrushFTP... Creating default admin... Admin user written to:./users/MainUsers/ cat: can't open '/etc/system-release': No such file or directory CrushFTP is not currently running... cat: can't open '/etc/system-release': No such file or directory Starting CrushFTP... OK Hello, I have the same problem 1 Quote Link to comment
TheLargeFries Posted June 9, 2022 Share Posted June 9, 2022 Hi @MarkusMcNugen, Thanks for maintaining docker containers! I'm trying to setup the sftp docker to sync/share some files across multiple devices. I read through the instructions, but can't seem to authenticate. I setup a sftp-share user in unraid, and granted read/write permissions to a single share. I then went into the container and configured a username and password, assigning to the same user/group as the unraid user: root@db516ccd2f61:/# cat /config/sshd/users.conf sftp-share:testpass:1000:100 Whenever I try to sftp, I can't authenticate at all; I've tried both terminal, and filezilla. Example: sftp -P 2222 sft-share@<server_IP> enter "testpass" without quotes, and then permission denied. Is there a step I am missing? Thanks in advance for any help! Quote Link to comment
jcofer555 Posted July 24, 2022 Share Posted July 24, 2022 (edited) hi i installed crushftp10, and assigned 4444 as sftp port and 2221 as ftp port, i opened them in the router, and i cannot access this externally via these protocols. https web browsing is working fine but filezilla is not able to connect unless i use the local ip. any ideas? Edited July 24, 2022 by jcofer555 Quote Link to comment
pbear Posted July 29, 2022 Share Posted July 29, 2022 Hello @MarkusMcNugen The CrushFTP v10.3 is out, can you update the docker ? Thanks Quote Link to comment
Nacrana Posted September 28, 2022 Share Posted September 28, 2022 On 7/29/2022 at 11:52 AM, pbear said: Hello @MarkusMcNugen The CrushFTP v10.3 is out, can you update the docker ? Thanks Asking the same question here. Or is this docker project dead? Quote Link to comment
je82 Posted October 12, 2022 Share Posted October 12, 2022 has anyone noticed that this docker may be leaking ram? I have a problem right now where my qbittorrent is taking 12gb of ram, it seems unreasonable high, it starts drawing more and more ram as time goes, anyone else have this issue with this container? Quote Link to comment
Roi Posted October 18, 2022 Share Posted October 18, 2022 On 9/4/2021 at 1:59 PM, Roi said: But I have one issue: How can I setup the container to write files in the correct user and group ownerships? Files and directories are created with root:root, but all other files on my shares have username:users. Problem for me is that I need to adjust the ownership before being able to rename, move, delete... through the shares. Hello, I want to bring this issue up again. I looked into it today and still did not find a solution which works for me. So no settings inside CrushFTP and also no option for the Docker container (as I am not the biggest Docker user this also can be PEBCAK ). Can someone help? Thank you and regards, Roi Quote Link to comment
thany Posted December 9, 2022 Share Posted December 9, 2022 (edited) OpenConnectServer doesn't seem to be working as expected. I just filled in my FQDN (into SRV_CN) and name (into SRV_ORG). I used default settings otherwise, for both client and server. I used the same username&password that I can already use to access shares on unraid. What's next please? Edited December 9, 2022 by thany Quote Link to comment
TBT Posted April 9, 2023 Share Posted April 9, 2023 On 7/29/2022 at 11:52 AM, pbear said: Hello @MarkusMcNugen The CrushFTP v10.3 is out, can you update the docker ? Thanks Thank you very much for your CrushFTP container. I would also kindly ask for a CrushFTP container update, in the meantime 10.4.0 is the most recent version. I noticed that it is possible to internally update the container, the update is gone however, once the container restarts. Quote Link to comment
Sinister Posted April 23, 2023 Share Posted April 23, 2023 Hello i cant seem to open the webui to this docker even though its started in the docker tab, this is what the log is showing. Quote Link to comment
ufo56 Posted April 26, 2023 Share Posted April 26, 2023 Thank you for CrushFTP container! Really useful thing. Any plan to update this ? @MarkusMcNugen Quote Link to comment
pbear Posted August 15, 2023 Share Posted August 15, 2023 Did something change with a recent update ? I cannot connect to the web interface anymore. I checked through the console, and no deamon are listening on 8080 (or 9090) anymore: Quote / # netstat -tulpn Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.11:41081 0.0.0.0:* LISTEN - tcp 0 0 ::ffff:127.0.0.1:40485 :::* LISTEN 113/java tcp 0 0 ::ffff:127.0.0.1:41599 :::* LISTEN 113/java tcp 0 0 :::2222 :::* LISTEN 113/java tcp 0 0 :::22 :::* LISTEN 113/java udp 0 0 127.0.0.11:47546 0.0.0.0:* - Do I have to do something ? KR, Quote Link to comment
ZanR7 Posted September 28, 2023 Share Posted September 28, 2023 (edited) Hi Guys need some help stupid qustion but what is the pass word for markusmcnugen/qbittorrentvpn on unraid i've tried user- admin and password/ adminadmin can't seem to find anywhere. Edited September 28, 2023 by ZanR7 1 Quote Link to comment
Nanobug Posted January 16 Share Posted January 16 Hello, I'm having trouble with the directories of SFTP. Here's my docker run: docker run -d --name='sftp' --net='br0' --ip='10.0.10.64' --privileged=true -e TZ="Europe/Paris" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Skynet" -e HOST_CONTAINERNAME="sftp" -e 'TCP_PORT_22'='22' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://raw.githubusercontent.com/MarkusMcNugen/docker-templates/master/sftp/SFTP.png' -v '/mnt/user/loa/':'/loa':'rw' -v '/mnt/cache/appdata/sftp':'/config':'rw' 'markusmcnugen/sftp:latest' It's the " -v '/mnt/user/loa/':'/loa':'rw'" part that's giving trouble. Here's the users.conf file: For some reason, it can't see the content of the correct folder, it's like it's creating a new one instead of using the one that is mounted. I looked at the Github page on how to do it, and to me it seems right. Does someone have the answer? Quote Link to comment
Caennanu Posted February 8 Share Posted February 8 Hey Guys, Been using crushftp for a bit now, a lil on the down low. The webgui and ftp clients connect just fine, is why i haven't run into an issue yet. However, since i want to start serving the files via an webpage, i need to find the files. Even tho i set the FTP folder variable, i cannot find the uploaded files i can find using the webgui. So i'm wondering, where are the files and folders etc. stored? It seems to be like an in-memory thing? Quote Link to comment
Transient Posted Saturday at 07:14 PM Share Posted Saturday at 07:14 PM (edited) Anyone running the CrushFTP10 container should be aware that there are several critical vulnerabilities in the version of CrushFTP being used (10.0.0). Details are available on their wiki: https://www.crushftp.com/crush10wiki/Wiki.jsp?page=Update I'm not sure what happened to MarkusMcNugen, but he seems to no longer be maintaining these projects. Here's a workaround to this problem: 1. Download CrushFTP 10.7.1 from CrushFTP's website: https://www.crushftp.com/early10/CrushFTP10.zip 2. Save the file into your CrushFTP appdata folder. eg. /mnt/user/appdata/crushftp/update/CrushFTP10.zip 3. Add a new path, mapping the update file to /tmp/CrushFTP10.zip (case-sensitive). The container looks for this file on startup and auto-applies the update, if present. 4. Be sure to set the mapping "Read Only", otherwise the file will be deleted after the update and you'll be back to 10.0.0 on the next startup. Edited Saturday at 10:21 PM by Transient added workaround 2 Quote Link to comment
KoNeko Posted Sunday at 06:47 PM Share Posted Sunday at 06:47 PM 23 hours ago, Transient said: Anyone running the CrushFTP10 container should be aware that there are several critical vulnerabilities in the version of CrushFTP being used (10.0.0). Details are available on their wiki: https://www.crushftp.com/crush10wiki/Wiki.jsp?page=Update I'm not sure what happened to MarkusMcNugen, but he seems to no longer be maintaining these projects. Here's a workaround to this problem: 1. Download CrushFTP 10.7.1 from CrushFTP's website: https://www.crushftp.com/early10/CrushFTP10.zip 2. Save the file into your CrushFTP appdata folder. eg. /mnt/user/appdata/crushftp/update/CrushFTP10.zip 3. Add a new path, mapping the update file to /tmp/CrushFTP10.zip (case-sensitive). The container looks for this file on startup and auto-applies the update, if present. 4. Be sure to set the mapping "Read Only", otherwise the file will be deleted after the update and you'll be back to 10.0.0 on the next startup. i just always update via the webgui/ admin and update there. the update restarts the docker it self. but i have to do another manual restart of the docker and than it works again. just in docker update works fine. But seeing V1 is out https://www.crushftp.com/crush11wiki/Wiki.jsp?page=CrushFTP11New i wonder how long v10 keeps getting updates.. About the currently problem i dont have any of the web functions open outside my network. So that limits it a lot. and for the secure ftp etc its all on IP lock. But still updating it manually. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.