I have a DNS A Record for
trace.filevacuum.com to go to my server’s IP.
This works for a Go Server running at:
http://trace.filevacuum.com:16686 (you won’t see this page as it’s just for my IP)
opentelemetry-rust tried to POST to
http://trace.filevacuum.com:14268/api/traces it times out. When
http://trace.filevacuum.com:14268/api/traces on POSTMAN it times out:
POST http://trace.filevacuum.com:14268/api/traces Error: connect ETIMEDOUT 555.555.555.555:14268 Request Headers User-Agent: PostmanRuntime/7.26.10 Accept: */* Cache-Control: no-cache Postman-Token: <TOKEN> Host: trace.filevacuum.com:14268 Accept-Encoding: gzip, deflate, br Connection: keep-alive
(at least I can see in PostMan that it hit my server’s IP and port)
- I turned off the Cloudflare proxy (just DNS) to try and help less things get in the way of the POST passing through.
- I’ve turned off as many security options as I could and tried other configurations.
- I set a specific Firewall Rule to Allow my IP.
- I set a Rule to allow this URI Path
I know the endpoint works because when I make it public
opentelemetry-rust POSTs traces to it fine that show up in the Jaeger app.
Here’s my Cloudflare DNS:
My Vultr Server’s Firewall Settings:
I thought setting the DNS A Record for
trace.filevacuum.com to just DNS and off proxy would have done the trick but it’s still getting caught somewhere in Cloudflare and timing out.
Getting a POST to pass through shouldn’t be too hard to do right?
Once I get it passing through I’ll setup mTLS via APISheild but need to get past this first.
Unless it’d listen to API Rules and let it through that way?
Any help is greatly appreciated. ♂