Cloudron Forum

I was in the early alpha test stage, great concept but at that point it was a bit clunky to use and the UI was a lot more barebone.

Seems like they did a lot of improvements. Time to have a look at it again!

I will probably end up with a different solution

I teste FileRun in a LAMP app (after reading @scooke reply here) and it does exactly what I need without all the added bloat and unpolished UI of Nextcloud.

It sorts pictures by date taken
Has a better UI than NextCloud (personal opinion)
It is a lot faster in previewing images
Works with the Nextcloud desktop and Android client (or any other app that supports webdav)
Can organize photos in albums and collections (I am not really interested in this, but it's a nice to have)

I hope that it will officially come to Cloudron at some point.

Try restarting either Umami or rebooting the server, after that Umami should stop working (you will see an error in the browser's console when loading the site).
Then after restarting/rebooting again, it will work again.

Basically it stops working every other reboot, so when a reboot is needed I need to reboot twice to get Umami to work.

Not sure if it matters, but in my case the website I am tracking is on a different server than Umami.

Seems nice, it's quite similar to YNAB, isn't it? Well, definitely more than Firefly III.

The method I linked above works, but it has a big drawback: each time the script runs it reprocess ALL files in the folder and subfolders, which is a waste of resources in my case.

I have two ideas in mind:

• Keep the InstantUpload folder created by the Andoird client as a temporary folder, and edit the script to process the images in it and move them to a different MobileBackup folder every hour.

or

• Use Nextcloud flows in conjunction with the Workflow external script to use a similar script and process each file as soon as it's uploaded in a specific folder.

I will do some tests (maybe not soon) and report back.

I just did a fresh install of Umami a few days ago, on May 13th, and I am experiencing the same exact issue.

Initially everything works.
If I restart the app, then on the site it loads a 200 for the js file but a 400 for the XHR request (so the data is not logged).
If I restart the app again, it works again as expected.
And so on...

The only customization I have is in the env.sh where I added

export TRACKER_SCRIPT_NAME=get.js
export COLLECT_API_ENDPOINT=/api/get

The installed version is:

App Title and Version: Umami 2.2.0
Package Version: is.umami.cloudronapp@3.1.0

This issue persists and can't understand why it's happening.
Every time a reboot is required I need to remember to manually restart Umami, or it stops working.

So weird that it happens every other reboot/restart.

I just set up Cloudron a few weeks ago, and I am slowly moving all my emails there (only personal, family and work stuff... so not many addresses, and not a lot of volume).

In my initial tests I only had issues getting delivered to Outlook and Yahoo and I haven't been able to figure out why. My IP is clean!

Now I am using Amazon SES and all seems to work smoothly

I think this commit fixes the issue?
https://github.com/kaleidos-ventures/taiga-back/commit/a46da85efafe976175847b850fd90d61c7dee633

By reading the PhotoPrism thread in Wishlist Apps it seems to be difficult to package for Cloudron... I have zero knowledge about docker (that's why I am using Cloudron ) so I hope it will be in the store one day!

Ok, no worries

Yes, it doesn't depend on the browser. I tried with Chrome, Edge, Firefox and Brave (even with shields off), without any ad-blocking extension enabled.

Maybe this could be a temporary but valid solution using Nextcloud https://rayagainstthemachine.net/linux administration/nextcloud-photos/ (read the part about Exiftool).

I will try this week

Sometimes I just need a static IP to be whitelisted on client's services, servers, etc.
My home internet connection doesn't provide me with a static IP.

I hit this wall a couple of days ago when I wanted to try out Taiga.
I chimed in the Github issue linked above, but it is open since September 2021...