I pointed a subdomain at my site’s ip address but discovered the ip was still being displayed in the browser. I then tried renaming the site from site1.local to the actual subdomain but then I encountered the “Sorry! We will be back soon” page that refused to go away. I’ve tried a lot of suggestions from the forum but none seems to have worked so far
I’ve run bench setup nginx several times followed by sudo service nginx restart but no change yet. I also tried sudo service nginx reload instead of restart but it hasn’t worked either. I’ve checked supervisorctl status and everything seems to be running
Please explain. Where do I find the request host in the access.log file? Where do I find host in the config?
Also, I’m not sure what you’re referring to as (host) in the sites folder
I guess the two instances of mydomain.com originate from renaming site1.local and also creating a second site. Maybe revert site1.local back to original state. If you only use one site, multitenancy should not be required. Only running site1.local should cover all incoming requests.
You mentioned initially a subdomain, so your host is subdomain.yourdomain.com, which resolves to the IP of the ERPNext system? In this case, also the site should be subdomain.yourdomain.com (it must match the full host name).
The host name will be in the log file the requested resource, e.g.
In the above instance, testerp is the local host name. It resolves to the ERPNext server, and there, either multitenancy is off and all sites are replyied to with the site1.local (or default site), or the site that is called testerp. In case your hostname is http://erpnext.mydomain.com, the site needs to be called erpnext.mydomain.com
Your last post gave me some insight into the issue. I went back to the domain account and found it had somehow been reset! I had to update the A records again and after that, it was just a matter of waiting for it to propagate and clearing the cache