- 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
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