I’m trying to play with my Philips Hue bridge. It’s on my local network, so at a 192.168.x.xxx address.
It works with the Windows app of Apidog but not with the Chrome extension. Is that an expected behavior?
I’m trying to play with my Philips Hue bridge. It’s on my local network, so at a 192.168.x.xxx address.
It works with the Windows app of Apidog but not with the Chrome extension. Is that an expected behavior?
Can you provide more screenshots or error about this request? Can you confirm whether you selected “Browser Extensions” under “Auto Agent” when using the web app?
Thanks Karan for your suggestion.
I changed the agent to Browser extension and registered a new key
I see the web extension cannot connect via https, that might be it
Yes, browser plugins follow the security settings of the browser. By default, browsers do not trust self-signed certificates.
But you can try accessing this URL using your browser in a new tab first to see if your browser supports manually trusting a self-signed certificate.
Which is the message I get when trying the http instead of https with Apidog
So, to make the Apidog extension work, I would need to fiddle with the Chrome settings and trust self-signed certificates? Is it possible to activate that only for local addresses on trusted networks?
You can try following the following instructions in the link to attempt adjusting Chrome settings:
It installed properly in the Trusted Root Certificate Authorities but it still doesn’t work.
Oh well, I’ll use the Windows app
The security settings are designed by Chrome. I believe there is nothing else we can do in our web app or browser plugin. Instead, you should use the Desktop app for debugging with self-signed APIs.
Thanks for having taken the time!