The most common reason for this to happen is after you suspend the EC2 instance and restart it again. What happens is that during suspend/restart, the IP address is changed. FusionPBX creates its default domain with the first public IP address when it starts. See some more explanations at https://stackoverflow.com/questions/396 ... ess-change
You can use "admin@<original ip>" to login. However, user extension calls will not work anymore, since there is no domain for the current IP address
To solve this cleanly, one should use an elastic IP address (i.e. fixed IP address) for the primary network interface. Alternatively, one can also use DDNS (dynamic DNS), in which case you need to create an additional domain that corresponds to the DNS name and only create users in the DDNS domain.
If you are able to log into the server with your SSH key, you can also run the following the script to check whether the default domain/user/password are in a sane state.
http://netspectrum.com/freeswitch/check-password.sh
FusionPBX - I cannot log in again?
Who is online
Users browsing this forum: No registered users and 0 guests