Apache breaks WebConfigurator?

[arrmo]

Hi,

I'm on v2.2 (which has been working great!), today I just installed Apache (want to use it to serve web pages), but now I can no longer get to the Web Configurator (basically, completely locked out from the Web interface).

Is this expected, or a known issue? Any known fixes?

Thanks!

[KOM]

The server is already running lighttpd to serve the pfSense WebGUI, and you slammed Apache on top of that?  I'm not surprised it broke.

[arrmo]

Hi,

Makes sense, my mistake - definitely no argument there! I admit, not sure what the package is for then, but that's not an issue … ;). Bigger issue is to fix it of course.

So a couple dumb questions then (sorry for my ignorance!),

1. Is there a way to kill / remove Apache from the shell (ssh still works)?
2. Can lighttpd be used to serve general web pages? Or, is it better to try to use Web Configurator from Apache?

Thanks!

[KOM]

1.  I have no idea, but I don't know if I would trust it at all any more.  Rebuild it from scratch and your config backup.

2.  Perhaps, I don't know.  Start reading up on lighttpd and then check the pfSense implementation.  I don't see why you couldn't use it as a generic web server.  I wouldn't use my main firewall as a web server.

[networkinggeek]

@arrmo:

Hi,

I'm on v2.2 (which has been working great!), today I just installed Apache (want to use it to serve web pages), but now I can no longer get to the Web Configurator (basically, completely locked out from the Web interface).

Is this expected, or a known issue? Any known fixes?

Thanks!

By default both Pfsense web filter and Apache web server use the same port i.e 80.
You can install apache and change the default listening port to 8080 and then it MIGHT work.

[arrmo]

Will dig into it, thanks for the thoughts!

And I understand the comment about the Web Server running on this box … but it's an "old" machine I had sitting around, lots of spare horsepower doing nothing ... ;).

Thanks again!

[KOM]

I use pfSense in an enterprise environment, not home, so it's a different use-case.  For me, increasing the attack surface of the firewall is a big no-no.

[arrmo]

Makes complete sense, and agree with you!

This is a smaller (home) environment, so having a separate machine just to serve a web page or two is a bit of an overkill … ;).

Thanks!