Scope could not be started because of a connection issue: here are some common error codes and their meanings.
There are several reasons and different layers of errors that can prevent Scope from starting properly. This table gives you a hint on how severe the issue is/was.
On the most common timeout errors, it might be helpful to check the Scope status page. There could be an ongoing incident or maintenance that affects your services.
https://status.riege.com/
| Error | Error Explanation |
| connect timed out | The system tried to connect but took too long and gave up. Usually caused by slow or unreachable servers. |
| 503 service unavailable | The server is temporarily unable to handle the request, often due to overload or maintenance. |
| read timed out | The server didn’t send data in time, so the connection was closed. |
| PKIX path validation | The system couldn’t verify the security certificate of the server. |
| connection reset | The connection was unexpectedly closed, often due to network issues or firewall settings. |
| PKIX path building | The system couldn’t build a trusted path to verify the server’s certificate. |
| 502 bad gateway | A server acting as a gateway received an invalid response from another server. |
| remote host terminated the handshake | The server stopped the secure connection setup, likely due to mismatched security settings. |
| received fatal alert | A serious error occurred during secure connection setup, often due to incompatible security settings. |
| permission denied | The system or user doesn’t have the rights to access the file or resource. |
| unable to tunnel through proxy | The system couldn’t connect through the proxy server. |
| unexpected end of file | The system expected more data but the file or stream ended too soon. |
| 403 forbidden | Access to the resource is blocked; permission is denied. |
| network is unreachable | The system couldn’t find a path to the network or server. |
| 408 request time-out | The server took too long to respond to the request. |
| http 500 | A general server error occurred while processing the request. |
| no route to host | The system couldn’t find a way to reach the server. |
| software caused connection abort | A software issue caused the connection to close unexpectedly. |
| unrecognized ssl error | An unknown issue occurred during secure connection setup. |