I tried to setup Seafile with Apache HTTPS on Ubuntu.
When I try to access my https server-address from WAN I get
Service Unavailable
The server is temporarily unable to service your
request due to maintenance downtime or capacity
problems. Please try again later.
Apache/2.4.7 (Ubuntu) Server at xx.xx-xx.xx Port 443
apache.log file says
[Fri Nov 11 17:38:48.627827 2016] [proxy:error] pid 12721:tid 2934961200Permission denied: AH00952: FCGI: error creating fam 2 socket for target 127.0.0.1
[Fri Nov 11 17:38:48.628010 2016] [proxy:error] [pid 12721:tid 2934961200] AH00959: ap_proxy_connect_backend disabling worker for (127.0.0.1) for 60s
[Fri Nov 11 17:38:48.628041 2016] [proxy_fcgi:error] [pid 12721:tid 2934961200] [client 192.168.20.21:56429] AH01079: failed to make connection to backend: 127.0.0.1
[Fri Nov 11 17:38:49.208150 2016] [proxy:error] [pid 12721:tid 3044013104] AH00940: FCGI: disabled connection for (127.0.0.1)
On seafile forum they say it is SELinux issue. But getenforce = 0.
Do I need to enable some setting in Deploy Linux ?
So, I tried different things - but could not find any element of response to this.
Does anyone know, if this might be related to localhost/127.0.0.1 (proxy for Apache/seafile) being used by Deploy Linux ?
Hi,
I tried to setup Seafile with Apache HTTPS on Ubuntu.
When I try to access my https server-address from WAN I get
Service Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. Apache/2.4.7 (Ubuntu) Server at xx.xx-xx.xx Port 443
apache.log file says
On seafile forum they say it is SELinux issue. But getenforce = 0.
Do I need to enable some setting in Deploy Linux ?