[Spce-user] Can't connect to 127.0.0.1:1442 (certificate verify failed)

Serge S. Yuriev me at nevian.org
Mon Jun 6 07:14:02 EDT 2016


Hello,

On 06/06/16 12:43, Alex Lutay wrote:
> Hi all,
>
> On 06/04/2016 04:25 PM, Serge Yuriev wrote:
>> Subject:Cron <root at host>  if /usr/sbin/ngcp-check_active -q; then /usr/sbin/ngcp-fraud-daily-lock; fi
>
> It means you have selfsigned certificate.
> As some components were switch to internal REST API the trusted cert is
> really mandatory now. Leaving in a world on corporate PRO/Carrier
> solutions we missed the fact of spce@ insecure users.

> It is HIGHLY recommended to use option
>> security > ngcp-panel > scripts > restapi > sslverify
> in TEST env ONLY, for any kind of production setup the trusted
> certificate is MUST have. They are free nowadays and requires
> 15 minutes to achieve/install one.

In our case is a very test system (and likely not go in prod) so I think 
this option fine for us.

>>> 502 Bad Gateway <html>
>
> It means ngcp-panel did not start.
> please check ngcp-panel log for more information.

Yes I have already found this - for some reason panel not started 
automaticaly after ngcpcfg apply

Thank you.

-- 
Serge S. Yuriev
Lead VoIP engineer




More information about the Spce-user mailing list