Any news?
Also without significant load, it isnt fine
10:00 healthmonitor App is down
23:31 healthmonitor App is back online
23:28 healthmonitor App is down
23:08 healthmonitor App is back online
21:48 healthmonitor App is down
20:06 healthmonitor App is back online
20:05 healthmonitor App is down
no errors in the test instance - healthcheck every 10 sec
you mention a 2nd instance without data?
can you increase the timeout?
Mar 13 14:12:15 [2025-03-13 13:12:15.157][response][INFO] (websockets_hub) GET /notifications/hub?<data..> => 200 OK
Mar 13 14:12:17 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 13 14:12:27 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 13 14:12:37 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 13 14:12:47 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 13 14:12:57 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 13 14:13:07 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 13 14:13:14 [2025-03-13 13:13:14.017][vaultwarden::api::notifications][INFO] Closing WS connection from
and vaultwarden.log:
[2025-03-13 13:12:15.157][response][INFO] (websockets_hub) GET /notifications/hub?<data..> => 200 OK
[2025-03-13 13:13:14.017][vaultwarden::api::notifications][INFO] Closing WS connection from
there is a gap ..
I can not see any abnormal:
Mar 13 12:12:05 => Starting supervisord
Mar 13 12:12:05 box:tasks update 14557: {"percent":100,"message":"Done"}
Mar 13 12:12:05 box:taskworker Task took 7.035 seconds
Mar 13 12:12:05 box:tasks setCompleted - 14557: {"result":null,"error":null}
Mar 13 12:12:05 box:tasks update 14557: {"percent":100,"result":null,"error":null}
Mar 13 12:12:05 2025-03-13 11:12:05,952 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
Mar 13 12:12:05 2025-03-13 11:12:05,952 INFO Included extra file "/etc/supervisor/conf.d/apache2.conf" during parsing
Mar 13 12:12:05 2025-03-13 11:12:05,953 INFO Included extra file "/etc/supervisor/conf.d/bitwarden_rs.conf" during parsing
Mar 13 12:12:05 2025-03-13 11:12:05,959 INFO RPC interface 'supervisor' initialized
Mar 13 12:12:05 2025-03-13 11:12:05,960 CRIT Server 'unix_http_server' running without any HTTP authentication checking
Mar 13 12:12:05 2025-03-13 11:12:05,960 INFO supervisord started with pid 1
Mar 13 12:12:06 2025-03-13 11:12:06,965 INFO spawned: 'apache2' with pid 27
Mar 13 12:12:06 2025-03-13 11:12:06,969 INFO spawned: 'core' with pid 28
Mar 13 12:12:06 /--------------------------------------------------------------------
Mar 13 12:12:06 | Starting Vaultwarden |
Mar 13 12:12:06 |--------------------------------------------------------------------|
Mar 13 12:12:06 | This is an unofficial Bitwarden implementation, DO NOT use the |
Mar 13 12:12:06 | official channels to report bugs/features, regardless of client. |
Mar 13 12:12:06 | Send usage/configuration questions or feature requests to: |
Mar 13 12:12:06 | https://github.com/dani-garcia/vaultwarden/discussions or |
Mar 13 12:12:06 | https://vaultwarden.discourse.group/ |
Mar 13 12:12:06 | Report suspected bugs/issues in the software itself at: |
Mar 13 12:12:06 | https://github.com/dani-garcia/vaultwarden/issues/new |
Mar 13 12:12:06 --------------------------------------------------------------------/
Mar 13 12:12:06 2025-03-13T11:12:06Z
Mar 13 12:12:06 [INFO] Using saved config from /app/data/config.json for configuration.
Mar 13 12:12:06 2025-03-13T11:12:06Z
Mar 13 12:12:06 [NOTICE] You are using a plain text ADMIN_TOKEN which is insecure.
Mar 13 12:12:06 Please generate a secure Argon2 PHC string by using vaultwarden hash or argon2.
Mar 13 12:12:06 See: https://github.com/dani-garcia/vaultwarden/wiki/Enabling-admin-page#secure-the-admin_token
Mar 13 12:12:06 2025-03-13T11:12:06Z
Mar 13 12:12:07 [2025-03-13 11:12:07.204][start][INFO] Rocket has launched from http://127.0.0.1:3000
Mar 13 12:12:07 [Thu Mar 13 11:12:07.270937 2025] [mpm_prefork:notice] [pid 43] AH00163: Apache/2.4.52 (Ubuntu) mod_perl/2.0.12 Perl/v5.34.0 configured -- resuming normal operations
Mar 13 12:12:07 [Thu Mar 13 11:12:07.271015 2025] [core:notice] [pid 43] AH00094: Command line: '/usr/sbin/apache2 -D FOREGROUND'
Mar 13 12:12:08 2025-03-13 11:12:08,272 INFO success: apache2 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Mar 13 12:12:08 2025-03-13 11:12:08,273 INFO success: core entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Mar 13 12:12:08 [2025-03-13 11:12:08.613][request][INFO] GET /notifications/hub?access_token=eyJ0eXAiOiJKV1QiL
Mar 13 12:12:08 [2025-03-13 11:12:08.613][vaultwarden::api::notifications][INFO] Accepting Rocket WS connection from 217.5.161.14
Mar 13 12:12:08 [2025-03-13 11:12:08.614][response][INFO] (websockets_hub) GET /notifications/hub?<data..> => 200 OK
Hi,
since a couple of days we have problems with vaultwarden. Logs show:
Mar 13 10:13:17 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 13 10:13:27 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 13 10:13:37 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 13 10:13:47 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 13 10:13:57 => Healtheck error: Error: Timeout of 7000ms exceeded
and Clients can not update or login.
I set the memory limit to 5 Gb with no success. Performance graphs are all at low state.
Someone with a glue or advise?
Regards
Dirk
Hi @girish,
thank you for the quick answer and explanation. We can deal with it. Have a nice weekend.
Hi cloudronians,
we use our active directory (external ldap) for usermanagement. Now we have to change some accounts (SAMAccountName and email). As a result, new users will creted in cloudron.
How can I manage it to change smoothly the exiting users to their new names.
I guess the feature "user can change name and email" would help, but if I set this option, I can not found the matching settings in the user profile. It is still not editable.
have a greet day,
dirk
Hi,
in logs I can find nothing, federation is off.
I had a look at the website and add to homeserver.yaml:
caches:
global_factor: 2.0
per_cache_factors:
get_users_who_share_room_with_user: 2.0
sync_response_cache_duration: 4m
cache_autotuning:
max_cache_memory_usage: 4096M
target_cache_memory_usage: 1516M
min_cache_ttl: 30m
Then I deleted approx. 400 unused rooms, but nothing helps.
I guess it is related to presence. There are 186 users, not too much.
Maybe we move Matrix/Element to separate hardware.
greetings
dirk
Good day and a happy new year,
we are facing a issue with cloudron performance and find out the reason with Matrix/Synapse.
Without interruption it shows:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
149 cloudron 20 0 3276808 312768 19816 S 96.7 1.9 6123:36 python3
restart, more memory - nothing helps.
Anybody out there with a hint,what we can ceck and fix?
kind regards
dirk
Thank you
Hallo,
we sync our ldap with the cloudron user directory. This works fine, also with groups. Now we discovered a problem. If a LDAP user is deaktivated or deleted, this user is active in the cloudron user directory. Maybe not an issue because the password, but if an active user is removed from a LDAP group, this user stays forever in the matching cloudron group.
Is there an option to prevent this?
kind regards dirk
Hi @girish,
if I create a new local user I do not get the invitation mail. If I make a user local and impersonate it, then I can still not login. Same error.
best
dirk
@subven
Hi,
we sync our AD to cloudron and decide with groups, which users can use the apps. The users with the corresponding groups are synced correctly and a login with nextcloud is working well. But they cannot login to Matrix/Element.
Hi there,
I enable a group of new users via LDAP for Matrix. This users cant login:
invalid username or password. I enabled the users directly in dashboard, but they still cant login.
Restart of container, but issue still exists.
Maybe something with the last update?
Please check, any ideas are welcome.
Greetings Dirk
@girish Thank you - now its working again.
Good afternoon,
I noticed no name resolution in all apps. I could not resolv our OnlyOffice instance.
It's not working since the last update.
Any help is wellcome.
Kind Regards dirk
Hi,
I maybe found the reason. We put all users in specific groups. Only users in this group can share by username with other users in this particular group. Now I created a group Kontakt and put all users in it. All users can now share files with others. I hope this opens no security hole and maybe there is a switch for this feature, but it works.
Feedback would be nice.
greetings dirk
