Covering OroCommerce topics, B2B eCommerce trends, community updates and company announcements.

This topic contains 7 replies, has 2 voices, and was last updated by  avinogradov 6 days, 2 hours ago.

  • Creator
  • #6181



    I’m trying to generate a WSSE header from my API key using the command line interface.

    When I enter command:

    spg@SPG-ORO: php app/console oro:wsse:generate-header a077[rest of my api key]

    I get back this response:

    Could not open input file: app/console

    I’m running PHP 7.0.18 on Ubuntu 16.04.2. How can I get an WSSE Header?

    Any help is much appreciated. Jorrit

Viewing 7 replies - 1 through 7 (of 7 total)
  • Author
  • #6182



    Can you please specify the folder where you execute the command?

    And also, please, provide the information concerning your environment as described in this topic:

    Please read this before starting a topic with technical question



    Hello Avinogradov,

    Here is my basic information:

    1. Application related information:

    Application Type: OroCommerce
    Application Version: 2.0.0-beta.1
    Application Edition: Community

    2. Environment related information:

    OS, name and version: Ubuntu 16.04.1
    Web server, name and version: Nginx 1.10.3
    Database, name and version: MySQL, 5.7.19

    PHP, version: 7.0.18

    I’ve tried running the command from the ROOT and BIN folders.

    Regards, Jorrit



    “OroCommerce” recently published v1.3. When you say “2.0.0-beta.1” you probably mean “OroPlatform”. can you specify “OroCommerce” version you’re using?

    Basically, command line interface tells you that he does not see the file you’re trying to execute. That means, that you’re either not executing the command from an appropriate folder or the file does not exist for some reason.

    You should be executing this command from root of your project folder – this is where your src/ vendor/ web/ and more importantly app/ folders are. Make sure you’re executing command from an appropriate folder and then take a closer look at your “app/” folder – console.php file should be there. If it’s not, then try reinstalling the whole application or just see what happened to it using git history.




    Based on the package versions I see in the system information I assume it then is OroCommerce 1.1.1

    To be complete here is a screenshot of all ORO packages and their version info:

    Regarding running the command from the correct folder: I’m not familiar with the Linux platform was just able to install ORO using a step-by step manual. I do not know which folder contains the project but I think it’s safe to assume it will be the default folder.

    What would be the default ORO project folder (+ path)?

    Thanks, Jorrit



    Could you post a link to the manual you used?




    The used installation manual is:

    After the installation was completed a few months ago Somebody has been “working” on the server to get integration going. He finally couldn’t get it working but I do not know what he’s been changing in the meanwhile.

    Is there an easy way to check if the required folders and/or content even still exist? (fyi, the front-end website works perfectly fine)

    Regards, Jorrit



    First, you have to understand where the root of your project is. You said that you’re using Nginx. There are nginx configuration files on your linux that tell the server that requesting some domain should execute index.php(for example) in some folder on your machine (the root folder configuration). I cannot know what folder it is exactly, because they are configured customly. There are many manuals as to how to find out where your projects roots are on the internet. This one fox example –

    Most commonly, your nginx configuration files would be in /etc/nginx/nginx.conf, there you must look for the domain you’re opening in your browser and look for “root” configuration – there you will find where your project root and THAT is where you need to execute the command.

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

You must be logged in to reply to this topic.