ERPNext

One-Click Installation

ERPNext Initialization:

Overview:

This guide will walk you through initializing ERPNext on your AWS instance in just one click. The setup process is streamlined using our custom script, designed for ease of use and efficiency. Before starting the script, ensure the minimum requirement is met.

Pro Tip: We recommend associating an AWS Elastic IP with your instance before running the setup. This prevents your IP address from changing when the instance is stopped and restarted.

 

Step 1: Access Your AWS Instance

1. Launch Your AWS EC2 Instance:

  • Choose your desired AWS EC2 instance type. (Minimum: t3a.small / t3.small)
  • Open ports 22, 80 and 443 in the security group.
  • Once the instance is running, connect to it via SSH.

2. Connect to the Instance:

  • Open your terminal (Mac/Linux) or use an SSH client (e.g., PuTTY for Windows).
  • Run the following SSH command:
ssh ec2-user@<your-aws-public-ip>

3. Run the Initialization Script:

  • To initiate the installation, run the following command:
/usr/local/bin/egl_init.sh.x
  • Note: This script automates the entire installation process. It typically takes about 10 minutes: the application is downloaded, then ERPNext creates its database and your site and installs every bundled app before the site is served. Keep your terminal open and do not close the session until the summary appears. The script generates new credentials for this instance.

Step 2: Instance Set Up and Installation

1. Completion Confirmation:

  • Once the installation is finished, you will see a summary on the screen with your address and your administrator sign-in.
  • Write the password down. It is generated for this instance and is not stored anywhere you can read it back.

Your ERPNext is installed and ready to use.

Your ERPNext: http://<your-public-ip>/

++++++++++++ Administrator sign-in +++++++++++++++++
Username: Administrator
Password: <generated for your instance>

2. Sign in with the USERNAME Administrator

  • Open http://<your-public-ip>/ in your browser.
  • Enter the username Administrator and the password from the summary.

3. Complete the ERPNext setup wizard

Do this before you go any further. After you sign in, ERPNext opens its setup wizard. It asks for your language, country, time zone and currency, then your company name and financial year, and creates your own user account with the email address and password you choose. Your company and currency cannot easily be changed once you have entered transactions, so take a moment to get them right.

  • From then on, sign in as your own user rather than as Administrator.

Before you invite your team

  • Your email account. Search for Email Account in the search bar and add the mailbox ERPNext should send from. This image does not include a mail server, so no invitation, notification or document is emailed until you set this up.
  • HR and Helpdesk. Frappe HR and Frappe Helpdesk are installed and open from the Apps screen. Each has its own settings to review before your staff or your customers use it.
  • Then invite your users: search for User, add each person and give them the roles they need.

Step 3: Add Your Own Domain and SSL

  • ERPNext is served over plain HTTP until you associate a domain. To use your own domain name with a free SSL certificate, run:
sudo /usr/local/bin/egl-setup-domain.sh.x
  • Full instructions are in Associating Your Domain.
  • Do this before your team starts using it. Your ERP holds financial and personal data, and it should not travel over plain HTTP.

 

Important Notes:

  • Mail Sending Restrictions:
    AWS restricts outbound email on port 25 from EC2 instances by default. ERPNext sends through the email account you configure, usually on port 587 or 465, which is not affected.
  • The database is not reachable from the internet.
    MariaDB runs on a private network inside the instance with no published port. Port 3306 does not need to be open and must not be opened.
  • Background jobs run on their own.
    Scheduled tasks, outgoing email and queued work are processed by the workers and the scheduler, which start with the rest of the stack. There is nothing to enable.
  • Do not run the installer a second time.
    Each run generates new passwords, while an existing installation keeps the ones it was created with. If you think something went wrong, email [email protected] rather than running it again.

 

CONTENTS