Fresh install from Git, v15. Everything default except I’ve renamed the default admin user, but everything else is working. I go into payment entry to create a new one and this pops up:
And nothing is available under Party Type, however if I go into doctypes supplier is there:
Hi,
I have a ERPNext: v15.51.0 (version-15). Frappe Framework, v15.55.1 (version-15) with
Payments: v0.0.1 (develop) and it seems to be working ok. Perhaps try the Permission Inspector , Roles and Permissions for the new name and see if they look right.
Looks like it yeah:
I did change the username from Administrator to my name, login works fine and all, no issues there.
Tried creating a new user giving all permissions, just to test, same thing, so its not the user.
Anyone got any ideas why its doing this?
Try reinstalling and see if the problem exists without changing the default admin name to see if that is indeed the cause of the problem?
Did you use the easy-install script from git?
No sorry not git, I did a docker install sorry. The issue is I setup all my accounts and everything already, hours of work.
I installed according to the git page, did a clone, then docker compose per instructions.
Do you mean you’ve renamed Administrator? Or the first user account you created on setup?
Renamed Administrator. That being said, I’ve tried creating a new user giving all permissions and it still gives same issue. Will changing admin back work?
Renaming Administrator is definitely going to break stuff in exactly the kind of way you’re seeing here. I’m surprised it was even possible. I thought there were guardrails to prevent that.
Wow, I cant believe in 2025 there is a system this large that is hardcoded to a single admin username, wow. Will renaming it back do anything at all?
The Administrator account is not intended to be used for much beyond initial setup. Like I said, I’m surprised it let you change the name without issuing warnings.
Will it work if you change it back? Hopefully! Though it’s possible that other things are now broken too, as a result of the Administrator not being present.
No, didn’t do anything. Changed it back, created new user, logged in as new user. No dice.
Hmm, it’s unfortunately hard to say then. Self-hosting can be a bit of a minefield, especially with caching and application version mismatches.
If it were me, my next step would probably be to try loading the site backup into Frappe Cloud to see if it’s working there on a known good installation.
Didn’t work, brought back the issues. But I think I figured out what happened and when. When I first installed it and ran the page the first time, it took forward, gave me a couple invalid or server errors, then finally worked. I forgot to wait 5 minutes after first starting to bring it up, for site create to work. Finally when it did come up I logged in as Administrator, and it went straight in, never gave me the option to create a new user or setup system. This is my second install, I remember originally it doing that. I thought it was strange but didn’t think much of it.
Seems me trying to go in too early botched the site-creation. So I deleted everything and did it again, this time waiting the 5 minutes and everything worked.
There really needs to be something in the installer to stop someone going early to things from botching it, makes no sense. But that’s what happened.
I had to re-create everything but it works now. Thanks!
Glad it’s working for you! I’ve never encountered needing to wait five minutes, but errors on setup are definitely a hazard.
It’s a lot better than it used to be, but if I run into server errors on first run I usually just dump the site and start a new one. The system doesn’t always recover fully from incorrect installation steps.