-
Alternative URL no longer working
Hi All,
The Alternative url : [share].server.sufix
is no longer working while the base url : server.sufix/flexshare/[share]/
is working
The appache error is :
Because the appache configuration is generated by flexshare webconfig in /etc/httpd/conf.d/flex-443.conf
I can't fix it.
The generated configation is :
Alias /flexshare/[share] /var/flexshare/shares/[share]
<VirtualHost *:443>
ServerName [share].server.sufix
DocumentRoot /var/flexshare/shares/[share]
ErrorLog /var/log/httpd/server.sufix_error_log
CustomLog /var/log/httpd/server.sufix_access_log common
SSLEngine on
# No weak export crypto allowed
SSLHonorCipherOrder on
SSLProtocol all -SSLv2 -SSLv3 -TLSv1 -TLSv1.1
SSLCipherSuite ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305HE-RSA-AES128-GCM-SHA256HE-RSA-AES256-GCM-SHA384:ECDH+AESGCMH+AESGCM:ECDH+AES256H+A$
SetEnvIf User-Agent ".*MSIE.*"nokeepalive ssl-unclean-shutdown downgrade-1.0 force-response-1.0
DefineExternalAuth pwauth pipe /usr/bin/pwauth
DefineExternalGroup pwauth pipe /usr/bin/unixgroup
Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile /etc/letsencrypt/live/server.sufix/cert.pem
SSLCertificateKeyFile /etc/letsencrypt/live/server.sufix/privkey.pem
SSLCertificateChainFile /etc/letsencrypt/live/server.sufix/chain.pem
</VirtualHost>
<Directory /var/flexshare/shares/[share]>
Options +Indexes +FollowSymLinks -IncludesNOExec
AuthName "my share"
AuthType Basic
AuthBasicProvider external
AuthExternal pwauth
<RequireAll>
Require unix-group moi
</RequireAll>
<FilesMatch \.php$>
SetHandler None
ForceType text/plain
SetHandler application/x-httpd-php-source
</FilesMatch>
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}
</Directory>
I also do not understand why the configuration is different as they both target the same folder and so the same configuration directives ?!?
What did I miss ?
Why this working feature is now down ?
As the user get a 403 error :
92.184.105.74 - - [17/Jun/2022:10:06:46 +0200] "GET / HTTP/1.1" 403 4897 -