Try ERPNext Buy Support Partners Foundation Foundation Members

Installation was Successful, but Can't Open ERPNext

Here’s the log for the installation. It appears to be very clean and successful.

[root@localhost ~]# sudo bash setup_frappe.sh --setup-production
Installing for centos 7 amd64
In case you encounter an error, you can post on https://discuss.frappe.io

Adding centos mariadb repo
Installing packages for centos. This might take time…
Installing wkhtmltopdf
Configuring CentOS services
Starting services
Adding frappe user
Installing frappe-bench
Setting up first site

Frappe/ERPNext is installed successfully and is running on port 80.
Frappe password: VEgxXRyxxPsdmClD
MariaDB root password: WXd6BtkOBphm9O7q
Administrator password: w5d3pRJL2SBhEpek

The passwords are also stored at ~/frappe_passwords.txt
You can remove this file after making a note of the passwords.

But when I try to access http://localhost:80, here’s what I got:

Unable to connect

Firefox can’t establish a connection to the server at localhost.

The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.

Any help is greatly appreciated.

@nanto_himawan, Just try with http://localhost or http://site_name

Same thing. Doesn’t work. But thanx for the suggestions.

Check nginx status /etc/init.d/nginx status or service nginx status.
If its not running , run nginx -t.

  • From the shell on the server, see if curl -I localhost, if this works you mighat have an issue with the firewall
  • If the curl doesn’t work then post the results of
sudo service nginx status
sudo supervisorctl status

Thank you guys for all the replies. It turns out that nginx was running, but not listening on any port. After some troubleshooting and googling, I found out the cause was this:

Description of problem:
SELinux is preventing /usr/sbin/nginx from ‘search’ accesses …

And I have to do
setsebool -P httpd_enable_homedirs 1

It’s working now.

Great, this SELinux policy works for us,