I am seeing this error on the logs after enabling metrics, any suggestions? ```Process is not runnin...
p

Pantelis Karamolegkos

over 2 years ago
I am seeing this error on the logs after enabling metrics, any suggestions?
Process is not running on K8S Error: Failed to load page, status code: 403
    at IncomingMessage.<anonymous> (/usr/local/src/app/node_modules/@opentelemetry/resource-detector-aws/build/src/detectors/AwsEksDetector.js:192:32)
    at /usr/local/src/app/node_modules/@opentelemetry/context-async-hooks/build/src/AbstractAsyncHooksContextManager.js:50:55
    at AsyncLocalStorage.run (node:async_hooks:319:14)
    at AsyncLocalStorageContextManager.with (/usr/local/src/app/node_modules/@opentelemetry/context-async-hooks/build/src/AsyncLocalStorageContextManager.js:33:40)
    at IncomingMessage.contextWrapper (/usr/local/src/app/node_modules/@opentelemetry/context-async-hooks/build/src/AbstractAsyncHooksContextManager.js:50:32)
    at IncomingMessage.emit (node:events:525:35)
    at IncomingMessage.emit (node:domain:489:12)
    at endReadableNT (node:internal/streams/readable:1358:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
{"stack":"Error: connect ECONNREFUSED 127.0.0.1:4318\n    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)\n    at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17)","message":"connect ECONNREFUSED 127.0.0.1:4318","errno":"-111","code":"ECONNREFUSED","syscall":"connect","address":"127.0.0.1","port":"4318","name":"Error"}
Hi all, I'm trying to run growthbook self-hosted on AWS, and I've managed to get the `growthbook/gr...
s

Spencer Kohan

about 1 year ago
Hi all, I'm trying to run growthbook self-hosted on AWS, and I've managed to get the
growthbook/growthbook:latest
container up and running and connected to a
DocumentsDB
cluster, but when I actually try to access the webapp, I get this error: > Error connecting to the GrowthBook API ... No authorization token was found From what I can tell it seems to be maybe related to this issue: https://linen.growthbook.io/t/34006/i-have-another-question-whilst-we-are-exploring-the-product- What I don't understand is, it seems to be the request to /auth/refresh which is returning 401, which doesn't make sense because I understood the token is expected not to exist, and should be generated on the first refresh Here's what I'm seeing from the container logs (note, I have the api mapped to host/api-route/ via an application load balancer):
{"level":50,"time":1727955520197,"pid":75,"hostname":"ip-10-0-165-156.eu-west-1.compute.internal","req":{"id":5,"method":"POST","url":"/api-route/auth/refresh","query":{},"params":{},"headers":{"x-forwarded-for":"94.134.28.56","x-forwarded-proto":"http","x-forwarded-port":"80","host":<host>,"x-amzn-trace-id":"Root=1-66fe8240-305abbc60e0d26dc5bbe8a0a","content-length":"0","user-agent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36","dnt":"1","origin":<host>,"referer":<host>},"remoteAddress":"::ffff:10.0.116.205","remotePort":62760},"msg":"No authorization token was found"}
Is this a known issue / is there anything I can do to get around it?