Hosts of a deleted user break the host lists

This error message happens when deleting a user which created hosts. “Cannot read property ‘avatar’ of null”

Are you in the right place? - I hope so, if not sorry.

• If you are looking for support on how to get your upstream server forwarding, please consider asking the community on Reddit.

• If you are writing code changes to contribute and need to ask about the internals of the software, Gitter is the best place to ask.

• If you think you found a bug with NPM (not Nginx, or your upstream server or MySql) then you are in the right place.

Checklist

• Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image? - No
• Are you sure you’re not using someone else’s docker image? - Yes
• If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network? - No

Describe the bug

• Cannot read property ‘avatar’ of null when deleting a user and going back to created hosts
• What version of Nginx Proxy Manager is reported on the login page? - v2.8.1

To Reproduce Steps to reproduce the behavior:

• Create a new user
• Create a new redirection host
• Delete user
• End up seeing “Cannot read property ‘avatar’ of null” where new redirection host should be

Expected behavior Got error when deleting user to a created redirection host, not sure what I should be seeing but it’s broken I think.

Screenshots Screenshots attached.

Operating System

• Ubuntu 20.10

Additional context Docker Engine - 20.10.6

[MichelBaie]

I think you should reopen this issue because it need to be fixed by the developpers. I’ve did the same error as deleting users with existing hosts.

[aab12345]

looks like I fixed it by doing the following;

Installed DB Browser SQLite (Windows) Going to /srv/dev-disk-by-label-Files/Config/Nginx-Proxy Open the database.sqlite with DB Browser SQLite Browsing the Data > Table user Modifying Is_Deleted=0 Go to > redirection host table > delete line 1 > Save Then file > write changes > Stopped the container Copied over edited database back to /srv/dev-disk-by-label-Files/Config/Nginx-Proxy Restarted the service > Bingo!

No more error and the users are back. I couldn’t find how to connect to the sql via docker but this way seemed to work so not sure if this is still a bug when deleting a user. Still might need looking into though but this above works.