- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Website Not Secure Only within internal Network
Our website, www.clinedesignassoc.com, shows up as "not secure" when visiting on our network. If I go to the website from my phone or if I take my laptop home and use my home WiFi it shows up with the correct certificates as secure. I'm wondering if our mx85 is doing something? Anyone have any suggestions? FYI this has been going on for awhile, I've even changed to a brand new laptop during so please don't suggest to clear the cache on the device.
Solved! Go to solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Next I would try doing NSLOOKUP and see what IP address that site is resolving to from your DNS. It's resolving to
After that, you may want to check your firewall flows and do some packet captures to see if traffic is going to the correct IP. You need to export to a syslog server to see flows on an MX. Good luck!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Anything else regarding your setup? Currently we know that you're using MX85. Have your configured it to act as Web Proxy? Are your using Umbrella as Cloud Web proxy?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No to both of those. Let me know if any other info is helpful.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What's the certificate showing up when you're browsing internally and how does it look like when you're coming from "external" sources? Especially: what's the signing party for that cert?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Internal DNS setup correctly?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You only get "secure" if using https. Are you using https when browsing the website internally?
If you click on the "insecure" part next to the address, what reason has the browser given for reporting it as insecure?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would start by checking the Event Log on the MX Dashboard to see if it's blocking the website. You can also enter that domain/website under the content filter to see if it'll be blocked.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I tried your suggestions and the website isn't getting blocked. The content filtering labeled it as safe.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Next I would try doing NSLOOKUP and see what IP address that site is resolving to from your DNS. It's resolving to
After that, you may want to check your firewall flows and do some packet captures to see if traffic is going to the correct IP. You need to export to a syslog server to see flows on an MX. Good luck!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good thinking on the NSLOOKUP. So on the same laptop it's getting the same IP as you when hotspot to my phone but a different one when on our network. I'm not sure how to correct this though. I'll do some research but let me know if you have any tips.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Nice. Sounds like we've narrowed the problem. Do you use an internal DNS or any kind of DNS filtering service? I would start investigating there to see why(and where) it's resolving.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We have a pretty basic setup, mostly just using Meraki for our networking setup. We don't have any kind of DNS filtering.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So after doing some digging it was just a DNS issue. Thanks for pointing me in the right way.
We had two old entries in our DNS server that didn’t get changed along with the external records when the website changed addresses
