Why is iboss so slow for remote users - troubleshooting thread

Oh, we've seen this exact pattern. The tunnel being "correct" is the standard line from networking teams who usually measure success by "is it up?" not "is it usable?"

Your problem is almost certainly SSL decryption on the remote tunnel. iboss is likely inspecting every single HTTPS request from those remote users, adding significant latency, especially to complex, chatty platforms like Salesforce. In-office traffic might be bypassing this inspection via a different path or policy.

Try this: create a test policy that bypasses SSL decryption entirely for your sales cloud domains and push it to a few remote users for a day. If the page load issues vanish, you've found your culprit. The performance hit from full inspection is brutal for remote connections with higher base latency.

"Tunnel set up correctly" is the classic network engineer answer. It means the routes work and packets flow. It says nothing about acceptable performance under inspection policies.

u/741 is right about SSL decryption being the likely culprit, but there's another layer. Even if you create a bypass policy, you're then relying on iboss's internal categorization of those domains being correct and up to date. Salesforce in particular uses a sprawling set of subdomains and CDNs. If your bypass policy is based on a static list, you might miss half of them, leaving inspection on for critical assets and creating a maddeningly inconsistent user experience where some page elements load fast and others crawl.

Have you actually measured the latency added by the iboss proxy hop for your remote users versus a direct connection? That's the data you need to push back with, not just anecdotal reports of "slow."

You've described a very common scenario, and your networking team's definition of "set up correctly" is probably the root of the problem here. It's likely working, but not optimized.

For cloud applications like Salesforce, the default SSL decryption and inspection settings can be a major bottleneck on remote connections. The added latency from having every single request flow through the iboss proxy for deep inspection is often the culprit, especially on high-latency home internet connections compared to your office network.

I'd start by asking your team to compare the exact access policies applied to in-office users versus your remote tunnel users. There's a good chance the remote tunnel has a stricter inspection rule set. A focused test, temporarily whitelisting those specific SaaS domains from decryption for a small group of remote users, will give you a clear answer on whether inspection is the issue.