Error: An IP has been blacklisted

LOG.JEST

SMB User
Basic Certified
Joined
Mar 22, 2025
Messages
8
Reaction score
1
I received this message when I tried to log into my system, but I can not log onto my system to check the IP blacklist. Is there any way around this?
 
@LOG.JEST

If you can not log in to the 3CX, the problem is you or someone on your LAN.

What you need to do, is change your WAN IP address, how?
-move to another WIFI place
-Set your laptop on the hotspot of your phone
-Go to shop with free WIFI
-use browser on phone while on 4G/5G
-Use Opera or Brave with incognito with VPN
-Use some VPN to anywhere

Whatever you do, as long as you have another WAN IP, you should be able to log in to the 3CX again. (with the correct details)
Last resort... wait until the blacklist is free again (can take some time).
 
I can not log onto my system to check the IP blacklist. Is there any way around this?
This the SMB forum so the Free version, correct? You can’t access the blacklist on Free as that’s a server level setting. Aside from the above you can open a support ticket or wait 24h from the last failure for it to expire. Also you might turn off or reset any physical phones you’ve tried to set up, and/or update it’s firmware.
 
This the SMB forum so the Free version, correct? You can’t access the blacklist on Free as that’s a server level setting. Aside from the above you can open a support ticket or wait 24h from the last failure for it to expire. Also you might turn off or reset any physical phones you’ve tried to set up, and/or update it’s firmware.
Thanks for the reply. I did notice I could not access the blacklist from from the free version, so I guess I'm stuck there. It has been well over 24 hours in between attempts, sometimes days and even more than a week, so now I'm trying, as you mentioned to reset everything, and get an IP change from my ISP. Also changing the IP on my computer. Thankfully I have been able to access things from other computers and phones so far. It is just my home system, where I most need to access it that is causing problems.
 
If it hasn't expired then something is still triggering the block...an app, a phone, something.
 
We, too, have Free SMB and got blacklisted. It happened after we provisioned a T53W phone. It appears to have taken its provisioning, as the display now has the assigned text but will not register. This process then blacklisted our IP. The firmware 98.86.0.75. ?
 
96.87 can only be upgraded through 3CX per 3CX posts. Change that URL to a previous version like (IIRC) 96.86.0.81 and try.

But yes if a phone is too old a version particularly making it a router phone can cause this.
 
  • Like
Reactions: Evolute IT
Hi Steve,

Thank you for your reply.

I investigated this firmware upgrade issue for Yealink T5xW phones from V86 to V87 and there is a problem.

As per Yealink Support pages, when using the phone's web gui to upgrade from V86 to V87, you MUST perform an intermediate firmware step as detailed below.

We followed this procedure and was able to successfully upgrade to the required 3CX version.

Thanks,
Lance


Conclusion

The older V86 firmware has a different firmware verification process when using the WebUI to upgrade, which causes this issue when directly upgrading to V87 via WebUI.

To solve this

This problem does not exist when using the Auto Provision method to upgrade V86 to V87. So you can try using Auto Provision to upgrade firmware.
If you need to upgrade via the web user interface, please try to upgrade to the interim firmware below first:
After that, you would be able to upgrade to V87 via the web user interface.
 
  • Like
Reactions: Evolute IT
Hi Steve,

Thank you for your reply.

I investigated this firmware upgrade issue for Yealink T5xW phones from V86 to V87 and there is a problem.

As per Yealink Support pages, when using the phone's web gui to upgrade from V86 to V87, you MUST perform an intermediate firmware step as detailed below.

We followed this procedure and was able to successfully upgrade to the required 3CX version.

Thanks,
Lance


Conclusion

The older V86 firmware has a different firmware verification process when using the WebUI to upgrade, which causes this issue when directly upgrading to V87 via WebUI.

To solve this

This problem does not exist when using the Auto Provision method to upgrade V86 to V87. So you can try using Auto Provision to upgrade firmware.
If you need to upgrade via the web user interface, please try to upgrade to the interim firmware below first:

After that, you would be able to upgrade to V87 via the web user interface.
@N_G can this be pinned somewhere? I had a similar issue recently and didn't know why. This makes sense.
 

Members Online Now

No members online now.

Forum statistics

Threads
111,831
Messages
589,277
Members
164,660
Latest member
RJenkinsROCK