I disagree. When ERPNext claims to be a professional product, A SAP alternative that is what people expect. People are trying to run their business on it, you cannot release it with 1000 open bugs and a failing CI build.
1 Like
Have you resolved the second error?
I just fixed it. Some developer will tell if it’s the right way
sudo systemctl start supervisor
sudo systemctl enable supervisor
sudo bench setup production <your-user>
sudo reboot
cd <frappe-bench directory>
bench update
1 Like
Released a patch version for frappe & erpnext, to fix the patching related issues.
3 Likes
Retail Module is not visible in User doctype. After Migrating from V12 to V13, we cannot allow the Retail module to an existing user.
The Domain 
is already visible for an existing System Manager. Even if we make an existing user a System Manager this user does not have access to the said Domain.
However, when creating a new it allows access to Retail Domain automatically.
Please see below the Retail Module is not visible in the User doctype.
Please let me know what to do as I need to allow users to assess the POS.
Thank you.
Skip Failing is not recommended, it might cause some other problems in the future or instantlly.
13.0.2 is available, it might help.
1 Like
No it does not seem to be solving the issue. I am still facing the same issue on bench update --patch.
1 Like
Looks like these issues are already fixed as part of patch Release Release v13.0.2 · frappe/frappe · GitHub
For other issues you can log into Issues · frappe/erpnext · GitHub
1 Like
Thanks @Majid_Ejaz
Couple of my sites went through. I will try over the weekend with the patch for the failed ones.
Will try this over the weekend.
Wawo! This new UI is Awsome. Really loved the main dashboard customizations hopefully they will be supported in the future version and will be made even better.
One thing I’m struggling with is ERPNext support for the ‘Production’, ‘IT’, and ‘Admin’ departments. Are there any specific modules and doctypes related to these departments.
ERPNext version 13 randomly crashing website (server is up)…
“This sitecan’t be reached”
ERR_CONNECTION_TIMED_OUT
sudo supervisorctl status
frappe-bench-redis:frappe-bench-redis-cache RUNNING pid 1079, uptime 0:54:29
frappe-bench-redis:frappe-bench-redis-queue RUNNING pid 1080, uptime 0:54:29
frappe-bench-redis:frappe-bench-redis-socketio RUNNING pid 1083, uptime 0:54:29
frappe-bench-web:frappe-bench-frappe-web RUNNING pid 1086, uptime 0:54:29
frappe-bench-web:frappe-bench-node-socketio RUNNING pid 1089, uptime 0:54:29
frappe-bench-workers:frappe-bench-frappe-default-worker-0 RUNNING pid 1099, uptime 0:54:29
frappe-bench-workers:frappe-bench-frappe-long-worker-0 RUNNING pid 1106, uptime 0:54:29
frappe-bench-workers:frappe-bench-frappe-schedule RUNNING pid 1096, uptime 0:54:29
frappe-bench-workers:frappe-bench-frappe-short-worker-0 RUNNING pid 1100, uptime 0:54:29
sudo supervisorctl restart all
restarts services, but does not fix issue.
a few minutes later… site comes back up for no reason.
Nothing in nginx access/error logs.
On the first attempt to upgrade from v12 to v13, after bench update --patch threw error 'User' object has no attribute 'module_profile'. I couldn’t find a way to fix it, so decided to reinstall and restore backup.
Finally v13! Thank you! Great work! Congratulations!!!
But… “Frapé” like iced coffe? I’ve been founding some strange translations to Spanish.
Try specifically node v10. I think that was what solved it for me.
Hi,
I tried after updating, but I am still facing the same error when I run bench update --patch. Need help.
I was trying to upgrade from v 12.9 to v13.
I first run the command
bench switch-to-branch version-13 frappe erpnext --upgrade
then I tried running
bench update --patch
and I am getting the above error
Thanks
Advanced Payment from Journal Entry (Opening Balance) can’t be offset from
Sales Invoice
Payment Reconciliation
before updated, “Allocate Advances Automatically (FIFO)” and “Payment Reconciliation” are working
1 Like
That sounds like an issue with the fail2ban configuration. You can just validate that, if the site is still available from a device with a different IP address.
Many thanks gsarunk,
Kind regards from Spain,
Alb
1 Like