Issues with systemd-resolved

[mmaridev]

Hi,
I just setup an instance with the same domain name for all services. Although having done the same setup in the past, today I was getting

openuem-console              | 2026/07/29 09:57:09 [ERROR]: could not connect to NATS nats: no servers available for connection

and

openuem-nats-server          | [1] 2026/07/29 10:02:35.240092 [WRN] Attempt to obtain OCSP response from CA responder for [OMISSIS] failed: exhausted OCSP responders: Get "http://OMISSIS.local:8000/OMISSIS": dial tcp 127.0.1.1:8000: connect: connection refused
openuem-nats-server          | [1] 2026/07/29 10:02:35.240673 [ERR] OMISSIS:53478 - cid:5 - TLS handshake error: client not OCSP valid

After a quite long investigation, I figured the issue was that the system, bootstrapped using the official Debian 13 Cloud image, defaulted to systemd-resolved as resolver which, apparently, throws 127.0.1.1 for what he thinks it's localhost even if the query comes from inside docker. A simple apt remove systemd-resolved and down & up of the containers solved the issue.

I would suggest adding an hint in the public docs.

[doncicuto]

Thank you for your suggested workaround I'll have a look and add a note in docs and readme files