@girish Thanks for the assistance.
Apparently this was caused by a misconfigured IPv6 / Ubuntu installation script which my host helped me diagnose and correct. Thank you for your help, I'm glad I stumbled upon Cloudron.
Correct, those "providers" are two different ones conceptually. One is where the server is hosted. This allows us to apply some VPS provider specific quirks, if required.
The DNS/Domains provider is the one where the domain is registered or at least the nameservers for that domain. This may or may not be the same company as the VPS provider, but they have otherwise nothing in common.
So, it seems like giving the app a "relocation" by pressing the save button under the Location config tab & a quick Cloudflare proxy off-on, and then some time is the fix.
EDIT
So it is Cloudflare that is the problem and not Cloudron. Specifically their proxy
@christiaan You can manually setup filters in SOGo, Rainloop, Roundcube, etc in Cloudron to do the exact same thing here. I can assist in a PM if you would like help setting this up.
@cyanogenic Did you install/enable any nextcloud plugins? This usually happens when one of the nextcloud plugins is not too happy. Try this https://cloudron.io/documentation/apps/nextcloud/#fixing-a-broken-install . Or if you have nothing important in it, I would just re-install nextcloud.
To add, the answer is that all the apps under apps/ are pre-installed as per this comment in code.
So, https://github.com/nextcloud/server/tree/master/apps is the list
@foliovision said in SFTP Missing for some apps?:
Hi Girish, Thanks for your quick answer. I did get as far as trying to edit the .env file with Vim in the Cloudron terminal. I think specifically with the .env file in Invoice Ninja that it's read only in Cloudron. Let me know if I'm wrong.
Yes, the file will be editable. In fact, we pushed an update yesterday to move the env file location to /app/data/env (instead of /app/data/.env). Can you please check again if it's writable and report here? Note you will have to restart the app (Console -> Restart) after making changes.
@girish The manual check method is good enough for me. If you do the release channel thing thats cool. But for those of us that a hungry, an extra few clicks isn't a bother.
To add here, SSHd configs are very often VPS provider specific even, not just Ubuntu. So ideally Cloudron should not try to manage too much around that, since then this might interfere with for example SSH recovery strategies from VPS provider.
Generally it is always a good idea to use ssh keys instead of password.
