Lewis,
you can for example turn log level to debug and access the site, tailing
the logs should provide some information about what is breaking. Also, why
you have a ProxyPass on a virtualhost that doesn't run anything PHP? Create
a template without the config and use it.
On Wed, Oct 3, 2018 at
Jack, the logs saying you can't bind the addresses:
Oct 03 14:44:01 donner start_apache2[3998]: (98)Address already in use:
AH00072: make_sock: could not bind to address [::]:443
Oct 03 14:44:01 donner start_apache2[3998]: (98)Address already in use:
AH00072: make_sock: could not bind to address
On 03 Oct 2018, at 12:27, @lbutlr wrote:
> There is exactly one line in the site configuration that, when commented,
> makes the site work again. Though, possibly only for a little while. I’ll
> have to check more in 3-4 hours. There is no other proxy logic at all.
It’ been over 4 hours now
A few minutes later I get:
apache2.service - The Apache Webserver
Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled)
Active: failed (Result: exit-code) since Wed 2018-10-03 15:10:27 PDT; 38s ago
Process: 5147 ExecStop=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k
Well, I have now set SuSE's YaST to reconfigure apache2 using the same
vhosts.conf file while ensuring that php5 is running. Now apache won't start. I
have moved from a 403 error to a site can't be reached error. I get the
following output from systemctl status apache2.service:
apache2.service
The main document root does not interfere with your vhosts. See:
http://httpd.apache.org/docs/current/vhosts/name-based.html#using (See note
about "Main host goes away")
On Wed, Oct 3, 2018 at 2:40 PM Jack M. Nilles wrote:
> I just noticed, upon running 'apache2ctl -S', that the server root is
I just noticed, upon running 'apache2ctl -S', that the server root is listed as
"/srv/www" and the document root as "/srv/www/htdocs" while the actual document
roots are elsewhere (such as /home/data/site1/htdocs). I'm assuming that the
vhosts.conf file takes care of this linkage. If it doesn't
On 03 Oct 2018, at 12:07, Filipe Cifali wrote:
> you can check what virtualhost is being served via apache2ctl like this: $
> apache2ctl -S
> $ apache2ctl -h provides this info:
> -S : a synonym for -t -D DUMP_VHOSTS -D DUMP_RUN_CFG
Yes that is all fine, and the site was
Hi Kremels,
you can check what virtualhost is being served via apache2ctl like this: $
apache2ctl -S
$ apache2ctl -h provides this info:
-S : a synonym for -t -D DUMP_VHOSTS -D DUMP_RUN_CFG
After checking that the right vhost is being served, start removing proxy
logic and just
On 03 Oct 2018, at 11:39, @lbutlr wrote:
> Removing that file made the site load properly.
Well, it did for about 3h25 minutes, in fact.
Just after posting the message, the site went back to showing only “File Not
Found”
I’m at a loss.
The only other issue I see is in the main http-error log
This is probably a coincidence, but I had one of my hosted sites (with no php
code anywhere, and certainly no .php files) returning a script error on load
instead of showing the non-php webpage:
[proxy_fcgi:error] [pid 88148] [client xx.xx.xx.xx:63137] AH01071: Got error
'Primary script
11 matches
Mail list logo
