n 18/04/17 17:04, Eric Covener wrote:
On Tue, Apr 18, 2017 at 12:01 PM, Purvez wrote:
Given where I AM what would you suggest would be the best course of action
to get back to a working system please?
Decide which http server will listen on port 80? Whoever gets port 80
may have to proxy to t
what would you suggest would be the best course of
action to get back to a working system please?
Regards
Purvez
On 18/04/17 16:49, Marat Khalili wrote:
Versions of Apache used by 14.04 and 16.04 are in fact very close:
2.4.7 and 2.4.18, I doubt their configurations are so much different
(u
then move your sites back
into /etc/apache2/sites-available/ one at a time, enable them one at a
time and test as you go along.
Good luck
From: Purvez
<mailto:pur...@nexar.free-online.co.uk>
Reply: users@httpd.apache.org <mailto:users@httpd.apache.org>
<mailto:users@httpd.apach
ir
latest version seems to be running nginx core as part of Standalone and
I think it is nginx that is grabbing port 80.
I'm going to go back to Phusion and explain the problem to them and ask
for a work around.
I will report back here once I have an answer.
Thanks again
Purvez
On 18/04
st on askubuntu:
http://askubuntu.com/questions/904042/upgrade-to-16-04-lts-has-broken-apache
Currently the biggest help I could get would be if someone would
decipher what the following output means when I do :
systemctl status apache2.service
output:
===
*Code:*
purve
