Re: [users@httpd] Failure to start apache2 after SSL cert update.

2020-07-12 Thread Jack M. Nilles
Thanks, Martin, Great advice! I have two virtual hosts. The certificate and key match on one of them but not on the other. The mismatched one is much less important so I guess I'll de-ssl it until I trace down the mismatch and redo the certificate/key. Thanks again, Jack

Re: [users@httpd] Failure to start apache2 after SSL cert update.

2020-07-11 Thread Jack M. Nilles
comment out the and lines in ssl-global.conf, leaving the SSLSessioncache line as is? And why did this glitch just happen recently? > On 11 Jul 2020, at 10:34, Jack M. Nilles wrote: > > I set the error level to debug in vhosts.conf, tried a restart and got this > from yesterday;

Re: [users@httpd] Failure to start apache2 after SSL cert update.

2020-07-11 Thread Jack M. Nilles
: Init: Session Cache is not configured [hint: SSLSessionCache] [Fri Jul 10 09:47:37.909108 2020] [:emerg] [pid 7681] AH00020: Configuration Failed, exiting AH00016: Configuration Failed > On 11 Jul 2020, at 7:52, Jack M. Nilles wrote: > > The /var/log/apache2/error_log simply li

Re: [users@httpd] Failure to start apache2 after SSL cert update.

2020-07-11 Thread Jack M. Nilles
The /var/log/apache2/error_log simply lists a set of Configuration Failed lines. apachectl configtest produces Syntax OK What file should I change to set the debug level? > On 11 Jul 2020, at 7:08, Jack M. Nilles wrote: > > If I use: openssl x509 -noout -text -in WWW.SITENAM

Re: [users@httpd] Failure to start apache2 after SSL cert update.

2020-07-11 Thread Jack M. Nilles
0 6:10 AM, Holger Schramm wrote: >> Am 11.07.20 um 00:32 schrieb Jack M. Nilles: >>> The apache error logs all quit at the point just before I restarted it. >>> User and group permissions for the SSL files are all root, as before. >>> >>> Jack >>

Re: [users@httpd] Failure to start apache2 after SSL cert update.

2020-07-10 Thread Jack M. Nilles
The apache error logs all quit at the point just before I restarted it. User and group permissions for the SSL files are all root, as before. Jack > On 10 Jul 2020, at 15:00, Antony Stone > wrote: > > On Friday 10 July 2020 at 23:54:05, Jack M. Nilles wrote: > >> I

[users@httpd] Failure to start apache2 after SSL cert update.

2020-07-10 Thread Jack M. Nilles
I recently updated two virtual servers with new SSL certificates, restarted apache and got a failure to load. Here is a diagnostic: systemctl status apache2.service ● apache2.service - The Apache Webserver Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled; vendor preset:

Re: [users@httpd] Access from Internet to web app

2020-04-20 Thread Jack M. Nilles
For starters, all your entries >/Directory> should read > On 20 Apr 2020, at 9:43, > wrote: > > Hi team, <> > > I need to access to a web app from the local network and from > internet (GLPI) > > I use linuxlite =ubuntu 18.04 and Apache 2 with SSL >

Re: [users@httpd] Configuring redirects from http to https

2018-12-03 Thread Jack M. Nilles
I quickly discovered that when a test of host2 returned the host1 index page. So I changed the second VirtualHost address to be the same as host1 (aaa.bbb.ccc.ddd:80). That seems to have solved the problem. So now the actually working *.conf is as follows (as a template?): Listen 80 # Listen

Re: [users@httpd] Configuring redirects from http to https

2018-12-02 Thread Jack M. Nilles
I just added a Listen 80 line at the top of my config file, changed both

Re: [users@httpd] Configuring redirects from http to https

2018-12-01 Thread Jack M. Nilles
on the server and port 80 should be open -- but clearly isn't. So I tried 'nc -l 80' to force the port open; it hung. I have exhausted my linux expertise. > On 1 Dec 2018, at 8:47, Jack M. Nilles wrote: > > Good point. I will add logging to port 80 and see wha

Re: [users@httpd] Configuring redirects from http to https

2018-12-01 Thread Jack M. Nilles
Good point. I will add logging to port 80 and see what happens. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] Configuring redirects from http to https

2018-11-30 Thread Jack M. Nilles
config seems correct, > which is weird > > On Fri, 30 Nov 2018 at 21:17 Jack M. Nilles <mailto:jnil...@jala.com>> wrote: > I have an access log and an error log. The error log doesn't show much for > today. The access log is full of entries from those who have used the ht

Re: [users@httpd] Configuring redirects from http to https

2018-11-30 Thread Jack M. Nilles
I have an access log and an error log. The error log doesn't show much for today. The access log is full of entries from those who have used the https address. What should I be looking for to detect the http failures? - To

Re: [users@httpd] Configuring redirects from http to https

2018-11-30 Thread Jack M. Nilles
The interchange also had no effect. Nor did changing the line to: RedirectPermanent / https://www.host1.com <https://www.host1.com/> > On 30 Nov 2018, at 13:52, Jack M. Nilles wrote: > > This doesn't work for me either with or without the trailing slash. I'll try > it with

Re: [users@httpd] Configuring redirects from http to https

2018-11-30 Thread Jack M. Nilles
erverName www.abc.com <http://www.abc.com/> > ServerAlias abc.com <http://abc.com/> > Redirect 301 / https://www.abc.com/ <https://www.abc.com/> > > > -- > Jeff Cox > j...@jeffpcox.com <mailto:j...@jeffpcox.com> > > > > On Fri,

Re: [users@httpd] Configuring redirects from http to https

2018-11-30 Thread Jack M. Nilles
and maybe more information > about the actual response? the 1xx range isn't supposed to be an error code > in HTTP. > > On Thu, Nov 29, 2018 at 3:25 PM Jack M. Nilles <mailto:jnil...@jala.com>> wrote: > I have the following configuration file covering two virtual

Re: [users@httpd] Configuring redirects from http to https

2018-11-29 Thread Jack M. Nilles
The error I mentioned turns out to be a Squid error. I'm beginning to think I'm getting a false alarm from the browser since, if I connect through a different network, I have no problem with the redirects. I'll have to test some more from different locations. So forget it for now, thanks. >

[users@httpd] Configuring redirects from http to https

2018-11-29 Thread Jack M. Nilles
I have the following configuration file covering two virtual hosts: # http redirect ServerName www.host1.com ServerAlias host1.com *.host1.com Redirect "/" "https://www.host1.com; ServerName www.host2.com ServerAlias host2.com *.host2.com Redirect / https://www.host2.com # https

Re: [users@httpd] 403 error upon upgrade

2018-10-04 Thread Jack M. Nilles
Eureka!! I found a new or recently revised file: /etc/apache2/listen.conf. That had a pair of listen lines under NameVirtualHost that I commented out. Restarting apache then produced a running server. Thanks, guys, for your patience and help! I will keep your emails in my Whatthehell? folder

Re: [users@httpd] 403 error upon upgrade

2018-10-04 Thread Jack M. Nilles
Of course, since Apache isn't running -- failed to start -- why would I get any LISTEN ports? > On 4 Oct 2018, at 11:46, Jack M. Nilles wrote: > > Here's what I get for the first part of that: > > # netstat -napo | egrep "(:80|:443)" > tcp0 0 1.2.3.4:

Re: [users@httpd] 403 error upon upgrade

2018-10-04 Thread Jack M. Nilles
Here's what I get for the first part of that: # netstat -napo | egrep "(:80|:443)" tcp0 0 1.2.3.4:43160 23.210.206.246:443 ESTABLISHED 1961/(squid-1) off (0.00/0/0) tcp0 0 1.2.3.4:59116 107.14.47.80:80 TIME_WAIT - timewait

Re: [users@httpd] 403 error upon upgrade

2018-10-04 Thread Jack M. Nilles
Here's what I get: # lsof -i:443 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME java 710 root 245u IPv6 49204 0t0 TCP server.site1.com:52752->central.crashplanpro.com:https (ESTABLISHED) squid 1961 squid 13u IPv4 19134 0t0 TCP server.site1.com

Re: [users@httpd] 403 error upon upgrade

2018-10-03 Thread Jack M. Nilles
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

Re: [users@httpd] 403 error upon upgrade

2018-10-03 Thread Jack M. Nilles
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

Re: [users@httpd] 403 error upon upgrade

2018-10-03 Thread Jack M. Nilles
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

Re: [users@httpd] 403 error upon upgrade

2018-10-02 Thread Jack M. Nilles
Frank, My main concern is to get apache to run with php at all, never mind scalability issues. So far everything looks fine except that it doesn't work. Maybe somewhere in the bowels of SuSE 42.1 there is an error. Jack - To

Re: [users@httpd] 403 error upon upgrade

2018-10-02 Thread Jack M. Nilles
t; Nowadays, mod_proxy_fcgi and php-fpm is trivial to set up, and allow you to > use a threaded mpm, such as event. > > On Tue, Oct 2, 2018 at 11:21 AM Jack M. Nilles <mailto:jnil...@jala.com>> wrote: > Sure enough, there seems to be no php module loaded: > > Loaded

Re: [users@httpd] 403 error upon upgrade

2018-10-02 Thread Jack M. Nilles
The package manager (YaST) shows php5.5 as installed so it should have php-fpm in its code base. I notice that /etc/php5/apache2/php.ini at present has short_open_tag = Off which might be the clue to its ignoring all the code in these sites that use -- or not. The commented text is a tad

Re: [users@httpd] 403 error upon upgrade

2018-10-02 Thread Jack M. Nilles
Sure enough, there seems to be no php module loaded: Loaded Modules: core_module (static) so_module (static) http_module (static) mpm_prefork_module (static) unixd_module (static) systemd_module (static) actions_module (shared) alias_module (shared) auth_basic_module (shared)

Re: [users@httpd] 403 error upon upgrade

2018-10-01 Thread Jack M. Nilles
/etc/apache2/conf.d/php5.conf is as follows: SetHandler application/x-httpd-php SetHandler application/x-httpd-php-source DirectoryIndex index.php4 DirectoryIndex index.php5 DirectoryIndex index.php Why this doesn't

Re: [users@httpd] 403 error upon upgrade

2018-09-30 Thread Jack M. Nilles
I don't have an index.html in that directory -- only index.php. I suppose I could put in an html file that immediately switches to the php page. That site has always worked before with no index.html file. Why not now? - To

Re: [users@httpd] 403 error upon upgrade

2018-09-30 Thread Jack M. Nilles
Basically the same as before: [Sun Sep 30 10:29:05.708882 2018] [autoindex:error] [pid 3663] [client 220.181.51.119:50416] AH01276: Cannot serve directory /home/data/site1/htdocs/: No matching DirectoryIndex (index.html,index.html.var) found, and server-generated directory index forbidden by

Re: [users@httpd] 403 error upon upgrade

2018-09-29 Thread Jack M. Nilles
I have found another DirectoryIndex directive in /etc/apache2/conf.d/gitweb.conf. Since this is higher up the chain than the vhosts.d directory that might be what's producing the file download behavior. If I omit the DirectoryIndex line and restart apache then I at least just get the 403 error

Re: [users@httpd] 403 error upon upgrade

2018-09-28 Thread Jack M . Nilles
f said .htaccess file is to set up > permalinks, all you need is likely a single FallbackResource in the vhost > context instead. > > Also, set the DirectoryIndex in the vhost context instead. > > On Thu, Sep 27, 2018 at 1:29 PM Jack M. Nilles <mailto:jnil...@jala.com>> wro

[users@httpd] 403 error upon upgrade

2018-09-27 Thread Jack M. Nilles
Two days ago I upgraded my SUSE server. It serves three websites as virtual sites. All of the sites run php. Upon restarting apache 2.4 I got the following error message: [Wed Sep 26 07:36:55.666104 2018] [autoindex:error] [pid 12345] [client 1.2.3.4:50430] AH01276: Cannot serve directory