When I try to install the selfhosted murena cloud I get an error at the end where nextcloud is restarted stating that I should increase COMPOSE_HTTP_TIMEOUT value (currently 60). Can you let me know how I can do it? I tried to include it in base.sh, but it didn’t work.
Thanks
ε
Regain your privacy! Adopt /e/ the unGoogled mobile OS and online services
You may be facing a Docker problem: https://duckduckgo.com/?q=COMPOSE_HTTP_TIMEOUT&ia=web&iax=qa.
Please tell us more about the server (kind, sizing, OS, …).
I am still running a Hetzner CX11 Server with a modified ecloud.cnf (innodb_buffer_pool_size=128 M, innodb_buffer_pool_chunk_size = 128M, innodb_log_buffer_size = 32M, innodb_io_capacity=200) and it worked pretty well with past versions, but with the current version I am running into the compose_http_timeout error). Because of this I am currently running the nextcloud only version of murena cloud (see here: https://gitlab.e.foundation/e/infra/ecloud/nextcloud) with only nextcloud, mariadb and nginx containers installed and using nginxproxymanager for domain management and it works pretty well. It would be my favorite solution as I don’t need mailserver or postfixadmin, but cronjobs don’t work and AJAX doesn’t meet my needs. If I could get cronjob to work with the nextcloud only version, I would stick to that solution, otherwise I will have to sort out the compose_http_timeout issue.
This topic was automatically closed after 90 days. New replies are no longer allowed.