Search results

  1. A

    Web GUI Issues after migrating to new server

    Hello! We migrated from a Debian 9 server to Debian 12. We started with a fresh 12 install and used the install script to setup a fresh copy of FusionPBX. All was working perfectly. We followed the restore process and transferred all the data/configs/DBs from 9 to 12. The server did not...
  2. A

    update

    Just an FYI - I was able to get my issue resolved. My groups table in the database was empty. I had to restore an old backup and manually insert my user-UID,etc. into the database.
  3. A

    update

    Tried doing as you suggested. It updated successfully with no errors. But did not fix the problem. Still get no menu's.
  4. A

    update

    I'm also having a bunch of issues after the latest update. All my menu's have disappeared. I get my login screen, enter my credentials, then it takes me to a screen with a blank dashboard. I followed the steps above to manually upgrade via CLI. Any ideas on how I can fix this??
  5. A

    Multiple "missed call" messages

    +1 for this issue. Experiencing same issue. Sometimes I get 4-5 emails. Also multi-tenant.
  6. A

    Password exposing itself at login

    Hello! We have a freshly install fusionPBX and noticed a small quirk. When we are at the main login screen and enter our admin credentials, click login. The password switches from the privacy dots to plain text and exposes the password. It then accepts the password and logs in fine with no...
  7. A

    Errors after changes, restored fusionpbx DB and now get blank page with <!--{project_path}--> in a lot of the asset URLs

    Thanks for response. I tried running logout.php and it didnt seem to do anything. Also ensured I am using the latest version. Any other ideas to try?
  8. A

    Migrated Fusion to new server - getting <! - {title} -> after restore

    Update: I figured the promox had something to do with it. Somehow going physical to virtual was causing issues. So I got a different physical server and performed the restore. End result was the exact same thing. Showing Title in browser only and identical error logs from nginx. I thought...
  9. A

    Migrated Fusion to new server - getting <! - {title} -> after restore

    I created a fresh container again, Debian V10, privileged (unchecked - unprivileged), enabled Nesting, ran the FusionPBX installation script, had to comment out 3 lines in fusionpbx service for it to start still... ran the restore script from the fusion site... Exact same result. get the title...
  10. A

    Migrated Fusion to new server - getting <! - {title} -> after restore

    Forgive my ignorance - I've never even heard of this. Did some reading and have enabled this as well.
  11. A

    Migrated Fusion to new server - getting <! - {title} -> after restore

    Yes - that option was enabled by default and both my V9 and V10 were set as unprivileged. Should I try a V10 container now with that option disabled?
  12. A

    Migrated Fusion to new server - getting <! - {title} -> after restore

    Just to add to this - Figured it may be something with the different version of debian... So I created a Debian 9 container, copied my same steps, got the same result. Any help would be greatly appreciated :(
  13. A

    Migrated Fusion to new server - getting <! - {title} -> after restore

    Forgot to mention - Below is the error.log file from Nginx 2021/04/18 11:38:51 [error] 274#274: *19 open() "/var/www/fusionpbx/<!--{project_path}-->/resources/bootstrap/js/bootstrap-datetimepicker.min.js" failed (2: No such file or directory), client: 10.242.2.2, server: fusionpbx, request...
  14. A

    Migrated Fusion to new server - getting <! - {title} -> after restore

    Hello! I have fusion installed a on a physical computer running Debian 9.8 and postgres 13. Trying to migrate that server to a proxmox container. Both sides were fully up to date with the latest pull. I setup a Debian 10 minimal image, went through the install script, Freeswitch wouldnt start...
  15. A

    Force outbound caller ID for DISA

    I enabled DISA through my IVR but I found that the original callers name and CID is being forwarded instead of the CID info from the PBX. I don't want to force a blanket outbound CID from the dial plan as some users want their personal names to show up rather than the company name (from the...
  16. A

    Setting up DISA with a DID

    I've been going through the same thing. I figured out that you have to enable it like James said... Then under Dialplan > Destinations set an outbound rule. After that is done you can enable the option through the IVR.