Skip to content

Conversation

@h4x3rotab
Copy link
Contributor

Summary

  • Fix ct_monitor to use HTTP /acme-info endpoint instead of pRPC
  • The gateway exposes /acme-info as HTTP, but ct_monitor was calling pRPC which caused 405 errors
  • Root cause: gateway pRPC uses trim: "Tproxy." so it expects Tproxy.* method names
  • Removes unused dstack-gateway-rpc and ra-rpc dependencies

Test plan

  • Build: cargo build --release -p ct_monitor
  • Test against production gateway: ./target/release/ct_monitor --gateway-uri https://gateway.dstack-pha-prod7.phala.network --domain dstack-pha-prod7.phala.network
  • Verified it successfully fetches public keys and checks certificate logs

🤖 Generated with Claude Code

The gateway exposes /acme-info as an HTTP endpoint, but ct_monitor was
using pRPC which expects Tproxy.* method names due to the gateway's
`trim: "Tproxy."` configuration. This caused 405 Method Not Allowed
errors.

Switch to using the HTTP /acme-info endpoint directly, which returns
JSON with hex-encoded public keys.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Remove dangerous `danger_accept_invalid_certs(true)` - gateway uses valid certs.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants