My Ajax Systems plugin no longer updates alarm state from live callbacks. Manual sync works, but arm/disarm/night mode changes never arrive automatically.
To verify this, I temporarily added safe instrumentation to jeeAjaxSystem.php so it logs incoming callback attempts without exposing secrets. A direct synthetic callback POST to the public endpoint is logged and processed correctly, but real Ajax arm/disarm changes produce no incoming POST at all.
The public callback URL returns Setup OK. I also moved the hostname behind a Cloudflare Tunnel to remove my firewall/HAProxy from the path, but real callbacks still never arrive.
Before Cloudflare, WAN tcpdump showed Ajax/Jeedom cloud connecting from 162.19.116.94 to my public IP on 443; my firewall replied SYN-ACK, then the remote side immediately sent RST. No TLS ClientHello, no SNI, no HTTP request.
I deleted/reinstalled the plugin, logged in successfully, and synced once. New command IDs and a new Ajax plugin API key were created; the new key works and Setup OK is returned. Still, real Night/Disarm/Night changes produce no callback POST.
This sounds similar to the previous Ajax “update queue” issue. Could my Ajax Systems update queue/callback registration be stuck on the Jeedom cloud side, and can it be cleared/reset?
The callback is not working at all. The connection shows SYN, SYN-ACK, then RESET. This appears to be a server-side issue, not a user-side configuration problem.
A full bidirectional tcpdump shows the Jeedom/Ajax cloud host 162.19.116.94 sends SYN, my firewall replies SYN-ACK immediately, then 162.19.116.94 sends RST without completing the TCP handshake. There is no ACK, no TLS ClientHello, no SNI and no HTTP request. Public TLS checks from other clients succeed and the certificate chain verifies correctly.
Quelqu’un peut-il apporter de l’aide ou du support pour ce plugin ?
Le callback ne fonctionne pas du tout. La connexion montre SYN, SYN-ACK, puis RESET. Cela semble clairement être un problème côté serveur, et non un problème de configuration côté utilisateur.
L’un des développeurs du plugin pourrait-il nous aider, s’il vous plaît ?
It’s an Ajax issue same we go since few month, I can(t find a solution because we received event from ajax too late (few hour after real event)
Your syn ack I don’t known for that on jeedom cloud it’s a simple http post resquest, only think mandatory it’s a valide certificat with 3 level (your domain, intermediate and root).
thank you for replying! - we don’t reach http, we haven’t finished tcp establishment. syn, syn-ack, next step is fin in the 3 way handshake… I get reset. this is well before, tls, then http. TCP must establish first. TCP (failure is here), TLS (Certs), HTTP
Thank you. Respectfully, can we look at this specific case? I am happy to donate to your coffee fund
The reset is happening before TLS and before HTTP. It is coming from the OVH socket side. I wonder if my account or callback registration is stuck and could be reset. My Ajax account email is tui@kapo.nz.
If useful, I can provide the exact callback URL and current Ajax plugin API key privately so you can test the endpoint directly from the same Jeedom cloud worker that is attempting the callbacks. The public callback host is jeedom.kapo.nz, and normal external clients can complete TLS and reach the endpoint successfully. The callback path is: https://jeedom.kapo.nz/plugins/ajaxSystem/core/php/jeeAjaxSystem.php - I can give you an API key privately… it works fine.
