monitoring: probe XMPP c2s with a plain connect
Some checks failed
deploy / ansible (push) Has been cancelled
Some checks failed
deploy / ansible (push) Has been cancelled
blackbox_exporter matches query_response line by line, and ejabberd writes its stream features and <proceed/> without newlines, so the STARTTLS dialogue always timed out and the probe alert fired while XMPP was fine. Port 5222 gets a TCP connect; the certificate is still checked through direct TLS on 5223. Assisted-by: Claude:opus-5-5
This commit is contained in:
parent
94bc2d7ee9
commit
3197f5fc16
2 changed files with 3 additions and 12 deletions
|
|
@ -16,7 +16,9 @@ monitoring_probes:
|
|||
- { name: forgejo, target: "https://git.asxp.io/", module: http_2xx }
|
||||
- { name: s3, target: "https://s3.asxp.io/", module: http_up }
|
||||
- { name: sillytavern, target: "http://{{ asxpio_services_wireguard_ip }}:8000/", module: http_up }
|
||||
- { name: xmpp c2s starttls, target: "xmpp.asxp.io:5222", module: xmpp_starttls }
|
||||
# blackbox matches responses line by line and ejabberd sends no newlines,
|
||||
# so a STARTTLS dialogue times out: plain connect here, TLS on 5223.
|
||||
- { name: xmpp c2s, target: "xmpp.asxp.io:5222", module: tcp_connect }
|
||||
- { name: xmpp c2s tls, target: "xmpp.asxp.io:5223", module: tls_connect }
|
||||
- { name: xmpp s2s, target: "xmpp.asxp.io:5269", module: tcp_connect }
|
||||
- { name: turn, target: "xmpp.asxp.io:3478", module: tcp_connect }
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue