Messages

1

18.1 Legacy Series / Re: lighttpd fails to start on 18.1.6

« on: July 13, 2018, 09:46:51 am »

Hi Franco,

In the settings of the WEB Ui I can only select the management interface. In this case however, the virtual IP's that have been declared as proxy-arp were added to the configuration of the web server.

Upgrading the software and rebooting the firewall caused all services to restart so lighttpd would not start as those IP addresses are not configured in the interface.

This certainly look like a bug to me.

Thanks

George

2

18.1 Legacy Series / Re: lighttpd fails to start on 18.1.6

« on: July 10, 2018, 03:28:11 pm »

It turns out that the configuration of the web server, lighttpd was also listening to 3 Virtual IP's that have been declared as proxy-arp. We had to declare them otherwise 1:1 NAT was not working since ARP was not being broadcasted for some reason.

I removed them from the configuration using vi and now it works.

Only after upgrading the firewall to this version we had that problem with lighttpd.

Could this be a bug that needs to be investigated?

3

18.1 Legacy Series / lighttpd fails to start on 18.1.6

« on: July 10, 2018, 02:42:56 pm »

Hi everyone,

Our OPNSense is running as a virtual machine. We recently upgraded to version 18.1.6 and since then the WebUI is not accessible. All other services work fine. Upon investigating I found the following in our logs:

Jul 10 12:24:38 vff00001 opnsense: /usr/local/etc/rc.reload_all: The command '/usr/local/sbin/lighttpd -f /var/etc/lighty-webConfigurator.conf' returned exit code '255', the output was '2018-07-10 12:24:38: (network.c.313) can't bind to socket: xxx.xxx.xxxx.xxx:443 Can't assign requested address’

Is there anyway to fix this issue or to change from the shell the port from 443 to 80?

Thanks

George