WillyXJ / facileManager

A modular suite of web apps built with the sysadmin in mind.
www.facilemanager.com
GNU General Public License v2.0
85 stars 37 forks source link

[OTHER] When behind a proxy like Traefik user receives "The required .htaccess file appears" error #549

Open Mr-Mors opened 2 years ago

Mr-Mors commented 2 years ago

Please prefix your issue title with one of the following: [BUG], [ISSUE], [FEATURE REQUEST], [MODULE REQUEST], [OTHER].

Replace everything between stars with current version of your facileManager and module installations:
fM Version : 4.2.0 fmDNS Version : 5.2.0

In raising this issue, I confirm the following (please check boxes, eg [X]):


ISSUE Expected Behavior: New install allows user to login after setting up user id.

ISSUE Actual Behavior: User is presented with:

Requirement Error The required .htaccess file appears to not work with your Apache configuration which is required by facileManager. AllowOverride None in your configuration may be blocking the use of .htaccess or dns.d1.mors.io is not resolvable.

ISSUE Steps to reproduce: Place a proxy with HTTP to HTTPS redirection like Traefik infront of facileManager point to facileManagers HTTP port. Issue is not present when going directly to service or disabling the HTTP to HTTPS redirect.

This is related to the following other ISSUES, but I think this is a bit different take on it:

I'm trying to get a slim clean docker project working for fmDNS and my last issue is this access check. Currently I'm just commeting out line 158 in fm-includes/init.php and everything is working.

You can recreate this by downloading the docker project at: https://github.com/Mr-Mors/fmDNS-docker. Then edit the Dockerfile for facileManager and comment out the patch line.

My suggestion is maybe a flag, thats off by default, that bypasses this check.

Thoughts?

adlp commented 2 years ago

For Information, I ve had this problem, and corrected it : my reverse proxy (nginx) was a very very old version, I've just upgrade it, and, now, it's working fine ;)

MeCJay12 commented 1 year ago

Having this issue when trying to upgrade from 4.3.0 to 4.4.0. Once the upgrade is run the error goes away. Using Nginx here.