Problem detecting Internet traffic in Secure connect

Merlin2025
Just browsing

Problem detecting Internet traffic in Secure connect

Hello Guys

 

I have activated Cisco Secure Connect in Meraki to secure Internet traffic from SD-WAN sites. I can see the traffic and firewall policy hits in Umbrella but no traffic stats, no firewall hits in the Secure Connect Dashboard. 

 

Have you encountered this before? 

How can I troubleshoot?

 

Looking forward for your feedback.

 

Thanks

2 Replies 2
RWelch
Kind of a big deal
Kind of a big deal

AI assistant suggests these troubleshooting steps:
  1. Check Umbrella Reporting Integration
    • Replace the Umbrella Reporting API key in Secure Connect. Go to Secure Connect > License & API Keys and use the "Replace API credentials" option on the Umbrella Reporting credentials card. Follow the instructions to retrieve and apply a new key, then verify if stats appear in Secure Connect.
      Cisco Secure Connect - Account Setup Troubleshooting
  2. Confirm Data Storage Location Alignment
    • Check the data storage location in both dashboards and ensure they are paired correctly (e.g., US with North America, Europe with Frankfurt). If misaligned, follow Umbrella documentation to correct the region pairing.
      Reserved IP Guidelines
  3. Review Firewall and Routing Configuration
    • Ensure firewall rules in Secure Connect allow agent traffic to the Internet. Traffic to Meraki and ThousandEyes backend should be excluded from HTTPS Inspection. DNS traffic (port 53 to Umbrella resolvers 208.67.222.222 and 208.67.220.220) should be bypassed from Secure Connect tunnels to avoid policy mismatches and reporting gaps.
      Umbrella SDWAN Connector Deployment Guide
  4. Use Umbrella Reporting Tools for Verification
    • Verify egress source IP addresses and traffic details in Umbrella by using the Activity Search page and filtering by egress data center. This helps confirm that traffic is being processed and reported correctly in Umbrella, even if Secure Connect is not showing stats.
      Umbrella Reporting Tools
  5. General Integration Checks
Summary of Next Steps:
  • Replace the Umbrella Reporting API key in Secure Connect.
  • Verify and align data storage regions between Meraki and Umbrella.
  • Review firewall and DNS exclusion rules.
  • Use Umbrella’s Activity Search to confirm traffic visibility.
  • Double-check API integration and policy assignments.
If these steps do not resolve the issue, please provide more details about your Secure Connect and Umbrella configuration, or contact Cisco Meraki support for further assistance.
 
 
 
If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
Bonzo
Comes here often

Have you updated the Custom Name servers within the Meraki Client VPN settings page. I use Umbrella and have everything working just fine. I have internal DNS appliance servers, when they connect to the vpn, I have the Secure client point to my internal DNS servers .

Get notified when there are additional replies to this discussion.