Cloudron Forum

Ok, I will close this one then. We really have to get down to that other issue again.

@LoudLemur it’s actually something that’s interesting for EVERY European business above 50 employees as they have to establish secure reporting channels for misconduct for their employees, freelancers, suppliers, etc. under the Whistleblower Directive

https://commission.europa.eu/aid-development-cooperation-fundamental-rights/your-rights-eu/protection-whistleblowers_en

Super helpful! Thank you!

@squareclouds I can asure you that your deliverability rate will not improve if you send through a selfhosted SMTP relay. Also sending from your Cloudrons SMTP won't be better (in most cases) other then your providers mail server. Ugly truth is that email besides the "big brands" is kinda broken. I pay 11$ ransom to mailjet every month to get my ~2500 mails/month out 😞

@manngobaum
There is:

POST /api/v1/cloudron/reboot

auth as usual

=D @girish in sync

@girish Yes, this was it. I did not manage to see the actual json. But seems like n8n always adds quotes using the name / value combination. I changed it to this:

{ "nodes": [ { "parameters": { "requestMethod": "POST", "url": "=https://my.xxx.de/api/v1/notifications/{{$node[\"Item Lists\"].json[\"id\"]}}", "jsonParameters": true, "options": {}, "bodyParametersJson": "={\n\"acknowledged\": true\n}", "headerParametersJson": "={\"authorization\": \"Bearer xxx\"}" }, "name": "HTTP Request1", "type": "n8n-nodes-base.httpRequest", "typeVersion": 2, "position": [ 1100, 300 ] } ], "connections": {} }

Now it's working. I used this:
Bildschirmfoto 2022-06-14 um 18.16.17.png
instead of this:Bildschirmfoto 2022-06-14 um 18.16.42.png

Did you explore this any further?

The solution is to add the filename to the path:

In my case:

/consume/file.pdf

@manngobaum Expectation was: link not displayed 🙂 Top. Thank you.

@nebulon thank you

@manngobaum yes, this was a display bug. It's fixed in the upcoming release. Thanks for reporting.

@manngobaum I prefer this client over element as well.

@nebulon no problem at all. The topic itself is quite large so individual bits are easy to miss.

A script could be a nice idea as most users will probably not be comfortable with doing sql updates manually. But such a script can probably turn into something complicated quite easily. The flow that immediately comes to mind would be doing in ldap server on the ldap backend and comparing it with the users that Cloudron already knows. Followed by the possibility to switch auth for any users that are primarily managed on Cloudron, but exist on the ldap side as well. Probably easier to do it in javascript than it would be in e.g. bash.