@girish said in Server security update reboot: SFTPGo doesn't start: A package cannot change the port ranges (just like it cannot change the installated domain names) . But for new installation, it will recommend 20000 instead Maybe you can explicitly mention in the update notes the default / advised ports? Existing installs will not be moved to the "new" ports and thus keep having issues?

@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 .