-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Self-hosted control rooms have invalid SSL certificates, which causes api calls from the extension to fail #8144
Comments
Capturing discussion from Slack here: The current approach is to download the certificate and trust it in the operating system. Our public docs are here: https://docs.pixiebrix.com/how-to/troubleshooting/troubleshooting-network-errors#the-browser-blocked-the-request-because-the-https-certificate-on-the-server-is-invalid-untrusted
To my knowledge that's not possible. You'd have to find a Chrome setting to not verify the SSL certificate for API calls. E.g., in Postman, there's a Postman setting to not verify the SSL certificate |
@grahamlangford this should likely be @BLoe and @johnnymetz pairing to ensure our dev/test environment is working again and steps to use it are documented |
For reference, other people calling out that service worker can't make API calls to server with invalid certificate: w3c/webextensions#72 (comment) |
NotesFull URL: https://pixiebrix-controlroom-dev-4.eastus.cloudapp.azure.com Folder structurepki folder:
Commands I TriedNote: I installed openssl with chocolately [DIDN'T WORK: https://stackoverflow.com/a/41531915/6611672]
[DIDN'T WORK: https://learn.microsoft.com/en-us/azure/application-gateway/self-signed-certificates]
Resources:
|
Directions for setting up a Control Room certificate: https://www.notion.so/pixiebrix/Create-and-Trust-a-Control-Room-Certificate-5a0873f8edc84ae7947ebe88346b5319 |
@johnnymetz I think the last thing to close out this ticket should probably just be adding that guide to our user-facing docs somewhere, and we're good to go |
I don't know if I have all the information here, but from what I've learned so far, we have basically two options if we want to test the extension with self hosted CRs:
The text was updated successfully, but these errors were encountered: