I have a problem with one web-application since I switched to XG18.
I have running EcoDMS on a linux server (10.100.10.x) with HTTPS enabled for the Web-Interface (I tired self-signed and wildcard certificate). When I try to connect with my client (same network, local, 10.100.10.x) with Chrome, Safari or Firefox I've always an HTTPS Error (ERR_CONNECTION_REFUSED e.g).
With Internet Explorer I don't have any problems.
I have no DPI or WebProxy enable in my local Network as far as I can see (I'm no Sophos XG expert).
Whats the best way to analyse this on my Sophos XG? Or does someone already know this issue?
please share the firewall rules that match this traffic.
Actually I don't have a rule for that? It's a separate VLAN (10) and both devices are in the same VLAN (10).VLAN (10) is my primary Network. I have rule for:
- VLAN 10 --> to all other VLAN's- VLAN 10 --> WAN
The traffic inside my VLAN 10 should not pass any of those rules, right?
If both devices are in the same VLAN and XG is not deployed in bridge mode and the switch is on the other side of the bridge, XG is not responsible for this issue.
Thanks for the feedback.Please share the drop packet capture and tcpdump for any client for Firefox and chrome.
I think Luk is right. Do the fact that all clients are in the same subnet, traffic is not going trought the XG and so the problem must somewhere else. Right?
Completely agree with you and FormerMember , that's why i have asked for tcpdump and packet capture details over SF Device.
Feel free to get back to us if you have any feedback for SFOSv18