Admin console locked out

Status
Not open for further replies.

brokertech

SOHO User
Joined
Jan 27, 2023
Messages
4
Reaction score
2
We can no longer access our admin console (not webclient) at the root of our 3CX domain.
I believe it's due to console restrictions.
I've tried tweaking the restricted IPs in the nginx config but so far nothing has worked.
I think there's probably some restricted IPs for console access in the management UI, but I obv can't get in there to change them.

The reason we're now locked out is due to us being forced to shut down the old location we used to VPN from.
We had a VPN and a jump box we used to hop over to 3CX from but that's now gone along with the network it was on.
I didn't get a chance to update 3CX directly but assumed I would be able to adjust the restrictions via SSH and logging into the box directly. Seems I was wrong.

It's currently hosted in an AWS lightsail instance on Debian. I can't run up another instance in the same subnet I don't think, and even if I did I don't know
what the console restricted IPs are so it probably wouldn't work.

I can see a 403 error being returned when clicking Login (POST to /api/login) with any credentials.
I do not get a chance to reset my password which makes me think it's the console restrictions on the IP.

I've looked through the forums and while there are a number of similar questions, nothing has helped me.
I appreciate this is a self-hosted install, but is there any way I can use SSH to see and update the restrictions? Or temporarily remove them so I can get back in and set the correct IPs?

Any suggestions welcome
 
Regarding your question and mentioned issue, we will require you to open a support ticket with 3CX technical support through portal.3cx.com to remove the console restrictions. Firstly though, ensure that you have access to the AWS machine via SSH as the root user before opening a ticket with us, as we will request you provide us with this access for us to be able to assist.

Additionally, revert any changes you have made to the nginx.conf, as this may result in the system needing to be redeployed to a new machine. As any changes made to this section is unsupported and cause unpredictable behavior!
 
  • Like
Reactions: OlegR_3CX
Excellent thanks Charles for such a prompt reply.

SSH as root is possible. I will manually open the firewall for the period of time that support requires access once I've raised the ticket.

I've reverted the tweaks I made to the nginx config. I was only changing the IP addresses in the geo plugin section in my attempts to try to gain access so it shouldn't be otherwise different from the standard install now.

I'll raise the ticket and hopefully tomorrow go through it with technical support. Appreciate your help so far.
 
  • Like
Reactions: Charles_3CX
Just in case anyone reading this thread was wondering, we used a local 3CX partner and they were able to quickly and affordably fix the problem for us. If you have the same issue then rest assured it's not the end of the world. Shout out to Avaio.

Very happy and thanks for your suggestions Charles.
 
  • Like
Reactions: Charles_3CX
Yep probably. I only found that post after we'd got it unlocked so at least next time I should be able to sort it myself.
 
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet