By default, the production image is usable on port 8080
. We checked the…
erp/config/nginx.conf
…file wherein the port set to listen to is 80
. But, why do we need to access the ERP on
localhost:8080
Shouldn’t it just be localhost
?
By default, the production image is usable on port 8080
. We checked the…
erp/config/nginx.conf
…file wherein the port set to listen to is 80
. But, why do we need to access the ERP on
localhost:8080
Shouldn’t it just be localhost
?
It is unclear what your long term intention is.
But a quick sanity check. Are you sure NGinx references the file erp/config/nginx.conf
?
Check the last lines of /etc/nginx/nginx.conf
. You ought to see:
include /etc/nginx/conf.d/*.conf;
Then look for a symlink in /etc/nginx/conf.d/
. You ought to see:
lrwxrwxrwx 1 root root 44 Feb 21 14:36 frappe-bench.conf -> /home/erpnext/frappe-bench/config/nginx.conf
If that chain is incomplete NGinx never sees the port 80 setting.
If you want eventually for remote users to access the VM you’ll need to look at something like How to Forward Ports to a Virtual Machine and Use It as a Server.
To do that you’ll want to expose ERPNext via port 443 not 80. If so, refer to Frappe Framework : Configuring HTTPS.
@MartinHBramwell
Thank you for your response.
Our intention is to access the ERP without the need to specify the port 8080
which is the case as I type it.
Since the web runs on port 80, 443
, the browser does not need any port to be explicitly mentioned in the URL for accessing the ERP. This simplifies the URL for the layman.