Hexnode portal inaccessible from office network due to blocked public IPSolved

Hi @ruthg_ ,

If the Hexnode UEM portal is unreachable only from a specific office network while it works from another network, the office public IP may have been restricted by a firewall or Web Application Firewall rule.

A good way to narrow this down is:

1. Try accessing the Hexnode UEM portal from a different network, such as a mobile hotspot.
2. Confirm whether the issue affects all users behind the same office network.
3. Check whether there were repeated failed login attempts, unusual API traffic, or automated requests from that network.
4. If the issue is isolated to one public IP, contact Hexnode Support and ask them to verify whether that public IP is blocked.

In this case, the public IP was found to be blocked and was removed from the firewall rules. Access to the Hexnode UEM portal from the office network worked again after the unblock.

Regards,
Isabel Lora
Hexnode UEM

What can trigger this type of block? We want to avoid it happening again, especially if something on our network is causing repeated requests.

Automated IP restrictions are usually triggered by traffic patterns that resemble abuse or unauthorized access attempts. Common causes include:

• Repeated failed login attempts from the same public IP within a short period.
• A spike in invalid, unauthorized, or unexpected API requests.
• Automated tools or scripts repeatedly hitting the portal or API endpoints.
• Residual MDM-related agents or services from a previous management solution continuously attempting unauthenticated check-ins.

If this happens repeatedly, review internal authentication logs, API integrations, network automation tools, and any legacy MDM agents still running on devices behind that public IP. The immediate fix is to have the IP block reviewed and removed, but identifying the traffic source helps prevent recurrence.

Regards,
Isabel Lora
Hexnode UEM