aisledotnet Posted March 11, 2015 Posted March 11, 2015 Hi, I have an error message when try to connect the systems behind a Corporate firewall. (see message capture). But, any system that has public IP, it works perfect. Do I need to open specific port for this service at firewall? or allow traffic from specific network? Thanks
Staff Chris Posted March 13, 2015 Staff Posted March 13, 2015 Hi, You need to allow outbound HTTPS (TCP 443) connections. No need to open inbound ports. Regards, Chris Pulseway Support
aisledotnet Posted March 16, 2015 Author Posted March 16, 2015 Yes, I allow outbound 443 and set rule and even I set the rule for "Skip SSL decryption, don't filter content, allow all" for *.pulseway.com But, still I have connection error for remote connect. Do you have any server other than *.pulseway.com? like IP range or aws? Because, I saw some drop packet that from Amazon AWS. Thanks
Staff Chris Posted March 16, 2015 Staff Posted March 16, 2015 Hi, No, we don't have any other server other than *.pulseway.com and we don't host our servers in Amazon AWS. Are you using a Pulseway Enterprise Server? Regards, Chris Pulseway Support
aisledotnet Posted March 18, 2015 Author Posted March 18, 2015 I found the issue. It was dropped by our IPS rule. I just whitelist *.pulseway.com also in IPS and works like charm. Thanks for your help.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now