Sometimes users see a message at the bottom of the form saying the system cannot connect to the server. This usually appears before submitting the form and can prevent the form from completing successfully.
This issue is not related to the form itself. In most cases, it happens because the network environment is blocking certain domains or services required for the form to work properly.
Let’s break down what’s happening and how to resolve it.
What the Error Means
When a form is opened, the system runs a quick background check to confirm that the required services are reachable. These services handle things like:
Form submission
Data validation
Analytics
Translation
Authentication
Security verification
If your network blocks one of these services, the form shows a “Cannot reach server” warning.
This usually happens in environments where:
1) If you are on a VPN
When you use a VPN, your internet traffic goes through a different network. Many VPNs (especially corporate VPNs) block certain cloud endpoints by default. So even if your normal internet works, the form’s backend may not be reachable through the VPN route.
What to do
Disconnect the VPN (even temporarily)
Refresh the form and try again
If the error disappears, the VPN is the cause, and the fix is simply: your VPN team needs to allow the required endpoints.
2) If you are behind a firewall (office or secured network)
Corporate firewalls often block external services unless they are explicitly allowed. In that case, the form loads, but when it tries to verify connectivity and submit data, the network blocks the request, and you see “Cannot reach server”.
What to do
Ask your IT/network team to whitelist the required endpoints and domains (listed below)
These Two URLs Must Be Accessible
Your network is currently unable to reach these routes, which is why the connectivity warning appears:
https://leole6cgas7upah5xfr4zklhha0rsbik.lambda-url.ap-south-1.on.aws/health
https://leole6cgas7upah5xfr4zklhha0rsbik.lambda-url.ap-south-1.on.aws
Once these work, the form can connect to the backend normally.
Domains to Whitelist (To Avoid Future Blocks)
To prevent the same issue from happening again (now or on other forms), please whitelist these domains and their subdomains:
*.boloforms.com(form backend + rendering)*.ap-south-1.on.aws(AWS Lambda form processing)*.amazonaws.com(cloud infrastructure + assets)*.googleapis.com(authentication + translation services)*.intercom.io(support chat)*.ipify.org(IP verification for signing legality)*.clarity.ms(analytics)*.mixpanel.com(analytics)
Access this doc - https://docs.google.com/document/d/1xt9d6eD-lEgovN6We8kon1cmJKjcKmokOKLg6QYuftg/edit?tab=t.0
Once this is done
Refresh the form, and you should be able to submit without any connectivity warnings.
Summary
This connectivity warning occurs when the user’s network blocks required backend services — most commonly due to VPN routing or firewall restrictions. The form intentionally detects this beforehand to prevent unsuccessful submissions.
Whitelisting the required domains and ensuring access to the Lambda URLs resolves the issue in nearly all cases.