Unanswered question

Why SSL_ERROR_RX_RECORD_TOO_LONG error is occurring while recording

While Recording a scenario in proxy mode on
https://dkdl6003.dcsgomni.com:9443/genesis/Crossview_ui_e..., getting
SSL_ERROR_RX_RECORD_TOO_LONG (see an attachment pls.) error in Mozilla firefox

Manual VU check shows:
Error detected by NeoLoad
Error Code: NL-NETWORK-01 Message: Network error: An IO error occurred sending the request. Details: java.io.IOException: org.apache.http.conn.HttpHostConnectException: Connect to dkdl6003.dcsgomni.com:9443 failed: Connection timed out: connect

I did add jdk.tls.disabledAlgorithms=DHE, ECDHE option in java.security file.But still facing the same issue.Please help on this

Abirami V.
Abirami V.

Abirami V.

Level
1
159 / 750
points

Answers

The two errors from the recording and from the check virtual user indicate two different issues which does not make sense.

The check VU seems to indicate an issue to reach your server like with some firewall issue. If it was a SSL issue i would expect a different error. But the recording seems to indicate a SSL issue that's why i'm confused here.

When you manually connect to your URL, what is the SSL settings like cipher used, SSL version etc...

Do you need a proxy to reach that URL? If yes have you configured it in NeoLoad?

Abirami V.
Abirami V.

Abirami V.

Level
1
159 / 750
points

The mentioned application is available in two different servers(two different environments). I have already recorded the application functionality in one server in which I am not facing any issues. I have just modified the recorded request with mentioned server name. Thats when I came across the NL-NETWORK-01 error while validating.

After that only I tried to record the application and thats whenSSL_ERROR_RX_RECORD_TOO_LONG error is shown in mozilla.

It doent need any particular proxy settings.

Could you check if in your <install_dir>\conf\controller.properties file under General section that you have TLSv1.2 on the list of SSL protocol.

If not please add it to the list, restart NeoLoad and try again the check virtual user.