I just started experimenting with ssllabs-scan a few days ago. Yesterday afternoon, I started getting NOTICEs when I tried to run it that it received a 529 and would sleep for some long amount of time. It is still happening today. Here is an example:
2024/05/31 15:13:43 [DEBUG] Request #1: https://api.ssllabs.com/api/v4/info
2024/05/31 15:13:44 [DEBUG] Response #1 status: HTTP/1.1 200
2024/05/31 15:13:44 [DEBUG] Server set current assessments to 0
2024/05/31 15:13:44 [DEBUG] Server set maximum assessments to 25
2024/05/31 15:13:44 [INFO] SSL Labs v2.3.0 (criteria version 2009q)
2024/05/31 15:13:44 [NOTICE] Server message: This assessment service is provided free of charge by Qualys SSL Labs, subject to our terms and conditions: https://www.ssllabs.com/about/terms.html
2024/05/31 15:13:46 [INFO] Assessment starting: google.com
2024/05/31 15:13:46 [DEBUG] Request #2: https://api.ssllabs.com/api/v4/analyze?host=google.com&all=done&startNew=on
2024/05/31 15:13:46 [DEBUG] Response #2 status: HTTP/1.1 529
2024/05/31 15:13:46 [NOTICE] Sleeping for 26 minutes after a 529 response
I understand that 529 indicates that the server is overloaded, however, when I use the SSLLabs WebUI at https://www.ssllabs.com/ssltest/ it works just fine to run server tests in just a few minutes. Is the server truly overloaded? If so, how often does this happen?
Similarly, I have been having problems getting 529 responses since last week. However, when I ran the API on approximately 2024-06-06T01:30:00Z, it started working properly.
I just started experimenting with ssllabs-scan a few days ago. Yesterday afternoon, I started getting NOTICEs when I tried to run it that it received a 529 and would sleep for some long amount of time. It is still happening today. Here is an example:
I understand that 529 indicates that the server is overloaded, however, when I use the SSLLabs WebUI at https://www.ssllabs.com/ssltest/ it works just fine to run server tests in just a few minutes. Is the server truly overloaded? If so, how often does this happen?