nfelczer
asked on
SonicWall Configuration
I have a dedicated server and recently added a sonicwall firewall to it. Since I did that, I am unable to https to my server. For example, I am able to get to http://www.mydomain.com, however, unable to get to https://www.mydomain.com. I also know the rule https management is working.
Before added the firewall, all was working well.... what could it be?
Before added the firewall, all was working well.... what could it be?
liddler
https uses port 443 http uses port 80, ensure that 443 has the same settings as port 80
ASKER
ports are fine and settings are identical..... what else??
Have you tried switching off the firewall for a moment...just to be certain it is that
ASKER
liddler... it is being hosted by a third-party company and that wouldn't been an option, however, this problem only started when the firewall was installed.
Are you going through a router to the third-party hosting people, if so check or have them check the ACLs on the router to ensure https is allowed
ASKER
liddler... I am directly connected to the WAN. I am sure that the WAN they provide is shared (a router) however, https worked before... only after they installed the firewall, it doesn't work anymore.
I assume if you go onto the server and run a browser locally it can connect to
https://localhost
...Though it does sound like the firewall is dropping it. I'm not familiar with sonicwall, but if it's like othre firewalls it must have a log.
Ensure that https traffic is being logged in the firewall (sometimes you can switch logging of on a rule), then try and connect and see if it is dropping any packets. If sonicwall tells you the rule that is dropping it, check to see if it is the last rule (usually any / any / any drop - i.e. your https rule is wrong) or see which rule is dropping it.
https://localhost
...Though it does sound like the firewall is dropping it. I'm not familiar with sonicwall, but if it's like othre firewalls it must have a log.
Ensure that https traffic is being logged in the firewall (sometimes you can switch logging of on a rule), then try and connect and see if it is dropping any packets. If sonicwall tells you the rule that is dropping it, check to see if it is the last rule (usually any / any / any drop - i.e. your https rule is wrong) or see which rule is dropping it.
ASKER
actually, just tried to https from the dedicated server and couldn't connect. Wierd!! Any ideas what went wrong?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Maybe port 443 or whatever port https is using in your server is blocked?