A website can work over HTTP while its HTTPS connection fails. These failures have been reported as a generic network_error, which makes it harder to understand why the screenshot failed and whether retrying will help.
We’re introducing secure_connection_failed for failures to establish a secure HTTPS connection to the target website. The error message explains the problem and suggests checking the site’s HTTPS configuration or trying its public HTTP URL.
If a public page works over HTTP, you can explicitly pass url=http://example.com while keeping the ScreenshotOne API endpoint on HTTPS. Use this only when an unencrypted connection to the target is acceptable and the request contains no credentials or sensitive data. ScreenshotOne does not automatically switch HTTPS requests to HTTP.
During rollout, these failures may still return network_error, so keep handling both error codes. See how to handle API errors for an updated example of showing the error to your users and deciding when to retry.
