Cloudron Forum

@LoudLemur Yes, they also ran other bench tests. AFAIK No, Hermes is a different UI and harness.

@joseph Thanks for the pointers. Upon further investigation on deSEC side, this might point to a temporary server overload with potential ways the help the issue. How does the Dynamic DNS update work on Cloudron's side. What does the cron table entry look like for this? (Is there a place where I should be looking for this info somewhere / additional tech info on cloudron's side?) Also, do you think that some of these suggestions are implementable (if not already present)? Many thanks again

@nebulon Thanks for this - I can confirm that this is an issue with the S3 endpoint and a faulty server app release not accepting upload and throwing HTTP/1.0 400 errors. If I may: The error message about MD5/checksum from Cloudron throw me off for a bit, not directly pointing at a lack of communication with the remote server. Reverting to and earlier release on the S3 endpoint fixed the issue.

@josephcosta Hmm. I'll check it out later today or tomorrow. Thanks for testing!

AlternativeTo link:- https://alternativeto.net/software/notediscovery/about/

Works great! Thanks a lot for the quick help!

Same issue here, looks like the latest update activates a new plugin, but does not run its db migration automatically. The fix is to run console core:update a second time.

@joseph practicality, probably. GitHub's free offering is still very attractive.

@girish happy to help, thanks for picking this up!

@joseph any support here wished/needed? Would be happy to contribute and get the fulltext search to Linkwarden.

Hi @joseph Thanks for this. I can confirm that vector is now enabled. Docmost is still complaining when I activate the option, but I see no "page_embeddings" tables at the moment so I will wait for a potential background creation and report. Thanks again,

@jendrik the ui is a bit confusing. You have to switch the mode to Private . Ideally, that password field should be disabled or hidden when 'Public'. [image: 1777903757310-67cd6c39-a43e-4446-9f92-fe1d26f59591-image.jpeg]

@Teiluj yeah, I have noticed that too. We don't want to lock it too much either (app location, footer, usernames, group names, etc - lots of scope to put offensive things).