FTD removed from FMC but can't login on FDM

[s.balon]

I had a FTD Virtual register to a FMC which I need to remove and manage as a standalone device.

I delete the device from the FMC.

I setup the FTD to be used as standalone as per CLI command : "configure manager local"

the GUI is working and I can browse the page via https but can't login to it.

I have the "admin" account on SSH (cli access) working

I create a new local account on SSH with config level and it's also working 

but neither the default admin password, the current ssh admin password or the new local user is able to connect to the FDM GUI.

the error message displayed on the page is : "Unable to authorize access.If you continue to have difficulty accessing this device, please contact the system administrator."

it's running : 

Cisco Firepower Extensible Operating System (FX-OS) v2.10.1 (build 1603)
Cisco Firepower Threat Defense for VMware v7.0.6 (build 236)

any idea  how to enable FDM access ?

is the SSH CLI admin account have the same password as the FDM GUI admin account ?

should I reset or change the SSH CLI admin password ?

Thanks for your comment.

[Sheraz.Salim]

Try reloading the FTD and if still not slove the problem. login in via ssh go to expert mode with sudo -su and give this command "root@FP-fw:/home/admin# pmtool status | grep -i waiting"and past your results

[MHM Cisco World]

Try use 

Username Admin 

Password Admin123

MHM

[s.balon · Accepted solution]

Username Admin is not working either.

I can't use the requested command by Sheraz

root@FTDv:~# root@FP-fw:/home/admin# pmtool status | grep -i waiting
-sh: root@FP-fw:/home/admin#: No such file or directory
root@FTDv:~# /home/admin# pmtool status | grep -i waiting
-sh: /home/admin#: No such file or directory

but I get a working solution from our Cisco Technical support 

On the FTD CLI please run the following commands:

> expert

$ sudo su (Enter Password)

# usertool.pl -p 'admin PASSWORD' (Where PASSWORD is the password you want to use for GUI access)

that solve my issue, I have now access back