| https URL Support |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ |
◄ ► |
| Author | Message | |||
| Tasneem Abumhlula New member Username: Tasneemmh Post Number: 1 Registered: 08-2022 |
Dear Support, Dose NowSMS support a https connection from another server? like using https:// in URL instead http://***.***.***.***:8800/?user=------&password=-------. Thanks.}} | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 6338 Registered: 08-2008 |
Yes, but ... Setting up a server for HTTPS is more difficult, because an SSL/TLS certificate needs to be installed on the server. This is the case with any server that provides an HTTPS interface, including NowSMS. Go to the SSL/TLS page in NowSMS Windows, or the SSL/TLS Certificate section in NowSMS Linux, to begin this process. The normal procedure is that you use the option in NowSMS to create a Certificate Signing Request (CSR). The CSR is a text file (SSL.CSR, usually in Program Files (X86)/NowSMS in Windows or /var/lib/nowsms in Linux), and you need to submit the data in this file to a Certificate Authority (CA). The CA will issue an SSL/TLS certificate, which you need to save in a text file named SSL.CA in the same directory as SSL.CSR. The NowSMS service needs to be restarted after SSL.CA is applied. When you create the CSR, NowSMS will enable additional configuration settings where you specify the TCP port number to be used for HTTPS (SSL/TLS). Once you have HTTPS working, if you wish to disable plain-text HTTP, next to the port number settings there is an "SSL Redirect Only" option. When this option is set, any attempts to connect to the plain text HTTP port will receive a "redirect" response indicating that HTTPS must be used. Regards, Des NowSMS Support | |||
| Tasneem Mh New member Username: Tasneemmh Post Number: 2 Registered: 08-2022 |
Dear support , Firstly, thanks for your response, i followed the previous steps starting from creat CRS and submitted with CA . But i still get the issue hen i access the web url it shows not secure connection, it appears to be the CRS i creat from nowsms is having a missing value (Subject Authority Name) how i over come this issue in-order to have a fully secure connection. Thanks in advance | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 6340 Registered: 08-2008 |
Hi, I'm sorry, but I don't know what a "Subject Authority Name" is. In an SSL certificate, there is a concept of a "Subject Alternative Name", which is related to additional host names in a single certificate. The CSR generated by NowSMS is for a single host name which is encoded as "Common Name". Your message suggests that you are seeing this error in your web browser. Perhaps you are connecting to the server by IP address, but SSL certificates are assigned to a host name, so you need to use the host name in the URL. Regards, Des NowSMS Support | |||
| Tasneem Mh New member Username: Tasneemmh Post Number: 3 Registered: 08-2022 |
Hi Des, I am already using the hostname in the URL and still get the following error.  | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 6341 Registered: 08-2008 |
Hi, I am not an expert on HTTPS certificates, but when I google ERR_CERT_COMMON_NAME_INVALID, it tells me that the host/server name in the URL does not match the host name (also known as "common name") in the certificate. When you generated the CSR in NowSMS, the "Host Name" needs to be the same as the host/server name in your URL. Regards, Des NowSMS Support | |||
| Tasneem Mh New member Username: Tasneemmh Post Number: 3 Registered: 08-2022 |
Hi Des , the certificate I generate from Nowsms app just worked fine only with internet explorer but not with Edge and chrome , and the main reason is that internet explorer (IE) does not require to have a Common Name in the SAN unlike the All modern browsers .  any recommended solution to make it work with modern browser. Thanks in advance. Tas | |||
