Core update 120: no access to web interface

Post Reply
hvb81479
Posts: 11
Joined: February 16th, 2013, 9:06 am

Core update 120: no access to web interface

Post by hvb81479 » May 1st, 2018, 3:19 pm

Hi everybody,

just in case somebody happens to have the same problem:
After updating to 2.19 core update 120 everything worked fine - but no access to web interface

Solution: There was an old "owncloud conf" file sitting in the apache conf folder (/etc/httpd/conf/vhosts.d) that prevented the web server from booting. Check server up & running with /etc/rc.d/init.d/apache status after reboot

kollege_essig
Posts: 1
Joined: May 1st, 2018, 7:35 pm

Re: Core update 120: no access to web interface

Post by kollege_essig » May 1st, 2018, 7:49 pm

All, I had also the issue to access the Web Interface after upgrade.

Following steps I used to solve :
SSH to IPFire (Green IP and port 222), eg with Bitvise

[root@fw ~]# /etc/rc.d/init.d/apache status
/usr/sbin/httpd is not running.

[root@fw ~]# /etc/init.d/apache restart
Restarting Apache daemon...
httpd: Syntax error on line 116 of /etc/httpd/conf/httpd.conf: Syntax error on line 6 of /etc/httpd/conf/vhosts.d/cacti.conf: No matches for the wildcard 'php*.conf' in '/etc/httpd/conf/conf.d', failing (use IncludeOptional if required) [ FAIL ]

--> Edit file with "IncludeOptional" instead of "Include"

[root@fw ~]# /etc/init.d/apache restart
Restarting Apache daemon...
httpd not running, trying to start [ OK ]

[root@fw ~]# /etc/rc.d/init.d/apache status
httpd is running with Process ID(s) 3747 3746 3745.
[root@fw ~]#

:) :) :)

fireon
Posts: 12
Joined: December 26th, 2017, 9:56 am

Re: Core update 120: no access to web interface

Post by fireon » May 1st, 2018, 9:21 pm

Same here, but a simple reboot get the webinterface up running again.

Best
Edi

Post Reply