Here's my story - I've moved to a new VPS which employed nginx, up until a few days ago. I was having an issue with logins, described
here. Disabling nginx caching didn't help; however, when nginx was removed, the login issue went away. My suspicion is that it has to do with the reverse proxy report of my server's IP as every client, rather than the caching aspect.
So currently, I have nginx removed. I was successful in being able to set MARTTIPHPBB_TRUSTXFORWARDEDFOR_IPS to my IP, as reported by this env.php script:
<? $site_path_var = $_SERVER["MARTTIPHPBB_TRUSTXFORWARDEDFOR_IPS"];
echo $site_path_var; ?>
But when I enable this extension, I start getting 500 errors. (I resolved by going into the database and setting the extension to disabled, and clearing the cache.)
martti wrote: Mon Jun 06, 2022 7:22 pm
So you need be sure before enabling the extension that your reverse proxy sets a
X-Forwarded-For
header and know the IP of your reverse proxy, which then you configure the to be trusted.
Hmmm... I take it that without nginx, I'm not going to get this header, and that breaks everything. So I have to reintroduce the problem that nginx causes, in order to test this extension. Have I summarized correctly? And, how do I configure this IP to be trusted? By whom? Sorry, newbie here.
Sorry for the ask - but, is there any way to make this extension innocuous, in the absence of an
X-Forwarded-For
header?
Dan