Project

General

Profile

Bug #1188

lighttpd not starting after update 20110111

Added by Mykolas Norvaišas over 8 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Web Interface
Target version:
Start date:
01/13/2011
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.0
Affected Architecture:
amd64

Description

Webgui stopped working in HTTPS after update pfSense 2.0 BETA5 amd64 20110111

[2.0-BETA5][root@fw.site]/root(20): cat /var/log/system.log | grep -i "light" -a
Jan 13 12:30:51 fw php: : The command '/usr/local/sbin/lighttpd -f /var/etc/lighty-webConfigurator.conf' returned exit code '255', the output was '2011-01-13 12:30:51: (network.c.565) SSL: error:00000000:lib(0):func(0):reason(0) /var/etc/ca.pem'
[2.0-BETA5][root@fw.site]/root(21): uname -a
FreeBSD fw.site 8.1-RELEASE-p2 FreeBSD 8.1-RELEASE-p2 #1: Wed Jan 12 23:11:04 EST 2011     root@FreeBSD_8.0_pfSense_2.0-AMD64.snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8  amd64 

if I edit conf.xml

                <webgui>
                        <protocol>https</protocol>
                        <ssl-certref>4d089d6f4108b</ssl-certref>
                        <port/>
                </webgui>

to

                <webgui>
                        <protocol>http</protocol>
                        <port/>
                </webgui>


and restart pfsense

History

#1 Updated by Mykolas Norvaišas over 8 years ago

starts working after reverting to HTTP

#2 Updated by Floris van Lint over 8 years ago

This also happened to me on 2.0-BETA5 (i386) built on Thu Jan 13 02:45:05 EST 2011.
Editing config.xml to accept http helped me regain webgui access.

#3 Updated by Mykolas Norvaišas over 8 years ago

one more note

webgui fails to start with my custom SSL certificate. With "webConfigurator default" certicicate HTTPS is working

#4 Updated by Mykolas Norvaišas over 8 years ago

I see CA info is lost after update

System: Certificate Authority Manager shows no authorities (empty).
System: Certificate Manager certificates are not lost (3)

When recreated CA and all certificates and everything is back to normal.

#5 Updated by Jim Pingle over 8 years ago

By default there is no CA with the stock HTTPS certificate, so a missing CA isn't really a problem.

#6 Updated by Mykolas Norvaišas over 8 years ago

I think we can close this bug. Later updates does not cause this issue.

#7 Updated by Chris Buechler over 8 years ago

  • Status changed from New to Closed

#8 Updated by Jim Pingle over 8 years ago

It should be better now, I make a commit to help out with this:
http://redmine.pfsense.org/projects/pfsense/repository/revisions/546f30caee9165f253d9ed3d84e23f03e82626d8

Forgot to update the ticket after the commit though, but I didn't see any more complaints after the snaps included that commit.

Also available in: Atom PDF