P
Thanks. I'm fine with an occasional troubles that I will leave alone (after all it was working fine for a few years without any problems), but I was absolutely sure that all 'core' services are monitored thought.
Is there any chance to expect that anytime soon?
I can't think of a work-around solution for a turn-server external check...
Is there any way to have turn healtcheck implemented?
I realized my turn server has been hanging somehow weird with the following messages in the logs:
=> Generating turnserver.conf
=> Ensure permissions
=> Starting coturn
bind: Cannot assign requested address
Cannot bind local socket to addr: Invalid argument
bind: Cannot assign requested address
Cannot bind local socket to addr: Cannot assign requested address
bind: Cannot assign requested address
Cannot bind local socket to addr: Cannot assign requested address
+ I wasn't able to extract them from the web console - it returned zero (empty) log - that is the output that I've received via docker log command.
@ccfu I can not agree on deactivate - the purpose is very useful. I would rather have it working properly!
@nebulon I wish... 
Guess I will end up removing it from the database, if it will be disturbing me too much
Regardless - thank you for the tool!!
Star based monitoring works!
I'm not using github stars, so I'm fine leaving with them - just one more question then: how do I remove a manually added entry?
@nebulon it's not that I'm using github automations, so rate limit is unlikely...
I understand the necessity for the logs though - that's why I asked how I can enable debug mode - to get them
Is there some way to enable debug mode to fetch the logs?
@nebulon looks like not...
@joseph apologies, I wish I had time for that 
I can enable debug mode, but I can't see no configuration file - happy to follow some reasonable instructions to enable it (I can see debug on the code)
I've added https://github.com/element-hq/synapse manually for the monitoring at 1.120.2 and it picked up no new releases ever since (and the latest is v1.128!)
According to the logs, everything is synced Ok
Apr 26 22:35:48 releasebell/tasks run: start +1h
Apr 26 22:35:48 releasebell/tasks syncGithubStarredByUser: admin +4ms
Apr 26 22:35:49 releasebell/tasks syncGithubStarredByUser: found 1 starred repos +244ms
Apr 26 22:35:49 releasebell/tasks syncGithubStarredByUser: new projects: 0 outdated projects: 0 +4ms
Apr 26 22:35:49 releasebell/tasks syncReleasesByProject: [element-hq/synapse] type github_manual start sync releases, notifications are enabled. Last successful sync was at 2025-04-26T19:35:48.572Z +15ms
Apr 26 22:35:51 releasebell/tasks run: done. Next run in 3600s at Sat Apr 26 2025 21:35:51 GMT+0000 (Coordinated Universal Time) +6ms
Apr 26 22:35:51 releasebell/tasks syncReleasesByProject: [element-hq/synapse] found 0 new releases +2s
Apr 26 22:35:51 releasebell/tasks syncReleasesByProject: [element-hq/synapse] successfully synced +0ms
Could you please, help with that?
Could you please convert that thread into a request to remove 'Cloudron' from the mail templates as well as from translation files, please?
@girish my bad, you covered it all, it's just me who just got what you meant - apologies and thanks for keeping explaining.
@girish Ok. And could you please, answer on my initial question, regarding the actual lines that are replaced inside the template?
Like I've told, I'm not referring to 'Powered by Cloudron' - I'm referring to the lines you have in Weblate.
@girish , I'm not referring to 'Powered by Cloudron' line - I was referring to 'Cloudron' direct mention in the title of the mail, for example - and I can't see it's being anywhere in the template - that's why I asked for localization.
you can just remove the line from /home/yellowtent/box/src/mail_templates/*.ejs files
Guess they will be overwritten on every update, wouldn't they?
@girish understand on not a priority - makes perfect sense.
Where do I remove that from? Where are localized strings stored in deployed Cloudron instance?
Negative. Please, disregard what have been said earlier: OpenID from Cloudron could be used as is.
Happy to share my findings on setting up the service with @vladimir.d or whoever will be doing this configuration for everyone on Cloudron.
From Cloudron manifest file I can see that you use callback as a static rule:
"loginRedirectUri": "/_synapse/client/oidc/callback"
Which is pretty much in line with what I wrote earlier -> Cloudron OpenID component needs improvements in order for Synapse's MAS to work.
@joseph I believe it's a question of support still - as I'm trying to figure out to configure Cloudron's OpenID to work with external app, which Cloudron is about to repackage on it's own.
The link you've provided - is related to configuring Synapse server, while the issue is with Cloudron's OpenID and the way it handles redirect_uri.
Please, let me know if I shall not expect any reasonable and prompt support on that - if that is the case, I will have to replace the Cloudron functionality as a platform, and for that I will need quite some time.
I would be happy to work with someone from the team however, to keep Cloudron in my perimeter and share everything I will work on, so that you would be able to merge Synapse MAS and Element Call into the platform easily.
That looks to be an error produced by oidc-provider module in use of Cloudron (InvalidRedirectUri exception), looks like it is raised by /home/yellowtent/box/src/oidc.js.
oidc-provider module provides information how to use wildcard redirect_uri, warming that is shall not be used in production: https://github.com/panva/node-oidc-provider/blob/main/recipes/redirect_uri_wildcards.md
It looks to me like oidc.js logic has to be altered in a way to let wildcard at the end of the redirect_uri, as otherwise Synapse's MAS won't work.
Unless I'm missing something.
Element's MAS requirements are as follow:
create an OAuth 2.0/OIDC client on the provider's side, using the following parameters:
- redirect_uri: https://<auth-service-domain>/upstream/callback/<id>
- response_type: code
- response_mode: query
- grant_type: authorization_code
I believe I assembled a first version, but got stuck with OpenID auth on Cloudron side: https://forum.cloudron.io/topic/13648/openid-uri-configuration-issue-for-synapse-s-mas
I would appreciate any help here - it would be beneficial for the work to be done by @vladimir.d or whoever would be solving the same task.