We are facing a recurring issue with our custom Frappe application hosted on Azure (Central India region). The problem occurs under the following conditions:
1 Users access a specific page containing custom HTML and VueJS components.
2 Rapidly refreshing the page (20-30 times) causes the site to stop responding, displaying “This site can’t be reached” in the browser.
3 Once this happens, the site remains inaccessible on the affected network. However, switching to a different network (e.g., mobile hotspot or another Wi-Fi) restores access immediately.
Key Observations:
1 The affected network’s IP no longer logs requests in Nginx, suggesting the traffic may be dropped or blocked before reaching the server.
2 No resource overutilization (CPU, memory, or disk) is observed on the Azure VM during these incidents.
3 The page in question has a custom backend function that takes some time to complete. Multiple rapid refreshes may be compounding the issue, potentially triggering a block at the network level.
4 The issue does not occur consistently across networks, which leads us to suspect network-level blocking rather than an application failure.
Request for Help:
We suspect the issue might be related to:
• Network-level rate limiting, timeouts, or blocks caused by repeated page refreshes.
• Application misconfigurations that may trigger network issues under load.
Has anyone faced similar issues with Frappe-based custom applications?
• Are there any recommended settings (e.g., Nginx, backend processing limits, or rate-limiting rules) to mitigate such scenarios?
• What tools or methods can we use to trace where the connection is being dropped?
Any guidance or suggestions would be greatly appreciated!