This should be fixed with next release. It was a missing event handler.

@mpeterson0418 On Cloudron, each app is run in a container and has it's own virtual file system. This way one app cannot see another and they can't tamper with each other. This has a wide range of security benefits. This is the reason File manager is inside the app setting.

@nebulon Awesome! Muchas Gracias!

@jdaviescoates so the folder is owned by root even after an app restart?

This is now fixed for the next version. On upload conflict, the code will add .n to the filepath, whereas n is an increasing number until no conflict is found.

@girish so I tried more things and my initial observation cannot be reproduced anymore, so I think I might have been misguided by persistent console logs here.

Now I am not able to reproduce the double upload trigger at all anymore in chromium or firefox. @robi can you maybe explain in more detail how to reliably reproduce this? Do you have any additional extensions installed and can anyone else here see the issue?

@mehdi thanks for reporting, this is fixed now. Next time a separate thread might be better to track those things if possible.

FYI - something in the Cloudron dashboard went stale, hence when reloading the dash, the FM began to load properly.

FileZilla has a Site Manager (File -> Site Manager). You can create named sites.

0cf9295b-7d1c-456b-bec6-64c9cb83bf06-image.png

@nebulon Oh yeah, I had not thought to try the right-click, good catch. Right-clicking on a webpage never feels intuitive to me, except when I want the browser's context menu 🤷

@vladimir-d thanks for debugging this! So, let me create largish archive to see if I can reproduce this.

thx! @girish restarting the sftp service helped… on the overview there was no error.

in the chrome dev tools /console I get still errors btw:
multiple 4040 like:

DevTools failed to load SourceMap: Could not load content for URLHIDDENHERE/3rdparty/js/showdown.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

and also angular js error:

angular.js:13920 ReferenceError: monaco is not defined

@nebulon Ahh okay that makes it clearer why this style was chosen.

I can live with that explanation. 👍

@nebulon Great guys! You're doing amazing !!!

Thanks for the detail @girish

Noted @nebulon - perhaps if the different stages of the startup process were tagged, one could track this more easily.

https://forum.cloudron.io/topic/3661/unable-to-uninstall is the same for another app (mastodon).