toor
veljača 2026 15:55 16
82
Pa 60 posto IP pola im je test. Žalosno.
1 lajk
amar
veljača 2026 19:31 16
83
jel vam forum ok radi? izgleda da je crashao docker container
3 lajka
toor
veljača 2026 13:01 17
85
Eggdropovi i Tcl scripte…. Eh mladosti moja.
1 lajk
amar
veljača 2026 20:36 17
86
jebeni forum je padao jer je nginx proxy imao rate limit 1 req per sec
root@ch1:~# grep -r “limit_req” /etc/nginx/
/etc/nginx/nginx.conf: limit_req_zone $binary_remote_addr zone=limit:10m rate=1r/s;
toor
veljača 2026 21:00 17
87
1r/s limit_req nije ‘uzrok crko maršal’ nego throttlinga. pravi pad se vidi po 5xx/OOM/DB lockovima. Ako je iza CF/CGNAT ili krivi real_ip, onda svi dijele isti bucket pa izgleda kao outage. Vidi si proxy na CF-u jel ti server vidi kao 1 ip, pa limit pogodi sve korisnike.
amar
veljača 2026 21:19 17
88
dolaze real_ip od cf-a, to je prvo što podesim
toor
veljača 2026 21:23 17
89
pa daj mu bursta, 1r/s je faktički ddos
amar
veljača 2026 21:31 17
90
root@ch1:~# grep -r “limit_req” /etc/nginx/
/etc/nginx/nginx.conf: limit_req_zone $binary_remote_addr zone=limit:10m rate=128r/s;
amar
veljača 2026 09:48 18
91
šta je ovo sa mydataknox, drugi dan za redom su offline
toor
veljača 2026 12:36 18
92
Ako moj noc ne laže onda je danas treći dan. A zanimljivo je i njihovo obrazloženje, ja samo mogu iščitati iz toga da serveri, switchevi, routeri nemaju redudantno napajanje.
amar
veljača 2026 14:46 19
94
novi projektić online https://bla.ba
1 lajk
Upravo sam se registrovao da vidim o cemu se radi
Skitamo se po Fejsu i komentiramo newse na carnetu…
amar
veljača 2026 18:11 27
98
Dižem mailcow server, kosa mi je opala jer neće letsencrypt da dodijeli cert na hostname.
amar
veljača 2026 19:27 27
100
a stavljam da smtp ide sa servera gdje je i forum, pa sam digao mailcow
a svaki put kad nešt mijenjaš od bitnih postavkih, moraš rebuildat cijeli discourse forum
nadam se da će ovo radit
opened 05:54PM - 10 Feb 22 UTC
zatvoreno 12:16AM - 14 Aug 22 UTC
bug
stale
**Prior to placing the issue, please check following:** *(fill out each checkbox… with an `X` once done)*
- [X] I understand that not following or deleting the below instructions will result in immediate closure and/or deletion of my issue.
- [X] I have understood that this bug report is dedicated for bugs, and not for support-related inquiries.
- [X] I have understood that answers are voluntary and community-driven, and not commercial support.
- [X] I have verified that my issue has not been already answered in the past. I also checked previous [issues](https://github.com/mailcow/mailcow-dockerized/issues).
## Summary
I have a fresh MailCow installation. I am trying to get my certificates signed by Let's Encrypt. Since I do not have IPv5, I disabled IPv6 according to [documentation](https://mailcow.github.io/mailcow-dockerized-docs/post_installation/firststeps-disable_ipv6/).
Then I run these commands:
```
cd /opt/mailcow-dockerized
touch data/assets/ssl/force_renew
docker-compose restart acme-mailcow
```
## Logs
When I run `docker-compose logs --tail=200 -f acme-mailcow` I get this error:
```
acme-mailcow_1 | OK
acme-mailcow_1 | Thu Feb 10 16:45:23 CET 2022 - Initializing, please wait...
acme-mailcow_1 | Thu Feb 10 16:45:23 CET 2022 - Using existing domain rsa key /var/lib/acme/acme/key.pem
acme-mailcow_1 | Thu Feb 10 16:45:23 CET 2022 - Using existing Lets Encrypt account key /var/lib/acme/acme/account.pem
acme-mailcow_1 | Thu Feb 10 16:45:23 CET 2022 - Detecting IP addresses...
acme-mailcow_1 | Thu Feb 10 16:45:32 CET 2022 - OK: 185.58.xxx.xxx, 0000:0000:0000:0000:0000:0000:0000:0000
acme-mailcow_1 | Thu Feb 10 16:45:33 CET 2022 - Found A record for autodiscover.mydomain.mk: 185.58.xxx.xxx
acme-mailcow_1 | Thu Feb 10 16:47:42 CET 2022 - Confirmed A record with IP 185.58.xxx.xxx, but HTTP validation failed
acme-mailcow_1 | Thu Feb 10 16:47:42 CET 2022 - Found A record for autoconfig.mydomain.mk: 185.58.xxx.xxx
acme-mailcow_1 | Thu Feb 10 16:49:53 CET 2022 - Confirmed A record with IP 185.58.xxx.xxx, but HTTP validation failed
acme-mailcow_1 | Thu Feb 10 16:49:53 CET 2022 - Found A record for mail.mydomain.mk: 185.58.180.221
acme-mailcow_1 | Thu Feb 10 16:52:04 CET 2022 - Confirmed A record with IP 185.58.xxx.xxx, but HTTP validation failed
acme-mailcow_1 | Thu Feb 10 16:52:04 CET 2022 - Cannot validate any hostnames, skipping Let's Encrypt for 1 hour.
acme-mailcow_1 | Thu Feb 10 16:52:04 CET 2022 - Use SKIP_LETS_ENCRYPT=y in mailcow.conf to skip it permanently.
acme-mailcow_1 | OK
```
## Reproduction
I tried that several times, always the same result. However, other parts of the system are working (receiving mails, sending mails,...).
## System information
| Question | Answer |
| --- | --- |
| My operating system | Debian 11.2 |
| Is Apparmor, SELinux or similar active? | Yes |
| Virtualization technlogy (KVM, VMware, Xen, etc - **LXC and OpenVZ are not supported** | KVM |
| Server/VM specifications (Memory, CPU Cores) | 10240 MB, 4 CPU cores |
| Docker Version (`docker version`) | 20.10.12 |
| Docker-Compose Version (`docker-compose version`) | 1.29.2 |
| Reverse proxy (custom solution) | don't know |
Regarding AppArmor, I get this:
```
apparmor module is loaded.
7 profiles are loaded.
7 profiles are in enforce mode.
/usr/bin/man
docker-default
lsb_release
man_filter
man_groff
nvidia_modprobe
nvidia_modprobe//kmod
0 profiles are in complain mode.
...
...
```
- DNS problems? Please run `docker exec -it $(docker ps -qf name=acme-mailcow) dig +short stackoverflow.com @172.22.1.254` (set the IP accordingly, if you changed the internal mailcow network) and post the output:
```
151.101.1.69
151.101.65.69
151.101.129.69
151.101.193.69
```