Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. qt.network.ssl: QSslSocket cannot resolve...
Forum Updated to NodeBB v4.3 + New Features

qt.network.ssl: QSslSocket cannot resolve...

Scheduled Pinned Locked Moved Unsolved General and Desktop
16 Posts 4 Posters 10.3k Views 5 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J.HilkJ Offline
    J.HilkJ Offline
    J.Hilk
    Moderators
    wrote on last edited by
    #6

    On the node of OpenSSL I would like to mention, that the QtOnlineInstaller now comes with the option to download the correct/needed openssl dll's no need to search for/compile the correct versions yourself anymore 🎉


    Be aware of the Qt Code of Conduct, when posting : https://forum.qt.io/topic/113070/qt-code-of-conduct


    Q: What's that?
    A: It's blue light.
    Q: What does it do?
    A: It turns blue.

    SPlattenS 1 Reply Last reply
    3
    • J.HilkJ J.Hilk

      On the node of OpenSSL I would like to mention, that the QtOnlineInstaller now comes with the option to download the correct/needed openssl dll's no need to search for/compile the correct versions yourself anymore 🎉

      SPlattenS Offline
      SPlattenS Offline
      SPlatten
      wrote on last edited by
      #7

      @J-Hilk , its very odd, I have two projects, one is a newer version of the original project and that does not come up with these messages. The project I'm working on is the original version and my task is to port it to Qt 5.8.

      I've compared the .pro files and the libraries included are the same, I've also single stepped the source, these messages do not appear until the QML is opened.

      Kind Regards,
      Sy

      J.HilkJ 1 Reply Last reply
      0
      • SPlattenS SPlatten

        @J-Hilk , its very odd, I have two projects, one is a newer version of the original project and that does not come up with these messages. The project I'm working on is the original version and my task is to port it to Qt 5.8.

        I've compared the .pro files and the libraries included are the same, I've also single stepped the source, these messages do not appear until the QML is opened.

        J.HilkJ Offline
        J.HilkJ Offline
        J.Hilk
        Moderators
        wrote on last edited by
        #8

        @SPlatten well QML allows for network access (its well integrated)

        This for example:

        Window {
            id: window
        
            width: 800
            height: 600
        
            visible: true
        
            Image {
                anchors.fill: parent
                source: "https://www.extremetech.com/wp-content/uploads/2020/01/NASA-Sun.jpg"
                fillMode: Image.PreserveAspectFit
            }
        }
        

        works fine and should require openssl support


        Be aware of the Qt Code of Conduct, when posting : https://forum.qt.io/topic/113070/qt-code-of-conduct


        Q: What's that?
        A: It's blue light.
        Q: What does it do?
        A: It turns blue.

        SPlattenS 1 Reply Last reply
        1
        • J.HilkJ J.Hilk

          @SPlatten well QML allows for network access (its well integrated)

          This for example:

          Window {
              id: window
          
              width: 800
              height: 600
          
              visible: true
          
              Image {
                  anchors.fill: parent
                  source: "https://www.extremetech.com/wp-content/uploads/2020/01/NASA-Sun.jpg"
                  fillMode: Image.PreserveAspectFit
              }
          }
          

          works fine and should require openssl support

          SPlattenS Offline
          SPlattenS Offline
          SPlatten
          wrote on last edited by
          #9

          @J-Hilk , there are no http references in the project, images are all from the resource file.

          Kind Regards,
          Sy

          1 Reply Last reply
          0
          • sierdzioS Offline
            sierdzioS Offline
            sierdzio
            Moderators
            wrote on last edited by
            #10

            @SPlatten said in qt.network.ssl: QSslSocket cannot resolve...:

            SSL_set_psk_client_callback

            The missing symbols were added in OpenSSL 1.1.1. Most likely you are still linking OpenSSL 1.1.0 or something.

            (Z(:^

            SPlattenS 1 Reply Last reply
            2
            • sierdzioS sierdzio

              @SPlatten said in qt.network.ssl: QSslSocket cannot resolve...:

              SSL_set_psk_client_callback

              The missing symbols were added in OpenSSL 1.1.1. Most likely you are still linking OpenSSL 1.1.0 or something.

              SPlattenS Offline
              SPlattenS Offline
              SPlatten
              wrote on last edited by
              #11

              @sierdzio , thank you, how or where does that go in the .pro file ?

              Kind Regards,
              Sy

              1 Reply Last reply
              0
              • sierdzioS Offline
                sierdzioS Offline
                sierdzio
                Moderators
                wrote on last edited by
                #12

                Just the regular linking:

                INCLUDEPATH+=/path/to/openssl
                LIBS+=/path/to/openssl
                

                I don't see any openSSL references in the source

                Then, as I mention, you can just ignore these messages. Or disable them using categorizable logging config.

                (Z(:^

                SPlattenS 1 Reply Last reply
                2
                • sierdzioS sierdzio

                  Just the regular linking:

                  INCLUDEPATH+=/path/to/openssl
                  LIBS+=/path/to/openssl
                  

                  I don't see any openSSL references in the source

                  Then, as I mention, you can just ignore these messages. Or disable them using categorizable logging config.

                  SPlattenS Offline
                  SPlattenS Offline
                  SPlatten
                  wrote on last edited by
                  #13

                  @sierdzio can this actually disable runtime messages?

                  Kind Regards,
                  Sy

                  sierdzioS 1 Reply Last reply
                  0
                  • SPlattenS SPlatten

                    @sierdzio can this actually disable runtime messages?

                    sierdzioS Offline
                    sierdzioS Offline
                    sierdzio
                    Moderators
                    wrote on last edited by
                    #14

                    @SPlatten said in qt.network.ssl: QSslSocket cannot resolve...:

                    @sierdzio can this actually disable runtime messages?

                    Yes that's exactly what it's for :-)

                    (Z(:^

                    SPlattenS 1 Reply Last reply
                    0
                    • sierdzioS sierdzio

                      @SPlatten said in qt.network.ssl: QSslSocket cannot resolve...:

                      @sierdzio can this actually disable runtime messages?

                      Yes that's exactly what it's for :-)

                      SPlattenS Offline
                      SPlattenS Offline
                      SPlatten
                      wrote on last edited by
                      #15

                      @sierdzio, thanks, I'll have to read up on how to do it.

                      Kind Regards,
                      Sy

                      1 Reply Last reply
                      0
                      • S Offline
                        S Offline
                        shaan7
                        wrote on last edited by
                        #16

                        @SPlatten if you are on Windows then simply copying libcrypto-1_1.dll and libssl-1_1.dll from the OpenSSL binaries (install them via the Qt Installer) to the path that contains your .exe should fix this as well (without needing to explicitly link at compile time).

                        1 Reply Last reply
                        0

                        • Login

                        • Login or register to search.
                        • First post
                          Last post
                        0
                        • Categories
                        • Recent
                        • Tags
                        • Popular
                        • Users
                        • Groups
                        • Search
                        • Get Qt Extensions
                        • Unsolved