Re: [users@httpd] problem when move https site to 2.4 from 2.2 Apache

2018-08-18 Thread Rose, John B
For each Wordpress site  ...


Wordpress Address (URL)

Site Address (URL)


contain "https" addresses


within Apache each of the sites has a virtual host config, which are basically 
identical except for the naming differences for the sites.


The 2.4 Apache config was built basically identical to 2.2 except for using 
php-fpm instead of mod_php, and "event" MPM instead of "prefork", Require 
instead of Allow/Deny, etc.


No redirecting within Apache except for the sites that my have done it 
themselves within htaccess.


From: Daniel 
Sent: Saturday, August 18, 2018 11:51:30 AM
To: 
Subject: Re: [users@httpd] problem when move https site to 2.4 from 2.2 Apache

depends entirely in the config and context,making assumptions and speculate 
based on generalizations will take you nowhere.

So you should start sharing the relevant bits of config and the queries and 
responses, including headers etc.

El vie., 17 ago. 2018 17:28, Rose, John B 
mailto:jbr...@utk.edu>> escribió:
Encountered problems moving web sites from Apache 2.2 to 2.4 for https

When moving web sites from an Apache 2.2 environment to to 2.4 the ones that 
are .html and self written .php seem to work fine via both http and https

When moving Wordpress sites to 2.4, they work fine via http, but go into 
endless redirects when accessed via https

Has anyone encountered this problem?

Have done some googling, switched back and forth between php-fpm and mod_php, 
removed .htaccess redirects, turned off plugins, etc. Nothing seems to remedy 
it so far.

Thanks




Re: [users@httpd] Problem setting up ssl

2018-08-18 Thread Mahmood Naderan
>OTOH, seems to be some  
>special setup, defaulting to an address from the loopback network  
>(127.0.1.1).

I also noted that, but don't know what to do.



>As you seem to receive some resources via HTTP, the request should get  
>logged somewhere.

I use "tail -f /var/log/apache2/access.log" and error.log on the console and 
then enter IP address in the browser.When I enter http://w.x.y.z the page is 
shown and access.log shows some messages.I also see some debug messages in 
error.log

IMO, the messages aren't important! since I see the page in the 
browser.However, when I enter https://w.x.y.z nothing is shown in the console. 






>You always tell you're accessing "w.x.y.z" and  
>said "the server's page is reachble by an IP address", so I understand  
>you're not using a host name, but IP address to connect. w.x.y.z reads  
>like an IPv4 address, while your earlier report of open ports just  
>gave an IPv6 port open for listening:
>
>root@webshub:~# netstat -tulpn | grep 443
>tcp6      0      0 :::443                  :::*                    
>LISTEN      14709/apache2
>
>So there might be a chance your browser's requests doesn't even end up  
>in *your* server.


I also think such thing is the root of the issue. Things are
1) Yes, I don't have hostname. So, I have to enter ip address.
2) The SSL certificates are created for our university where they have host 
name. 

3) I don't know if the certificates are only usable with subdomains only. Any 
thought?
4) The netstat command shows the IPv6. Is that a firewall issue? iptables? ufw? 
Here is the output of ufw

root@webshub:~# ufw status
Status: active

To Action  From
-- --  
Apache Full    ALLOW   Anywhere
OpenSSH    ALLOW   Anywhere
20/tcp ALLOW   Anywhere
21/tcp ALLOW   Anywhere
990/tcp    ALLOW   Anywhere
4:5/tcp    ALLOW   Anywhere
Apache Full (v6)   ALLOW   Anywhere (v6)
OpenSSH (v6)   ALLOW   Anywhere (v6)
20/tcp (v6)    ALLOW   Anywhere (v6)
21/tcp (v6)    ALLOW   Anywhere (v6)
990/tcp (v6)   ALLOW   Anywhere (v6)
4:5/tcp (v6)   ALLOW   Anywhere (v6)

root@webshub:~# netstat -tulpn | grep 443
tcp6   0  0 :::443  :::*    LISTEN  
1114/apache2
root@webshub:~#







Regards,
Mahmood


Re: [users@httpd] problem when move https site to 2.4 from 2.2 Apache

2018-08-18 Thread Daniel
depends entirely in the config and context,making assumptions and speculate
based on generalizations will take you nowhere.

So you should start sharing the relevant bits of config and the queries and
responses, including headers etc.

El vie., 17 ago. 2018 17:28, Rose, John B  escribió:

> Encountered problems moving web sites from Apache 2.2 to 2.4 for https
>
> When moving web sites from an Apache 2.2 environment to to 2.4 the ones
> that are .html and self written .php seem to work fine via both http and
> https
>
> When moving Wordpress sites to 2.4, they work fine via http, but go into
> endless redirects when accessed via https
>
> Has anyone encountered this problem?
>
> Have done some googling, switched back and forth between php-fpm and
> mod_php, removed .htaccess redirects, turned off plugins, etc. Nothing
> seems to remedy it so far.
>
> Thanks
>
>
>