I am getting an issue with console restrictions where some IP addresses in Console restrictions work, and at least one doesn't.
See this list:
It seems like a bug. I have verified with numerous "what's my IP address" sites that from my home computer and they report exactly that IP#2 address. And it used to work, up until only recently (within the last week).
Why so many IPs you might ask? It's mostly the primary and backup WAN links of our sites, plus the reseller has a couple of IPs, plus I have my home WAN IP. I would dearly love to be able to add comments to these!
I've tried rebooting the PBX, and tried different browsers, but still same result.
And for those with eagle eyes, that 159.x.x.0 address without the subnet mask is not a typo. We have a 157.x.x.0 PPPoE host IP assigned off a /22. Yes I felt dirty when I saw that I'd been assigned a .0 host address, but technically it is legit - it's neither subnet nor directed broadcast. Just mentioning it though in case it is borking the parsing of this list somehow. It's probably a red herring as that IP#2 was working fine until recently.
I could try and re-add the IP#2 that is not working, but I thought if a 3CX Engineer wants some logs I could provide to help diagnose first. Any assistance would be greatly appreciated. It's really worrying being locked out of one's own system!
Thanks,
Gavin O
EDIT: OK so after I successfully logged in via one of the work servers and logged out again, I tried again from home again (IP#2), and to my surprise - it worked!
I am not sure if the home ISP is to blame. The home ISP is Foxtel Broadband (Australia) as I bundle it with some Pay TV. I asked CoPilot if Foxtel Australia use CGNAT and it wasn't sure. ISPs tend not to advertise these things. I have hammered a lot of "what's my IP sites" and they are all saying the same thing (IP#2) so not sure what's going on here. Pretty concerning that I couldn't get access to the Admin Console for a period of time when seemingly nothing had changed.
See this list:
- When I log into my PBX using the work/office IP address of 27.x.x.66 - I have access to the Admin Console. Let's call this IP#1.
- When I log into my PBX using the home IP address of 1.x.x.62 - I do not have access to the Admin Console. Let's call this IP#2.
It seems like a bug. I have verified with numerous "what's my IP address" sites that from my home computer and they report exactly that IP#2 address. And it used to work, up until only recently (within the last week).
Why so many IPs you might ask? It's mostly the primary and backup WAN links of our sites, plus the reseller has a couple of IPs, plus I have my home WAN IP. I would dearly love to be able to add comments to these!
I've tried rebooting the PBX, and tried different browsers, but still same result.
And for those with eagle eyes, that 159.x.x.0 address without the subnet mask is not a typo. We have a 157.x.x.0 PPPoE host IP assigned off a /22. Yes I felt dirty when I saw that I'd been assigned a .0 host address, but technically it is legit - it's neither subnet nor directed broadcast. Just mentioning it though in case it is borking the parsing of this list somehow. It's probably a red herring as that IP#2 was working fine until recently.
I could try and re-add the IP#2 that is not working, but I thought if a 3CX Engineer wants some logs I could provide to help diagnose first. Any assistance would be greatly appreciated. It's really worrying being locked out of one's own system!
Thanks,
Gavin O
EDIT: OK so after I successfully logged in via one of the work servers and logged out again, I tried again from home again (IP#2), and to my surprise - it worked!
I am not sure if the home ISP is to blame. The home ISP is Foxtel Broadband (Australia) as I bundle it with some Pay TV. I asked CoPilot if Foxtel Australia use CGNAT and it wasn't sure. ISPs tend not to advertise these things. I have hammered a lot of "what's my IP sites" and they are all saying the same thing (IP#2) so not sure what's going on here. Pretty concerning that I couldn't get access to the Admin Console for a period of time when seemingly nothing had changed.
Last edited:
