[Spce-user] SSL for the provisioning interface

Andreas Granig agranig at sipwise.com
Wed Dec 29 08:19:51 EST 2010

Btw, seems like the server on port 443 is answering your request, instead of the one on 2443. Can you check /var/log/ngcp/oss.log for any hints of a redirect or an error?

"Andreas Granig" <agranig at sipwise.com> schrieb:

>Double-check that you really use https in your uri scheme when
>communicating with the provisioning interface.
>"Robert C. Chandler II" <robert3056519624 at yahoo.com> schrieb:
>>I'm receiving the following message when I try to test the
>>interface with 
>>the default CE self-signed SSL certificate (using https and port
>><title>400 Bad Request</title>
>><h1>Bad Request</h1>
>><p>Your browser sent a request that this server could not
>>understand.<br />
>>Reason: You're speaking plain HTTP to an SSL-enabled server port.<br
>>Instead use the HTTPS scheme to access this URL, please.<br />
>><blockquote>Hint: <a 
>><address>Apache/2.2.9 (Debian) mod_ssl/2.2.9 OpenSSL/0.9.8g
>>Perl/v5.10.0 Server at myserver Port 443</address>
>>---END DATA---
>>Is a certificate signed by a CA required to use the provisioning
>>interface via 
>>XML-RPC or can I use a 
>>self-signed certificate?  If a CA signed certificate is required for
>>SSL how can 
>>I temporarily disable SSL 
>>while I test the provisioning interface?
>>Spce-user mailing list
>>Spce-user at lists.sipwise.com
>Spce-user mailing list
>Spce-user at lists.sipwise.com

Andreas Granig
CTO, Sipwise GmbH

More information about the Spce-user mailing list