Learn what Felgo offers to help your business succeed. Start your free evaluation today! Felgo for Your Business

Forums

OverviewFelgo 2 Support (Qt 5) › ssl handshake failed, very urgent !!!

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #24468

    Felgo User

    Help needed.

    I am using Felgo 3.50 and today all my clients (> 10) showing SSL handshake failed.

    Client is configured with win 10 LTBS for POS.

    I did following test, same bin can function correctly on my desktop.

    I can curl with no problem from client.

    If I do http, all client machines work well.

    I am pretty much stuck now, not knowing what to do.

    Please advise.

     

    Jun

    #24469

    Alex
    Felgo Team

    Hi,

    if this starts to fail simultaneously for all of your clients, my first guess would be that there is an issue with the SSL certificate on the host machine? Is the target of the request a self hosted service?

    Best,
    Alex

    #24471

    Felgo User

    hi Alex,

    I can do curl from same client to same server without problem.

    seemed only using httpreuqest had issue.

    Same program runs ok on my desktop to the same server too.

    I can setup a teamviewer if that helps.

    I do need advise on this. otherwise I am pretty much doomed. we built product years on top of vplay. and this issue is such fundamental I can’t tell how to workaround at this moment.

    I simplified my code as below. Just a https get.

     

    import Felgo 3.0
    import QtQuick 2.0
    
    
    App {
        // You get free licenseKeys from https://felgo.com/licenseKey
        // With a licenseKey you can:
        //  * Publish your games & apps for the app stores
        //  * Remove the Felgo Splash Screen or set a custom one (available with the Pro Licenses)
        //  * Add plugins to monetize, analyze & improve your apps (available with the Pro Licenses)
        //licenseKey: "<generate one from https://felgo.com/licenseKey>"
    
    
        NavigationStack {
    
    
            Page {
                title: qsTr("Main Page")
    
    
                AppTextField{
                    id: _text
                    anchors.centerIn: parent
                    width: dp(300)
                    height: dp(300)
                }
                AppButton{
                    id: _ssl
                    anchors.top: _text.bottom
                    text: "ssl"
                    onClicked: {
                        test("https://api.lianup.com:7777")
                    }
                }
                AppButton{
                    id: _nossl
                    anchors.top: _ssl.bottom
                    text: "nossl"
                    onClicked: {
                        test("http://api.lianup.com:8888")
                    }
                }
            }
    
    
        }
    
    
        function test(url){
            _text.text += url +"\n";
            HttpRequest
            .get(url)
            .timeout(1000000)
            .send({})
            .then(function(res) {
                _text.text += " OK !";
                console.log("res: " + JSON.stringify(res.body))
    
    
            })
            .catch(function(err){
                _text.text += " bad !" + err.message + err.response;
                console.log("http request err: " + err.message)
                console.log(err.response)
            })
            ;
        }
    }
    
        
    #24472

    Felgo User

    Answer to myself.

    After spending hours and following Alex’s hint.

    it seemed that windows root CA “DST Root CA X3 expired September 29 19:21:40 2021 GMT.” caused problem.

    After deleting this CA it is working now.

    Question still remains is  this a windows issue? or httprequest issue?

    seemed that curl and other etc don’t experience same issue.

Viewing 4 posts - 1 through 4 (of 4 total)

RSS feed for this thread

You must be logged in to reply to this topic.

Qt_Technology_Partner_RGB_475 Qt_Service_Partner_RGB_475_padded