wooden-river-6675
11/28/2023, 3:37 PMswift-helmet-3648
11/28/2023, 3:45 PMwooden-river-6675
11/28/2023, 4:01 PMswift-helmet-3648
11/28/2023, 4:02 PM/backend
is pointing to /api
which it shouldn't be - it should point to /
on port :3100wooden-river-6675
11/29/2023, 8:09 AMswift-helmet-3648
11/29/2023, 3:39 PM/api
is the only endpoint we have that would return thatswift-helmet-3648
11/29/2023, 3:41 PM/
on the API, you should get something like this:
{
"name": "GrowthBook API",
"production": false,
"api_host": "<http://localhost:3100>",
"app_origin": "<http://localhost:3000>",
"config_source": "db",
"email_enabled": false,
"build": {
"sha": "",
"date": ""
}
}
wooden-river-6675
11/29/2023, 4:30 PMwooden-river-6675
11/29/2023, 4:31 PMswift-helmet-3648
11/29/2023, 4:32 PM/backend
is being passed along to the backend by ingress/loadbalancer.wooden-river-6675
11/29/2023, 4:33 PMswift-helmet-3648
11/29/2023, 4:34 PM<http://api.example.com|api.example.com>
instead. Alternatively, you could configure ingress to replace the path before sending to the backend but that seems harderwooden-river-6675
11/29/2023, 4:35 PMswift-helmet-3648
11/29/2023, 4:37 PMwooden-river-6675
11/29/2023, 4:38 PMswift-helmet-3648
11/29/2023, 4:38 PMswift-helmet-3648
11/29/2023, 4:39 PMwooden-river-6675
11/29/2023, 4:43 PMswift-helmet-3648
11/29/2023, 4:44 PMwooden-river-6675
11/29/2023, 4:45 PMswift-helmet-3648
11/29/2023, 4:45 PM<http://example.com/backend|example.com/backend>
and send it to your api as <http://example.com|example.com>
wooden-river-6675
11/29/2023, 4:46 PMswift-helmet-3648
11/29/2023, 4:47 PMwooden-river-6675
11/29/2023, 4:49 PMwooden-river-6675
11/29/2023, 4:54 PMswift-helmet-3648
11/29/2023, 4:55 PMwooden-river-6675
11/29/2023, 5:03 PMwooden-river-6675
11/29/2023, 5:05 PMwooden-river-6675
11/29/2023, 5:12 PMswift-helmet-3648
11/29/2023, 5:27 PMswift-helmet-3648
11/29/2023, 5:27 PMwooden-river-6675
11/29/2023, 5:49 PM