| Summary: | ASTERISK-28872: Asterisk services are not starting with ssl on 8089 port after configured http.conf | ||
| Reporter: | Amit Kumar Sinha (amitsinha280) | Labels: | security webrtc |
| Date Opened: | 2020-05-05 06:29:06 | Date Closed: | 2020-05-05 06:30:49 |
| Priority: | Trivial | Regression? | |
| Status: | Closed/Complete | Components: | . I did not set the category correctly. |
| Versions: | 17.4.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Ubuntu 18.04 asterisk 17.4.0 | Attachments: | |
| Description: | i configured http.conf with letsencript/slef signed ssl certificate but secure services are not starting on port 8089. I follow docs https://wiki.asterisk.org/wiki/display/AST/Configuring+Asterisk+for+WebRTC+Clients and i visited https://community.asterisk.org/t/not-able-to-connect-asterisk-while-trying-with-wss-connection/65658/2 but it didn't resolve and i stuck at this point. The hello world program and mini http server part is working correct with softphone.
Asterisk cli output of http show status is HTTP Server Status: Prefix: Server: Asterisk/17.4.0 Server Enabled and Bound to 0.0.0.0:8088 Enabled URI's: /httpstatus => Asterisk HTTP General Status /phoneprov/... => Asterisk HTTP Phone Provisioning Tool /metrics/... => Prometheus Metrics URI /ari/... => Asterisk RESTful API /ws => Asterisk HTTP WebSocket Enabled Redirects: None. Please help me to overcome this issue. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2020-05-05 06:29:08.695-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. 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. By: Asterisk Team (asteriskteam) 2020-05-05 06:29:09.405-0500 This issue has been automatically restricted and set to a blocker due to being a security type issue. If this is not a security vulnerability issue it will be moved to the appropriate issue type when triaged. By: Joshua C. Colp (jcolp) 2020-05-05 06:30:42.245-0500 We appreciate the difficulties you are facing, however this does not appear to be a bug report and your request or comments would be better served in a different forum. The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors. Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines | ||