And checked it through the “HTTP show status” command.
HTTP Server Status:
Prefix: /asterisk
Server: Asterisk
Server Enabled and Bound to 0.0.0.0:8088
HTTPS Server Enabled and Bound to 0.0.0.0:8089
Enabled URI's:
/asterisk/httpstatus => Asterisk HTTP General Status
/asterisk/phoneprov/... => Asterisk HTTP Phone Provisioning Tool
/asterisk/ari/... => Asterisk RESTful API
/asterisk/ws => Asterisk HTTP WebSocket
It seems to work as I see the message https server enabled
but I keep getting the following error message when I try to connect to the was through
wss://[myip]:8089/asterisk/ws
[Aug 28 15:09:16] ERROR[8086]: iostream.c:647 ast_iostream_start_tls: Problem setting up ssl connection: error:00000001:lib(0):func(0):reason(1), Internal SSL error
[Aug 28 15:09:16] ERROR[8086]: tcptls.c:179 handle_tcptls_connection: Unable to set up ssl connection with peer '219.75.139.45:63402'
[Aug 28 15:09:16] ERROR[8086]: iostream.c:552 ast_iostream_close: SSL_shutdown() failed: error:00000001:lib(0):func(0):reason(1), Internal SSL error
Anybody got a clue what I am doing wrong here?
Your help would be highly appreciated.
Visit https://[myip]:8089/ in your browser and ensure that the self signed certificate is accepted. If it’s not, then when the browser connects on that page it may not prompt you to accept it - and thus fail.
It indeed shows an error and the Asterisk certificate is not accepted.
As I understand correct; the self sign certificate of asterisk is not correct.
To use a correct certificate I should get one from a official CA provider like letsencryp for example.
A self signed certificate is just that, self signed. Since it is such then the browser will not automatically trust it like is done for certificates issued by actual authorities. You can still use a self signed certificate but must ensure it is trusted in the browser, which depends on the browser. Using an actual issued certificate however removes that step and is simpler long term.