The HighLevel Connect flow has been broken on my account all evening. GHL completes the OAuth grant fine, but the callback to https://hermes.composio.dev/api/v1/auth-apps/add returns Cloudflare 1016 / HTTP 530 every time, so the auth code never reaches your backend. Every attempt dies as INITIATED → EXPIRED with no ACTIVE connection. Quick curl test from my machine (2026-05-07 00:05 UTC): curl -I https://hermes.composio.dev → HTTP/2 530 curl -I https://backend.composio.dev → HTTP/2 200 Only hermes is unreachable — DNS resolves, Cloudflare just can't reach the origin behind it. Account info: Email: evans@cnufit.com Org: evans_workspace Project: ok_YkhXyjqOi6IN Toolkit: highlevel Sample failed callback URL the browser landed on: https://hermes.composio.dev/api/v1/auth-apps/add?code=cd653134838d342e9953b3ec592d180213073ba6 → Cloudflare 1016 page, code never delivered. GHL's marketplace shows the app as "Installed in 1 Sub-Account" so GHL's half completed; only Composio's receiving endpoint failed. All my other connectors (Gmail, Calendar, Sheets, Drive, YouTube, Discord, Meta Ads, Asana, GA) are ACTIVE — this is HighLevel-only. Three things I'd love help with: Is hermes.composio.dev a known incident? Any ETA? Once it's back, do I need to manually clear the INITIATED/EXPIRED rows or will a fresh Connect overwrite? Is there a way to manually feed the existing GHL install token in (since GHL already approved on their side), to skip another full OAuth round trip? Thanks

Hi @evans-cnufit , thanks for the detailed info, the error codes are really helpful! The DNS error you're currently seeing (Cloudflare 1016) happens when you try to install your own OAuth app with our redirect URI configured directly in the account/workspace, instead of going through the Composio connection flow. Could you try initiating a connection via the Dashboard and let me know if it works? Also, just to confirm, could you share a complete screen recording of the flow? It'll really help us narrow this down.

this what I got. I removed everything from GHL and started over https://www.loom.com/share/d1e4094ce7fb4d42a92a0090d5c440f7

Hey @evans-cnufit ,thanks for sharing the recording! Just wanted to flag — I went through the Loom carefully and didn't actually see the Cloudflare 1016 / DNS error come up at any point in the flow. It looks like Hermes is reachable on your end now, but the issue you're hitting in the video seems to be a different one from what was originally reported. Could you lmk if it's fixed? Also, one quick question that'll help us narrow this down: is your HighLevel auth app set up as private or public (listed in the GHL Marketplace)? The behavior can differ between the two and also depends on if you are on free trial, so knowing these will help us pinpoint what's going on.

https://www.loom.com/share/17bfd14691e64c699bbfe7733e7793cf I tried again but tis is error I received https://cdn.discordapp.com/attachments/1501741476046966885/1503155177384054816/Screenshot_2026-05-10_at_6.00.12_PM_2.png?ex=6a0251d9&is=6a010059&hm=dccad4886063b9c2d15184aa81555b6e85376adb070f567a57e27fb61f7da59c& https://cdn.discordapp.com/attachments/1501741476046966885/1503155178050687066/Screenshot_2026-05-10_at_6.01.07_PM.png?ex=6a0251d9&is=6a010059&hm=2f14823f3978827e6a9727f9391c83fa8e075ef93273f6ff97e5a69a07366717&

Hi @evans-cnufit, thanks for confirming the app type. We were unable to reproduce the issue with our current credentials. That said, we've applied for new credentials which should help us reproduce the same DNS issue. I'll keep you updated on this! Thanks for understanding : )

Thank you