Meisner
Hoarder (karakeep) search breaks
I have been having an issue where i cannot user the search function of Hoarder, i have been manually locating things but finally had a moment to check what was going on.
the version of meilisearch had updated since my initial install of hoarder, which resulted in my meilisearch database being on version 1.11.3 but the engine being 1.12 which is not compatible.. there appears to be a manual way to update the database detailed on meilisearches site but for the time being i have just added a user config to force the meilisearch version back down to 1.11.3 and search is working again... anything i added since it broke isn't searchable so i am attempting to re-index them so they will be added..
I assume i missed a release note that included a breaking change. Can anyone point me to where I might find details of when the meilisearch version was changed and what tips or info were hopefully included on completeing the database update within the docker container etc?
1 replies
Wallos seemingly not applying TZ
Hi all, my runtipi tubs in a Ubuntu VM on my proxmox controller. As far as I can tell time/date/timezone are all set correctly and working at proxmox, VM and runtipi level.
I have other apps, like n8n, that timezone matters and it is working correctly.
I am setting up wallos and noticed my notifications were not coming through, reached out to wallos support and after updating the app notifications and now sending but they appear to be a day behind.
I'm in Australia Melbourne and TZ set to Sydney (since Melbourne is usually not accepted) and I had 2ctest subscriptions one for 13th and one for 14th. I set the 13th to notify on due date and 14tg not notify one day before. So at 9am on the 13th (yesterday) I should have got both notifications.. instead I got a notification for a test subscription I had made set to the 12th with on due date notifications.
If I look at the audit log for wallos in the runtipi interface it looks to be logging audit events with my correct date time.
App support has suggested I override the TZ reference to the env file which I will try today.. but I'm not confident it will help.
Any ideas?
18 replies
help understanding which domains are given a certificate
dont have an issue just need help understanding the expected behaviour.
i have dns in cloudflare and have setup the 2 entries pointing at my IP. (sub.domain.com) & (*.sub.domain.com).
Then i have several apps setup that use app.sub.domain.com
I just got an email from le saying cert for *.sub.domain.com was expiring soon. So my question is in runtipi's strucutre does that need a cert (i dont think it does), I believe the *. only had a cert from my previous deployment of cloudron that was using the same sub domain... but that being said I don't know... hence my question 🙂
6 replies
recommendation for nas mount for dockage app access
I have dockage installed and have cloned a notion backup docker app (https://github.com/digitalgenesiskompound/notion-backup) inside dockage app-data stacks folder. (just noting how i was assembling things in case i am mistaken)
i need to mount a nas share to point the backups two (i will also later be wanting to point or rsync the tipi backups there as well).
I believe i should mount the nas share within runtipi/media/
any recommendation as to nfs vs smb/cifs? just using fstab?
do i need to do anything to the mount point in that location to allow the dockage hosted app to access it or am i correct that runtipi/media/ is accessible to all apps?
please excuse any ignorance.
5 replies
n8n GENERIC_TIMEZONE environment value not applying correctly
By default n8n uses America/New York timezone, this is used by scheduling nodes and also shows as the selected timezone in each workflows settings: "Default:America/New York" is what is says.
To change this you set the required timezone as an environment variable. This should get teh schedule/cron nodes running atthe correct time, change the default workflow timezone etc.
I have tried every variation I can think of but cannot get it to apply correctly when running n8n in tipi.
I have set it these ways:
- directly in the docker-compose.yml for n8n-1
- as a reference in the yml to the app.env
- using a user-config yml and app.env both coded directly into the yml or again referencing the .env
It appears the timezone is applying for the schedule nodes and when using now() it is returning in the correct timezone. But the workflow time default value will not change, which makes me quesiton where else it is not applying.
I have a post on n8n community running as well to see if I can get any input there - https://community.n8n.io/t/timezone-setting-doesnt-take-effect/63400
46 replies