How to Fix 'OpenSSL is Not Recognized as an Internal or External Command' Error

How can I resolve the 'OpenSSL is not recognized as an internal or external command' error when trying to generate an application signature?

The error 'OpenSSL is not recognized as an internal or external command' usually arises when the OpenSSL executable is not installed or its installation path is not included in the system's PATH environment variable. This guide will help you install OpenSSL and set up your environment correctly to avoid this error while generating your application signature for Facebook integration.

# To verify OpenSSL installation, use this command in the terminal:
openssl version

# Ensure it returns the version number of OpenSSL installed.

Causes

• OpenSSL is not installed on your system.
• The path to OpenSSL is not included in your system's PATH environment variable.
• You are using a Windows command prompt without administrative privileges.

Solutions

• Install OpenSSL by downloading it from the official site or a trusted repository based on your operating system (e.g., Windows, macOS, Linux).
• After installing OpenSSL, find the installation directory and copy the path (e.g., C:\OpenSSL-Win64\bin).
• Add the OpenSSL installation path to the PATH environment variable: 1. For Windows, follow these steps: - Right-click on 'This PC' or 'Computer' and select 'Properties'. - Click on 'Advanced system settings'. - Click on 'Environment Variables'. - In the System Variables section, find the variable named 'Path', select it, and click 'Edit'. - Add the copied OpenSSL path to the list. Ensure to separate it from existing entries with a semicolon. - Click 'OK' to save changes. 2. Open a new command prompt to verify that the changes have taken effect by typing 'openssl version'.
• Restart your command prompt after making the above changes to apply the new PATH settings.

Mistake: Not restarting the command prompt after changing environment variables.

Solution: Always open a new command prompt to see if the changes take effect.

Mistake: Installing OpenSSL but forgetting to link the executable path to PATH.

Solution: Make sure the OpenSSL executable directory is correctly added to your PATH environment variable.