FOP2 Community Forum

If you saw the login script, and entered login credentials but from there it failed, then please follow the troubleshooter I posted. Another mistake I see usually is that people copy files to the web directory, but not its subdirectories, in that case the application will be completely broken. If possible you must move the html directory that comes in the tarball as it has all subdirectories and correct permissions for files and directories. I do not want to type again all what it says in the troubleshooter and that I wrote countless of times in this forum, you can experience issues connecting for several reasons, fop2 server not started, port 4445 blocked, or perhaps it is not that issue but just bad credentials (in the later case, you will be prompted again for exten/pass).

Uninstalling fop2admin should not interfere at all with Freepbx after the uninstallation. If files are removed, there is nothing that could affect FreePBX. So, I have no idea what is wrong in your setup. It is quite simple, if a module is NOT present, it cannot break FreePBX as the module itself is not loaded, there are no files, no hooks, no callbacks, etc. So what you say it does not make any sense to me. If in doubt, remove the module directory by hand, usually in /var/www/html/admin/modules/fop2admin , just remove the whole directory. fop2 and fop2admin are non intrusive in its nature. I think you have some other kind of problem.