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

[Alex Lutay]

Hi,

The issue is still open and we are working to solve it fast.


On 06/26/2016 11:31 PM, Matthias Hohl wrote:
> Hello,
> 
> i updated today on the latest 4.4.1 version of SPCE and this bug is still
> there after activating "sslverify" in config.yml:
> 
> root at spce:~# /usr/sbin/ngcp-fraud-daily-lock
> 500 Can't connect to 127.0.0.1:1442 (certificate verify failed) Can't
> connect to 127.0.0.1:1442 (certificate verify failed)
> SSL connect attempt failed error:14090086:SSL
> routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed at
> /usr/share/perl5/LWP/Protocol/http.pm line 49.
> 
> Any information, when this will be fixed?
> Thanks for your help.
> 
> 
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: Alex Lutay [mailto:alutay at sipwise.com] 
> Gesendet: Montag, 6. Juni 2016 14:14
> An: Alexander Griesser <AGriesser at anexia-it.com>; Matthias Hohl
> <matthias.hohl at telematica.at>; spce-user at lists.sipwise.com
> Betreff: Re: AW: AW: AW: [Spce-user] Can't connect to 127.0.0.1:1442
> (certificate verify failed)
> 
> Hi all,
> 
> On 06/06/2016 02:00 PM, Alexander Griesser wrote:
>> But we still need to find a way for the fraud detection script to 
>> successfully connect to 127.0.0.1:1442 using our valid certificate - 
>> any further ideas about this issue?
> 
> Yes, it is a good question, I need Kirill comments here.
> Anyway tnx for pointing, we will address it internally as MT#20341
> 
> --
> Alex Lutay
> 
> Meet us @ ANGACOM: Hall 10.1 / booth N10 Exhibition and Congress for
> Broadband, Cable & Satellite: 07 – 09 June, 2016 in Cologne
> 

-- 
Alexander Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: https://www.sipwise.com