Hi y'all! We just set up Growthbook and we are rea...
# ask-questions
q
Hi y'all! We just set up Growthbook and we are really excited! I tried to set up the Chrome browser extension but I'm getting errors in the console and the extension doesn't open:
GET <https://cfrp-growthbook-msinfra-gitlab-bot-test.wattbuy.com/sub/sdk-xr00JmwSfLVE60DD> net::ERR_QUIC_PROTOCOL_ERROR 200
The extension asks for the API host and the API secret. Should I be using the SDK connection host and client key? Or setting up an API key?
s
Hi @quiet-spring-78839 You must be using an older version of our self-hosted app ... You'll need to generate an API key for that to work. However, if you update to latest, that flow has been eliminated to be completely streamlined with no API key generation necessary.
q
Huh. I don't think we are self-hosting. We are on the free plan, though.
s
That's weird. Can you relay to me the version of your Chrome Extension then?
q
0.3.1
s
Could you send me a screenshot of where the extension is asking for the API host and key?
q
Yeah!
s
Thank you
q
I go to Options there
and it takes me here
s
Ah, okay. Those are usually automatically set. And they are only used for the Visual Editor only. I would clear them out for now in your case. This is probably an improvement we can be clear about this in the modal..
q
Ohhhh ok. Strange. Well, when I don't have them, the extension also doesn't work. Should it render as a sidebar on the site if things are working correctly?
s
The sidebar is the Visual Editor. That can only be opened from a GrowthBook experiment page
q
Ohhhh
s
The Devtools feature is in the Chrome Devtools panel, which you'll have to open up
q
Ohhhhhhhh
oh!
I see it!
s
Ok great
q
Sorry I didn't understand that.
Thank you for the help!!!
🙌🏾 1
s
No problem!
q
@swift-helmet-3648 ok even though I found the location in the Chrome dev tools, it seems like we are unable to connect. I confirmed with my engineer that we are not doing self-hosted but are using a reverse proxy. Could that be related?
Another question from him:
"I wonder if I have to call loadFeatures to connect in the browser? I'm loading things server side and then just initializing growthbook in the client with the features we loaded on the server. So I never call
loadFeatures
. In case that matters."
Maybe that could be related?
s
Yes, you'll need to call loadFeatures in the browser for DevTools to recognize the SDK
q
Woot ok cool!