API Keys for Server

I think this is a different problem, it can't validate the cert. They have recently renewed their cert so it could be either you are getting the old cert or your setup can't validate it.

Screenshot 2023-06-16 at 21.25.24.png (65.46 KiB) Viewed 1692 times

Can you install this on your Indigo's Python install?

Code: Select all

pip install --upgrade certifi

Also getting Error Unable to connect to IndigoDomo.com

Not happy how this is implemented

I appreciate the error may be different but the root cause (needing to connect to a remote server to run things locally) is the same.

I’m unfamiliar with indigos python install. I don’t run any embedded scripts. Further instructions appreciated.

[matt (support)]

We are experiencing a server problem. Actively working on it now and will post when it is fixed.

[matt (support)]

We had a problem with how a new SSL certificate was installed on our server which caused problems for the Indigo Server.

It is fixed now, but may take 15 minutes for your reflector to re-establish itself. Appreciate everyone's patience with this not working earlier.

As of 23:57 (uk time) and a quick server reboot, all appears to be operational again. Thanks

[matt (support)]

The original post on this thread was requesting API keys that don't require backend calls to our server for validation. The most recent release (2023.1.0) now has this capability via what we call Local Secrets.

Many thanks for fulfilling this. I would have preferred to call them local keys and also to use public/private API keys to avoid having hardcoded keys in plain text config files but this would do nicely for the people like me that want full offline mode operation.

PS: A bit of FUD on the logging message when using local secrets...

Code: Select all

 Web Server Warning              HTTP API v2 POST command received, id: 'optional-user-generated-id' from '192.168.111.11'

[jay (support)]

PS: A bit of FUD on the logging message when using local secrets...

Code: Select all

 Web Server Warning              HTTP API v2 POST command received, id: 'optional-user-generated-id' from '192.168.111.11'

That's not FUD. We believe (based on prior feedback among other things) that users should be very aware of any incoming API connections. This message is shown for all API messages (not just for those using local secrets). You can turn off these warnings in the new Advanced Web Server Config dialog.

That's not FUD. We believe (based on prior feedback among other things) that users should be very aware of any incoming API connections. This message is shown for all API messages (not just for those using local secrets). You can turn off these warnings in the new Advanced Web Server Config dialog.

I agree on that 100%. I just don’t think an API call should be logged as a Warning message and neither should be highlighted in yellow (which is a side effect of logging it as a warning). So if I want logging I need to leave the warning messages.