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

Matthias Hohl matthias.hohl at telematica.at
Wed Aug 24 18:42:56 EDT 2016


 i did update to the latest version and set

ssl_verify = yes
ssl_verify_loopback = no

now if I try to execute the fraud check script and it looks like it works now.

Btw: you wrote "you can switch it to yes to skip the certificate validation to loopback" but I think you mean " you can switch to yes to NOT skip the certificate validation on lookback" or?

-----Ursprüngliche Nachricht-----
Von: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] Im Auftrag von Alex Lutay
Gesendet: Montag, 22. August 2016 14:01
An: spce-user at lists.sipwise.com
Betreff: Re: [Spce-user] Can't connect to (certificate verify failed)


It has been addressed long time ago and backported to mr4.4.1 in a safest way: A new option "ssl_verify_loopback" is introduced in config.yml and it is 'no' by default, causing all requests from interfaces starting with "lo" or "dummy" to skip the verify.

You can switch it to 'yes' to skip certificate validation on loopback.

Does it work for you?

On 08/22/2016 01:49 PM, Matthias Hohl wrote:
> any news about that?

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
Spce-user mailing list
Spce-user at lists.sipwise.com

More information about the Spce-user mailing list