Unable to access ERPNext from the browser after production deployment
See original GitHub issueDescription of the issue
Unable to access ERPNext from the browser after production deployment.
Context information (for bug reports)
Docker production deployment
Steps to reproduce the issue
-
Follow instructions for production deployment as also specified in this issue 233
-
Run
docker compose up
command. -
Execute
docker-entrypoint.sh new
command in the erpnext_python container.
Observed result
Cannot access ERP from erp.mycompany.com
Expected result
Production deployment is supposed to be complete and ERPNext should be accessible from erp.mycompany.com
Issue Analytics
- State:
- Created 3 years ago
- Comments:6
Top Results From Across the Web
Can't access ERPNext - Deployment
I've installed the ERPNext on my VM CentOS 6.7 on Google Cloud. Whenever I try to access my server with the external IP...
Read more >Unable to connect to erpnext in browser
To fix this issue run the command 'echo madvise > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in ...
Read more >Accessing ERPNext from web browser from a client pc
Hi I am very new to ERPNext and Linux. I have managed to installed ERPNext on my centos server VM. how do it...
Read more >Can't access ERPNext with latest release - Deployment
Hello. I'm currently using ERPNext on Google Cloud Platform, every thing worked fine for me until the latest release. (that's what I think)....
Read more >Installation was Successful, but Can't Open ERPNext
[root@localhost ~]# sudo bash setup_frappe.sh --setup-production Installing for centos 7 amd64 In case you encounter an error, you can po…
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The Readme reads
SITE_NAME: name of the new site to create
, which was unclear to me.But thanks, this fixed it for me. I’ll probably raise a PR to provide more information in the Readme file.
Okay, cool.