Highlighted
Trusted Contributor.
Trusted Contributor.
5046 views

SSL Errors after initial few successful replays

Jump to solution

I have been running https based scripts successfully over last few days (to a cloud service) , but suddenly I started seeing below SSL error. Does anyone know the possible reasons for all of a sudden appearance of error..

ssl_handle_status encounter error : SSL_ERROR_SSL, error message : error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure   [MsgId: MMSG-26000]

 

Tags (1)
0 Likes
17 Replies
Highlighted
Regular Contributor.
Regular Contributor.

Hi, did you go into the Networking and Filtering dialog and set up an entry for the server under test?

we have enabled auto SSL detection under that SSL version selected as "SSL 2/3" and SSL CIPHERS AS"Default Open SSL Ciphers"

As you stated correctly we can't system can't compromise with TLS option. Please help how to avoid below eeror from executin. If replay from vugen, it give error and passing. But if we run from controller then all the errors are accumilating it is going around 500 errors

Action.c(14): ssl_handle_status encounter error : SSL_ERROR_SYSCALL, error id : 0 [MsgId: MMSG-26000]
Action.c(14): ssl_handle_status encounter error : SSL_ERROR_SSL, error message : error:140E0197:SSL routines:SSL_shutdown:shutdown while in init [MsgId: MMSG-26000]
Action.c(14): ssl_handle_status ssl_handle_status encounter error : SSL_ERROR_SSL when read, retry count = 0 [MsgId: MMSG-26000]

 

0 Likes
Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..
I'm sure you took the one meaningful error code and searched for its meaning (140E0197). The components in the system you are testing are not described in the postings I've seen, so I/we have no way of knowing what to suggest as your next course of action. As with everything in data processing, you need to take a logical approach to the issue at hand to arrive at the root cause. You need to identify the components involved and involve their owners/vendors.
Again, using any version of TLS less than 1.2 is foolhardy. If any system in the real world is still using SSL, it should be regarded as broken or, at best, a honeypot. That LoadRunner defaults to suggesting use of SSL 2/3 seems to be some sort of lowest common denominator branch in its logic tree and generally ignored. To be blunt, if your organization has a developer who is ignorant of the fact that SSL was considered broken as of 1996 or so, s/he should be taken to a reeducation camp. TLS 1.3 was accepted as the current version in 2018. TLS 1.2 is acceptable until such time as 1.3 has achieved a critical mass of deployment.
-TN
0 Likes
Highlighted
Regular Contributor.
Regular Contributor.

Thanks, i will check with devteam on this and come back

0 Likes
Highlighted
Regular Contributor.
Regular Contributor.

Hello,

I have update on this issue, when i run this script from my laptop it is working fine, if i run from controller machine then ssl error comes. Is it do with some port or firewall settings. If so please let me know what change i have to do and how to change

0 Likes
Highlighted
Regular Contributor.
Regular Contributor.

If i open my application in chrome then run through VUGEN then it is working fine

0 Likes
Highlighted
Valued Contributor.
Valued Contributor.

I tried setting the SSL version in the Runtime Settings first but that did not seem to work.

For me the option worked : web_set_sockets_option("SSL_VERSION", "TLS1.2");

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.