[Home]

Summary:ASTERISK-29133: Problem setting up ssl connection: error:00000001:lib(0):func(0):reason(1), Internal SSL error
Reporter:Faiz Ali (roxane_11)Labels:webrtc
Date Opened:2020-10-18 02:12:07Date Closed:2020-11-01 12:00:01.000-0600
Priority:MinorRegression?
Status:Closed/CompleteComponents:Resources/res_crypto
Versions:17.7.0 Frequency of
Occurrence		Constant
Related
Issues:
Environment:Attachments:
Description:I am trying to setup asterisk webrtc using the doc:
https://wiki.asterisk.org/wiki/display/AST/Configuring+Asterisk+for+WebRTC+Clients

however, when i try to connect chrome browser to
https://<IP>:8089/ws i get this error:

Problem setting up ssl connection: error:00000001:lib(0):func(0):reason(1), Internal SSL error


http.conf:

[general]
enabled=yes
bindaddr=0.0.0.0
bindport=8088
tlsenable=yes
tlsbindaddr=0.0.0.0:8089
tlscertfile=/etc/ssl/certs/nginx-selfsigned.crt
tlsprivatekey=/etc/ssl/private/nginx-selfsigned.key
tlsclientmethod=ALL
tlscipher=ALL

self signed certificate created by openssl
sudo openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout /etc/ssl/private/nginx-selfsigned.key -out /etc/ssl/certs/nginx-selfsigned.crt

Comments:By: Asterisk Team (asteriskteam) 2020-10-18 02:12:08.337-0500

The severity of this issue has been automatically downgraded from "Blocker" to "Major". The "Blocker" severity is reserved for issues which have been determined to block the next release of Asterisk. This severity can only be set by privileged users. If this issue is deemed to block the next release it will be updated accordingly during the triage process.
By: Asterisk Team (asteriskteam) 2020-10-18 02:12:08.598-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].
By: Joshua C. Colp (jcolp) 2020-10-18 04:39:53.736-0500

What browser are you using? What Linux distribution? Have you accepted the self signed certificate? If you visit https://<ip>:8089/ and accept the self signed certificate does it work?
By: Asterisk Team (asteriskteam) 2020-11-01 12:00:00.844-0600

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines