Can ping Webconfigurator, but can't access

[alvayag]

Hi guys.

I have this weird problem where I can succesfully ping my Pfsense interface ip, but when I put the same ip in the browser, Chrome says the ip takes too long to respond.
The thing is Pfsense is already configured. I have internet in my network, and everything is working properly.
But I cant acces the web gui.

I had to put another nic in Pfsense to access the configurator, and that's not really an option.

Any ideas?  :-\

[muswellhillbilly]

Well, it's a bit of stab in the dar, but could you have set up a firewall rule to block access to your management console from your LAN? Have you checked to see that the management console is running at all? Have you tried restarting the management console from the command line?

[chpalmer]

@alvayag:

Hi guys.

I have this weird problem where I can succesfully ping my Pfsense interface ip, but when I put the same ip in the browser, Chrome says the ip takes too long to respond.
The thing is Pfsense is already configured. I have internet in my network, and everything is working properly.
But I cant acces the web gui.

I had to put another nic in Pfsense to access the configurator, and that's not really an option.
Any ideas?  :-\

If you assign your "new" NIC as the LAN does the problem follow?

[alvayag]

Thanks for the response, guys.
I reinstalled Pfsense from scratch and everything is working good now.

[davzarek]

I have this problem as well on ESXi 6.0.0 pfSense 2.3.2 - DHCP works and can ping,
but can not http in to pfSense on LAN side (havent tried WAN side).

EDGE (IE) just says waiting for 192.168.x.x

WT pfSense in that?

SOLUTION:
Show it was EDGE blocking http and unsecure site with no certificate.
F*** Microsoft and their baby wipers.