" if [ $retval -eq 0 ]; then compile=1; fi sa-update --nogpg --channel sought.org retval="$?
Correct ISPConfig Group File Configuration: [sorucecode language=”BASH”] ispconfig:x:5002:apache [/sourcecode] I refreshed the page after adding apache to the ispconfig group and the admin page appeared instantly so problem solved.This obviously indicated a permissions problem of some sort but the correct way to fix things was not to leave it with open access to the world so I investigated further.First off I copied the directory back so I could verify when I had corrected the issue the proper way.One of the things that the package configures is a user and group named nagios.When I took a look into the /etc/group file I noticed that apache was a member of the nagios group but no longer a member of the ispconfig group.Apache ISPConfig Admin 403 Forbidden Error Log Example: So with little to do on in any of the logs I had investigated I decided to retrace my footsteps to see where and when the error might have occurred.
I knew I had made a modification to so i decided to start there in case I had inadvertently added a configuration option that was telling Apache to block the admin directory.
This article explains a system upgrade procedure from Debian 8 Jessie Linux to Debian 9 Stretch.
Apart from the up to date Linux kernel, Stretch comes with a considerable amount of new and updated software as well as a number of packages had been rendered obsolete: This new release of Debian again comes with a lot more software than its predecessor jessie; the distribution includes over 15346 new packages, for a total of over 51687 packages.
I was baffled since this had been working fine after installation.
The Apache logs with the 403 Forbidden errors didn’t provide any more clues but I included them below so you can see if your issues is similar.
I decided to investigate the extra packages I had installed after the ISPConfig setup was complete.