Topics created by imc67

@imc67 said in default plugins not available:

Thanks for fixing this.

Yeah! I wasn't missing this as I wasn't aware it existed, but having both random and hyphenated short links now available is awesome, thanks!

@jayonrails
In Apple Mail on iOS :

B8DC815D-3B7D-41E0-9A33-A4C7B5843C07.jpeg

Perfect! I ran some tests today with tweaking various numbers and looked at recommendations online too. It's mostly a copy of yours @imc67 in the end but with a lower MaxConnectionsPerChild. Ran a bunch of different tests with different numbers but concluded that was the best bang for the buck so-to-speak given the 4 GB memory max set on each WP app.

It's a mix of default values from the Ubuntu install and the default Apache values in the original package too (for the 256 MaxRequestWorkers for example). I'm pleased with the results. 🙂

Here's what I have for reference now, and I used ab (Apache Benchmark) to run some performance tests and had significant improvements over the defaults. Thought I'd share the testing results in case anyone was interested.

New mpm_prefork.conf I'm using:

# Restart the app if you make changes to this file <IfModule mpm_prefork_module> # On startup, start these many servers StartServers 5 # At any given time, keep atleast these many servers MinSpareServers 5 # At any given time, keep atmost these many idle servers (this is always >= MinSpareServers+1) MaxSpareServers 10 # Maximum number of servers at any given instant. Requests will be queued after this MaxRequestWorkers 256 # Recycle process after handling these many requests. This protected against accidental memory leaks MaxConnectionsPerChild 500 </IfModule>

Resources:

https://httpd.apache.org/docs/2.4/mod/prefork.html https://exampleconfig.com/view/apache-ubuntu20-04-etc-apache2-mods-available-mpm_prefork-conf https://www.woktron.com/secure/knowledgebase/133/How-to-optimize-Apache-performance.html https://www.maketecheasier.com/optimizing-apache-part-1/

Results from ab with default settings that come with Cloudron's WP package: (note the rather large spread between min and max request times)

Concurrency Level: 50 Time taken for tests: 12.391 seconds Complete requests: 1000 Failed requests: 0 Total transferred: 84813000 bytes HTML transferred: 84205000 bytes Requests per second: 80.70 [#/sec] (mean) Time per request: 619.574 [ms] (mean) Time per request: 12.391 [ms] (mean, across all concurrent requests) Transfer rate: 6684.04 [Kbytes/sec] received Connection Times (ms) min mean[+/-sd] median max Connect: 227 291 36.4 287 401 Processing: 220 281 122.2 252 1039 Waiting: 144 190 120.0 161 954 Total: 451 572 127.3 546 1285 Percentage of the requests served within a certain time (ms) 50% 546 66% 570 75% 584 80% 594 90% 624 95% 818 98% 1091 99% 1261 100% 1285 (longest request)

Results after tweaking to the above new configuration: (note that the max request time here is about 60% faster still than original config results and overall a much more consistent behaviour too!)

Concurrency Level: 50 Time taken for tests: 11.358 seconds Complete requests: 1000 Failed requests: 0 Total transferred: 84813000 bytes HTML transferred: 84205000 bytes Requests per second: 88.04 [#/sec] (mean) Time per request: 567.899 [ms] (mean) Time per request: 11.358 [ms] (mean, across all concurrent requests) Transfer rate: 7292.24 [Kbytes/sec] received Connection Times (ms) min mean[+/-sd] median max Connect: 230 287 26.9 283 389 Processing: 220 252 17.3 249 329 Waiting: 144 160 10.0 157 217 Total: 467 539 33.0 538 649 Percentage of the requests served within a certain time (ms) 50% 538 66% 550 75% 559 80% 567 90% 584 95% 599 98% 618 99% 622 100% 649 (longest request)

Excellent. Thank you @vladimir-d @girish.

@girish 👍🏻

Without being able to debug this further, for a start, the filter seems wrong. The Cloudron provided user records would have the following objectClass attribute:

objectclass: [ 'user', 'inetorgperson', 'person' ]

so use one of those three entries there. Also Cloudron has no attribute uidNumber maybe using entryuuid works there though.

@nebulon it's up again

@imc67 one way to solve it (temporary?) is to clear cache and cookies

@imc67 published update

@imc67 Should be fixed now.

But if you had issue with the logo not changing, that is something caching related and not related to this warning (Afaict). I didn't dig much but it's related to https://github.com/owncast/owncast/issues/1776 or https://github.com/owncast/owncast/issues/1773 . After you upload a logo, go to /app/data/data and it still has the logo.svg . Deleting it + hard refresh in browser makes it immediately load the new logo.

@imc67 essentially the patch for this is https://git.cloudron.io/cloudron/box/-/commit/eb0662b2455e0687ab3ce5dd02d2466e16670092 so two files need to be adjusted. The .ejs file is a template which will result in /etc/nginx/applications/my.<domain.com>.conf so besides the editing the .ejs file additionally edit that file and then systemctl restart nginx and systemctl restart box.

@imc67 are you referring to the chatwoot nokogiri security issue bullet point? The upstream project has provided no information on how severe it is. I couldn't find nokogiri in the diffs either, would appreciate any info on this. They have no info on their blog either.

As for AdGuard, it has already been updated to support ipv6 (which is not backward compatible tested with 7.0). Also, the security issues from what I see are Go related things which are kinda unlikely because AdGuard is not exposed to the world.

In contrast, for clear security posts like https://about.gitlab.com/releases/2022/02/25/critical-security-release-gitlab-14-8-2-released/ , we make it available asap for 7.0.

The main reason is that their rewrite of the LDAP connector does not work anymore and is pending fixes. I had some attempts to contribute a fix, but I so far lack the in-depth knowledge of the PHP frameworks used. It is still on my list to hopefully be able to contribute a fix. You can track the upstream issue at https://github.com/firefly-iii/firefly-iii/issues/5133

@jodumont said in Harden security features:

provide and identifiy authentification via SAML (if it is possible)

SAML is an old and outdated protocol (that is also hard to work with), a more modern alternative is oidc (OpenID Connect, a standard based on Oauth 2.0), which is also offered in your screenshot.

@imc67 I have not found anything about LDAP in the documentation. https://www.chatwoot.com/docs/self-hosted
There is a GitHub issue about "Oauth integration". https://github.com/chatwoot/chatwoot/issues/1318 Let's see.

@imc67 Awesome and happy to hear that.

PS: I know that feeling - a fellow FF user.

@imc67 currently only via SSH, so umount the device and then run systemctl restart <mountpointunit.mount>

@nebulon thanks!

@imc67 yes sorry, I completely forgot about that regression in Cloudron 6.3.5.

@nebulon 👍🏼

@nebulon thanks!!!!!

@nebulon I can reproduce it on 2 of the 3 FreeScout instances, all three have at least LDAP:

The one with only LDAP shows indeed the translations for LDAP FreeScout number 2 has: Block External Images, Custom Folders, Followers, LDAP Integration, Spam Filter, Tags FreeScout number 3 has: Block External Images, Followers, LDAP Integration, Spam Filter, Tags, Two-Factor Authentication

I have a gut feeling it has to do with Block External Images, since I bought and installed it on 2 of the 3, those 2 have the issue.

Ok there was a related new upstream release and I have update the Cloudron package now.

I read that file quickly, indeed it seems it can pull in email addresses from LDAP.

I agree this looks quite useful to have! I will open a bug to investigate - https://git.cloudron.io/cloudron/roundcube-app/-/issues/3 . I think this might need change to our LDAP directory first to make the username <-> concrete mailbox work well, have to investigate.

The logs do indicate a database issue and restarting that might have fixed it as well. I guess you restarted mysql as you mentioned, while both apps use postgresql.
Actually the line of:

FATAL: remaining connection slots are reserved for non-replication superuser connections

gives a good indication here. I have seen that recently, that if apps hog onto the postgres connections, it eventually may exhaust the connection pool, then this message is shown. A postgresql service restart resolves this, as it frees up those connection slots.

@imc67 nevermind, I found it - https://docs.espocrm.com/user-guide/mass-email/#settings

I will move this to feature request. But we haven't really analyzed what work this involves.

@girish I requested the developers to review the query. Meanwhile I changed the setting in mysql and indeed the plugin doe work now as expected!

The root cause is that the nextcloud package is configured to log to the console (stdout / stderr) instead of a file. Nextcloud tries to open the stdout/stderr and this fails. Ideally, nextcloud can show a graceful error message that logs cannot be viewed from inside the app because it is logging to the console. Workaround is to use the cloudron logs viewer to view the logs - which IMO is the correct place to view logs (for all apps and not just nextcloud). After all, if the app is not working, one cannot view the logs within itself.

@imc67 there were a couple of upstream releases shortly after each other, and we don't skip package updates, so you had to go through them one-by-one.