abd6ab06de
mongodb: fix restart
2023-03-14 11:59:25 +01:00
d2f0bb2b44
sftp: ed25519 keys
2023-03-09 11:03:13 +01:00
d1398659a3
Move sftp to new base image
2023-03-09 09:18:26 +01:00
5d425fbce5
Update graphite
2023-03-09 01:55:12 +01:00
2402bf45f4
hold off on mongodb update because it needs avx
2023-03-09 00:44:58 +01:00
b9a484f72e
Update mongodb
2023-03-08 23:44:21 +01:00
9cd3874b57
mysql: set secure_file_priv
2023-03-02 21:20:46 +01:00
bfeea414d8
Use sftp 3.6.2
2023-02-25 15:38:41 +01:00
582994b9d6
addons: stable IPv4 addresses
...
give addons static IPv4 so one can reliably connect from outside via
SSH tunnel
2023-02-21 12:20:44 +01:00
8c59528cc2
eventlog: keep 3 months
2023-02-21 10:38:15 +01:00
69d4404b05
mail: update haraka to 3.0.1
2023-01-23 09:48:02 +01:00
4aa67ba1f8
mysql: fix default collation during restore
2023-01-20 18:03:11 +01:00
15e4ceeb76
Use new postgres addon 5.0.1
2022-12-29 16:15:00 +01:00
4d5d6c6eb4
Update mail image
2022-12-28 14:46:52 +01:00
c26a3786fb
mail: update container base image
2022-12-06 13:50:41 +01:00
eedb239acf
postgresl: upgrade to 14
2022-12-06 11:52:09 +01:00
2bcd8e64aa
addons: update base images of addons
...
* mysql
* redis
* turn
2022-12-06 10:39:57 +01:00
38bf284806
Update base image to 4.0.0 (ubuntu jammy)
2022-12-05 12:27:04 +01:00
1c3ef36a47
typo in graphite version
2022-11-30 10:37:28 +01:00
cab7409d85
mail: update haraka
2022-11-24 18:27:33 +01:00
b437466f8c
mail: send quota value as raw bytes
2022-11-21 09:45:17 +01:00
250d54f157
postgresql: fix issue with pg_ctl timing out
2022-11-20 18:05:37 +01:00
00771d8197
reverseproxy: move dashboard config to subdir as well
2022-11-17 15:50:34 +01:00
293b8a0d34
remove location type from nginx filename
...
this will keep it consistent with upcoming cert filenames
2022-11-17 10:22:46 +01:00
af870d0eac
mail: fix dnsbl count
...
empty string was parsed as [''] leading the UI to think there is one zone
2022-11-14 22:06:33 +01:00
d49c171c79
mail: fix 100% cpu use with unreachable servers
2022-11-09 23:04:05 +01:00
deb6d78e4d
bump addon timeouts
2022-10-11 23:33:35 +02:00
3caffdb4e1
Rework app stats
...
Previously, the du plugin was collecting data every 20 seconds but
carbon was configured to only keep data every 12 hours causing much
confusion.
In the process of reworking this, it was determined:
* No need to collect disk usage info over time. Not sure how that is useful
* Instead, collect CPU/Network/Block info over time. We get this now from docker stats
* We also collect info about the services (addon containers)
* No need to reconfigure collectd for each app change anymore since there is no per
app collectd configuration anymore.
2022-10-10 21:13:26 +02:00
2133eab341
postgresql: fix issue when restoring large dumps
2022-10-10 12:30:26 +02:00
7dbb677af4
postgresql: move config to runtime for debuggability
2022-10-06 10:13:49 +02:00
acb92c8865
mail queue: fix search + pagination
2022-10-03 10:51:35 +02:00
1f74febdb0
mail: do not clear eventlog on restart
2022-09-28 22:16:32 +02:00
88e9f751ea
mail: update for logging changes
2022-09-26 09:37:36 +02:00
1f5831b79e
rename queue route
2022-09-22 19:48:20 +02:00
6382216dc5
mail: proxy queue routes correctly
2022-09-20 20:02:54 +02:00
82142f3f31
mail: fix issue where signature was appended to text attachments
2022-09-16 12:40:33 +02:00
bd7ee437a8
collectd: fix memory stat collection configuration
...
https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v1/memory.html#usage-in-bytes says
this is the most efficient approach for v1. It says RSS+CACHE(+SWAP) is the more accurate value.
Elsewhere in the note in https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v1/memory.html#stat-file ,
it says "‘rss + mapped_file” will give you resident set size of cgroup." Overall, it's not clear how
to compute the values so we just use the file.
https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html is better. https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html#memory
says the values are separated out.
2022-09-14 18:15:26 +02:00
2a93c703ef
mailserver: add queue routes
2022-08-31 08:45:18 +02:00
e21f39bc0b
Update mail container for quota support
2022-08-23 18:48:06 +02:00
d1bdb80c72
Update mail container for quota support
2022-08-22 19:03:47 +02:00
104bdaf76b
mail: cgroup v2 detection fix
...
there is crash in mail container when fts/solr is enabled
2022-06-26 14:28:22 -07:00
7ed8678d50
mongodb: fix import timeout
2022-05-09 17:20:16 -07:00
7cf80ebf69
postgresql: add connection logs
...
This was an attempt to fix connection leak in postgresql. It turns
out that there was a long running cron task which was holding a db
connection. When that happens, the apptask might fail because postgres
says db is in use. The code in scheduler.js currently does not really
'suspend' task running because of re-entrancy issues.
2022-04-28 16:11:09 -07:00
ac2186ccf6
redis: fix cgroup check
2022-04-27 18:46:00 -07:00
de9f3c10f4
Use new sftp addon 3.6.1
...
This will copy the uploaded file on conflict with a unique .number
extension
2022-04-07 18:02:11 +02:00
fc2a326332
mysql: Fix default collation
...
https://github.com/mattermost/mattermost-server/issues/19602#issuecomment-1057360142
> SELECT @@character_set_database, @@collation_database;
This will show utf8mb4 and utf8mb4_0900_ai_ci (was utf8mb4_unicode_ci)
To see the table schemas:
> SELECT table_schema, table_name, table_collation FROM information_schema.tables;
2022-03-02 22:34:30 -08:00
34c3a2b42d
mail: increase pool_timeout
2022-02-24 12:25:38 -08:00
24a16cf8b4
redis: fix issue where protected mode was enabled with no password
2022-02-21 12:21:37 -08:00
8f4779ad2f
Update addons to listen on ipv6
...
docker sets up the hostname DNS to be ipv4 and ipv6
Part of #264
2022-02-10 10:53:46 -08:00
ca83deb761
Docker IPv6 support
...
Docker's initial IPv6 support is based on allocating public IPv6 to containers.
This approach has many issues:
* The server may not get a block of IPv6 assigned to it
* It's complicated to allocate a block of IPv6 to cloudron server on home setups
* It's unclear how dynamic IPv6 is. If it's dynamic, then should containers be recreated?
* DNS setup is complicated
* Not a issue for Cloudron itself, but with -P, it just exposed the full container into the world
Given these issues, IPv6 NAT is being considered. Even though NAT is not a security mechanism as such,
it does offer benefits that we care about:
* We can allocate some private IPv6 to containers
* Have docker NAT66 the exposed ports
* Works similar to IPv4
Currently, the IPv6 ports are always mapped and exposed. The "Enable IPv6" config option is only whether
to automate AAAA records or not. This way, user can enable it and 'sync' dns and we don't need to
re-create containers etc. There is no inherent benefit is not exposing IPv6 at all everywhere unless we find
it unstable.
Fixes #264
2022-02-09 23:54:53 -08:00
Girish Ramakrishnan