Open source feature flagging and experimentation platform for stress free deployments, measured impact, and smarter decisions.

GrowthBook Users

yes, curl "<http://gb-api.example.com:3100>" returns output

are you getting a CORS error with that 'failed connecting' ? (if you look in the console)

the only error in browser console is <http://gb-api.example.com|gb-api.example.com> refresh fetch mixed block and looks denied

so either the request is not making it to the API end point, or the API end point is ignoring it because of the CORS headers

docker logs shows this: "{"level":30,"time":1736366925462,"pid":59,"hostname":"t2gb1","msg":"Back-end is running at <http://localhost:3100> in production mode. Press CTRL-C to stop"}"

can you share or DM the request details from the console?