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. QNAM issues with https + openSSL
Forum Updated to NodeBB v4.3 + New Features

QNAM issues with https + openSSL

Scheduled Pinned Locked Moved General and Desktop
4 Posts 2 Posters 2.3k Views 1 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.
  • C Offline
    C Offline
    cp133
    wrote on last edited by
    #1

    When using QNAM, when I try to post data to a https, I get the following issue in console:
    [code]
    QSslSocket: cannot call unresolved functionSSLv23_client_method
    QSslSocket: cannot call unresolved function SSL_CTX_new
    QSslSocket: cannot call unresolved function SSL_library_init
    QSslSocket: cannot call unresolved function ERR_get_error
    [/code]

    Now, some googling has lead me to this thread:
    http://codeblog.vurdalakov.net/2009/11/solution-qsslsocket-cannot-call.html

    Now, I downloaded openSSL, and I moved ssleay32.dll and libeay32.dll into my execution folder, and I also put it in my environmental path:

    !http://i.imgur.com/nTj97.png(Environmental path)!

    However, when I try to post data to https, I still have the errors printed into console.

    I have the full installation, version 4.8.0

    Can anybody help me?

    1 Reply Last reply
    0
    • G Offline
      G Offline
      goetz
      wrote on last edited by
      #2

      Is that really 32bit? OpenSSL-Win64 sounds like 64bit...

      http://www.catb.org/~esr/faqs/smart-questions.html

      1 Reply Last reply
      0
      • C Offline
        C Offline
        cp133
        wrote on last edited by
        #3

        Does it have to be 32 bit? And I think the ssleay32 and libeay32 are the same regardless of #of bits

        1 Reply Last reply
        0
        • G Offline
          G Offline
          goetz
          wrote on last edited by
          #4

          Of course, it must be 32bit if your application is 32 bit too. One cannot mix 32bit and 64bit code within one running application. You should double check whether the DLLs are really 32bit. I wouldn't be surprised if they are 64bit and just carry the 32 in the name for historical reasons. OpenSSL is a bit, let's say weird, regarding their naming scheme(s).

          http://www.catb.org/~esr/faqs/smart-questions.html

          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