HTTP SMSC Connection can't be saved

HTTP SMSC Connection can't be saved SearchSearch
Author Message
New member
Username: Peter01

Post Number: 8
Registered: 10-2020
Posted on Wednesday, March 10, 2021 - 12:04 am:   

Hi Team,

I am trying to define an HTTP SMSC connection, but when I push the "save" button, nothing happens.

I notice in my browser that there is a Javascript error. How can I save the connection?


Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 8415
Registered: 10-2002
Posted on Wednesday, March 10, 2021 - 04:45 am:   

Hi Peter,

Yes, there does seem to be an error when trying to save HTTP SMSC connections where the URL does not include an explicit port number. For example: http://provider and https://provider will not save, but http://provider:80 or https://provider:443 will save.

So, as a workaround, it is possible to simply add the port number to the hostname or IP address portion of the URL.

Normally port numbers are not required if using a standard port (80 for http or 443 for https).

Interestingly, if you do add the port number to the URL and save ... then edit the connection, NowSMS removes any standard port numbers.

We've fixed the Javascript error in the embedded web form and pushed out an update, version 2021.03.10. This update can be applied via the NowSMS NextGen web interface under Admin/System Configuration, or via the download links on our website.


Bryce Norwood
NowSMS Support

Add Your Message Here, or click here to start a new topic.
Bold text Italics Underline Create a hyperlink Insert a clipart image
Options: Automatically activate URLs in message