Title: Got a Solution to OpenSSl error
Last modified: August 22, 2016

---

# Got a Solution to OpenSSl error

 *  Resolved [HgtuRgg](https://wordpress.org/support/users/kalyanbratadas/)
 * (@kalyanbratadas)
 * [11 years, 9 months ago](https://wordpress.org/support/topic/got-a-solution-to-openssl-error/)
 * Hi,
 * Just now I got a solution to that upload error. Hope all finds this useful. Let
   me know.
 * Assuming that you have done all the things mentioned in the documentation –
 * STEP 1 : Look at the Service Account column (Projects>API Project>Credentials
   >Service Account
 * STEP 2 : Find this **PUBLIC KEY FINGERPRINTS**. Copy the key.
 * STEP 3 : Go inside your cPanel file manager and locate the **.p12** file (_it
   should read like **API Project-88c96113d7123.p12**_
 * STEP 4 : Click on **Rename **and rename the file inside your file manager (from**
   API Project-88c96113d7123.p12** to **87490071f38ed496f0679ce8898750b612e719c4-
   privatekey.p12**)
 * Now you get the path to this like [http://yourdomain.com/87490071f38ed496f0679ce8898750b612e719c4-privatekey.p12](http://yourdomain.com/87490071f38ed496f0679ce8898750b612e719c4-privatekey.p12)
 * STEP 5: Upload the path to the **Private Key Url Path** inside Settings of the
   plugin.
 * Hope this works.
 * PS: _Not sure but I also enabled Drive SDK services apart from the Drive API.
   Not sure whether it has any effect or not._
 * PS1 : _Request the author and/or moderator to check this and if found useful,
   you can pin this thread at the top so that others can be benefited from this._
 * [https://wordpress.org/plugins/google-drive-wp-media/](https://wordpress.org/plugins/google-drive-wp-media/)

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

 *  [Anthony Tilke](https://wordpress.org/support/users/iwritten/)
 * (@iwritten)
 * [11 years, 8 months ago](https://wordpress.org/support/topic/got-a-solution-to-openssl-error/#post-5260151)
 * Thanks Kalyan. I had this problem and your solution worked!
 *  Thread Starter [HgtuRgg](https://wordpress.org/support/users/kalyanbratadas/)
 * (@kalyanbratadas)
 * [11 years, 7 months ago](https://wordpress.org/support/topic/got-a-solution-to-openssl-error/#post-5260153)
 * You’re welcome **[@iwritten](https://wordpress.org/support/users/iwritten/)**
 *  [arniarni](https://wordpress.org/support/users/arniarni/)
 * (@arniarni)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/got-a-solution-to-openssl-error/#post-5260167)
 * Hi,
    By my experience with this settings one week ago I found another solution
   for F12 bug. You can rename F12-file to any filename without space and underline
   characters inside filename. For example you can only delete this characters from
   filename. And after renaming insert this filename to plugin settings. So, the
   f12-file can have any name.
 *  [wsj101](https://wordpress.org/support/users/wsj101/)
 * (@wsj101)
 * [11 years, 5 months ago](https://wordpress.org/support/topic/got-a-solution-to-openssl-error/#post-5260168)
 * Yes, that’s it. Just remove the space from the file name in your website directory
   and put the same name in the Google Drive WP Media settings.

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

The topic ‘Got a Solution to OpenSSl error’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/google-drive-wp-media_d5d5d4.svg)
 * [Google Drive WP Media](https://wordpress.org/plugins/google-drive-wp-media/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/google-drive-wp-media/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/google-drive-wp-media/)
 * [Active Topics](https://wordpress.org/support/plugin/google-drive-wp-media/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/google-drive-wp-media/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/google-drive-wp-media/reviews/)

 * 4 replies
 * 4 participants
 * Last reply from: [wsj101](https://wordpress.org/support/users/wsj101/)
 * Last activity: [11 years, 5 months ago](https://wordpress.org/support/topic/got-a-solution-to-openssl-error/#post-5260168)
 * Status: resolved