I upgraded my EC2 instance to a larger instance type (with 2 gigs of RAM) and installed again and everything works fine.
The minimum required RAM is 2GB for ERPNext.
I upgraded my EC2 instance to a larger instance type (with 2 gigs of RAM) and installed again and everything works fine.
The minimum required RAM is 2GB for ERPNext.
Thanks Lawes. Its worked me
Itâs Work for me.
it Means User not rightâs to access some fileâŚlike css
Finally i fix the display problem after run production site.
So it just need to change the permission for the installation directory. On my case, I run this command in :~/frappe-bench$
directory. So go to cd ~/home/[youraccount]/frappe-bench
then run:
sudo chmod o+x /home/[your-account-profile]/
eg: sudo chmod o+x /home/admin
The problem is, some answer on the other thread did not explain this properly, so newcomer like me canât understand
I had similar issue. On my cicd I havd 5 migaes from deployments and the assetsfrom the first one was being requsted by the browser, despite the running container had the latest in assets.json.
eg: container assets.json: âlogin.bundle.cssâ: â/assets/frappe/dist/css/login.bundle.BNLXGCOL.cssâ
broser was trying to fetch login.bundle.VNLPGCOL.css.
The possible issue with my environmnet was the Redis cache holding old stale outdated assets.json data.
Running these commands solved the issue:
docker exec -it redis-cli FLUSHALL
docker exec -it redis-cli FLUSHALL