Locked out of GUI

[Kenny Riley]

Hello

I recently installed FusionPBX in AWS.. I assigned it an elastic IP, essentially changing it's public IP address and now my credentials are failing at the login screen for the GUI. Why is this happening? What can I do to regain access?

 

[DigitalDaz]

@Kenny Riley use username@theoriginalinstallip

 

[Kenny Riley]

@Kenny Riley use username@theoriginalinstallip

I'm not sure I can find that information since I've assigned an elastic IP in AWS, I will do my best though.

 

[Kenny Riley]

Ok I got in, thank you Daz! Do I need to change my username or always log in this way moving forward? Do I need to update my IP in the GUI to correct this?

 

[DigitalDaz]

@Kenny Riley In a linux command prompt:

ls /var/lib/freeswitch/recordings

You should have a folder named the original IP

 

[DigitalDaz]

Yes, you can rename it in the gui, best way is to map a domain to it, better for security anyway, then create a domain and within that domain, create a superadmin account.

 

[Kenny Riley]

Yes, you can rename it in the gui, best way is to map a domain to it, better for security anyway, then create a domain and within that domain, create a superadmin account.

Ok this makes perfect sense since it's an MT solution. Thank you so much for your prompt response, I really do appreciate it!

 

[DigitalDaz]

Basically whatever you have in URL bar it tags on in the background

so http://10.10.10.10 and login with admin sends admin@10.10.10.10

By mapping a domain in with DNS you can always log in with admin

By of course http://bloggs.com

 

[DigitalDaz]

I haven't explained that very well where I was just trying to get you in quickly but I think you have the gist

 

[Kenny Riley]

I haven't explained that very well where I was just trying to get you in quickly but I think you have the gist

Makes perfect sense Daz, thank you so much!

 

[Soleo InfoServ]

So just to clarify....If I build my FusionPBX on 192.168.1.10 and then move into production and change the underlying server's IP to 10.10.10.10, when i try to login it doesn't allow and if I do the password reset I end up with a blank environment......but if I login as user@192.168.1.10 all my database info, extensions, basically everything I've built prior in the 192,168 land will come back?

 

[Kenny Riley]

Hi Soleo

The IP doesn't matter when it comes to login credentials, the default domain name that you configure when you first initially set up FPBX is what matters.

If you initially set up your default domain name as 192.168.1.10, and change your default domain name to 10.10.10.10 instead, you will navigate to the IP of your FPX and login as admin@192.168.1.10 -- Make sense?

 

[Soleo InfoServ]

It does! however, I'm not changing my domain name but the IP of the Centos server that I have FusionPBX/FreeSwitch installed on.....Is that just changing the domain but using different words to mean the same thing?

Thanks!!!

 

[Kenny Riley]

Your IP address and domains are different, however, they can be the same if you configure your default domain as your IP (I did this..)

If you change your IP of your actual server, that doesn't affect your login per say. Just ensure you are logging in with the following format: admin@ORIGINALDOMAIN or in your case: admin@192.168.1.10 (I'm assuming you set the domain as your IP when you initially set up Fusion).

 

[Soleo InfoServ]

Lightbulb! Thx!!