This message was deleted.
# ask-questionsw
worried-planet-2191
12/13/2023, 5:15 PMThis message was deleted.
r
rhythmic-agent-34208
12/13/2023, 9:13 PMHi Geoffrey, if your API and Back End server on port 3100 is crashing, then the proxy definitely won't work.
Please try setting things up without the proxy first, then see what's going wrong before adding in the proxy.
m
modern-lock-72431
12/14/2023, 9:55 AMHi @brief-honey-45610 I've tried and still the same
and the ui is out
r
rhythmic-agent-34208
12/19/2023, 11:39 PMHi Geoffrey, are you able to visit the `/healthcheck` endpoint at `http://localhost:3300/healthcheck` ? Change the port to the port you're using.
rhythmic-agent-34208
12/19/2023, 11:40 PMMake sure that all the necessary environment variables are correctly set. These include:
`GROWTHBOOK_API_HOST`,
`SECRET_API_KEY`,
`NODE_ENV`,
`CACHE_ENGINE`,
`CACHE_CONNECTION_URL`,
`CACHE_STALE_TTL`,
`CACHE_EXPIRES_TTL`.
Double-check the values for any typos or incorrect URLs.
rhythmic-agent-34208
12/19/2023, 11:40 PMEnsure that the GrowthBook API host is accessible from the location where the proxy is running. If you are using a load balancer or reverse proxy for SSL termination, confirm that it is configured correctly to forward requests to the GrowthBook Proxy.
rhythmic-agent-34208
12/19/2023, 11:41 PMIf you are using a load balancer in front of the GrowthBook Proxy, ensure that it supports HTTP/2 and streaming responses, as recommended for high-traffic production scenarios.
rhythmic-agent-34208
12/19/2023, 11:45 PMIf you are using Redis or MongoDB as the cache engine, verify that the connection URL is correct and that the GrowthBook Proxy can connect to the cache engine.
The GrowthBook server itself does not support SSL directly. If you need SSL, use a load balancer or reverse proxy to handle SSL termination.
169 Views