Hello @valexico I have reproduced it and identified the cause. An app update will be available soon that will fix starting the @sftpgo app without SFTPd initially configured.

Hi and thanks. besides MongoDB ervery service seems okay. Just put the app into recovery mode and back - that helped.

Guys, tyvm for your feedback. As a workaround I simply disallowed dav on a group level. Nevertheless I'll feature request this during Christmas time. ^^

Hello @msbt @msbt said in Connection to server takes 10 seconds in FTP mode and port changes don't work: you think it might be worth reporting upstream? No. I've tested this on another SFTPGo instance that is outside the Cloudron ecosystem, and it worked with no issues. So I must assume we have a mistake somewhere.

FWIW, I can confirm that on Hetzner/Ubuntu this is the default range.

@imc67 https://docs.sftpgo.com/2.6/config-file/#plugins . I haven't been able to find examples of how the json should be written.

Yes, since those are in /app/data they will persist and also be part of the backup

O, I see, this is where I found it: https://docs.sftpgo.com/enterprise/changelog/

@girish thanks!

Users and Groups are not synced. Users will only be available after first login of that user. Groups itself are fully managed within the app itself.

I think this is some docker issue. We see the same issue in our CI and also reported in the Mirotalk threads. Reinstalling fixes the problem as you already found out

An, I had it installed when they weren’t there (?)

yes, the app containers can't connect to private network internal IP . Turns out this is not true, I am able to connect . You might have to use the internal ssh port btw and not the public ssh port .