Dev environment not recognized in IpRestrictMiddleware.php

Documentation
1

I installed mautic in Ubuntu with nginx.
I significantly adapted the nginx configuration of proffalken.
I cloned the github repository and executed composer install
The integration with a database using the web installer works fine.
I got the success page.

I want to switch to the development mode before I integrate a mail server.
I added a file .env.local in the mautic root folder with

APP_ENV=dev
APP_DEBUG=1

However, this apparently brakes the application.
After that, the page /installer responded:
You are not allowed to access this file.

My work around was to replace in app/middlewares/Dev/IpRestrictMiddleware.php:

if (in_array($request->getClientIp(), $this->allowedIps) || false !== getenv('DDEV_TLD') )`

with

if (in_array($request->getClientIp(), $this->allowedIps) || false !== getenv('DDEV_TLD') || $_SERVER['APP_ENV'] === 'dev')

But, there might be something else that would fix this problem
in a better way. Any help would be appreciated.

2

I now understand a bit better the situation. The code in IpRestrictMiddleware.php is executed when, in the .env file, APP_DEV=dev. It is not executed when APP_DEV=prod. The code requires that you are in a DDEV environment (not just any dev environment) or that the client Ip is in an allowed list of Ips This seems a reasonable requirement. Moreover, the ips 127.0.0.1, fe80::1 and ::1 are harcoded in the list of allowed Ips. So, in most cases, when you test locally it works. In my case, the client Ip was an Ip of the local network: 192.168.1.x. Fortunately, the code appends to the list of allowed Ips, the value of the environment variable MAUTIC_CUSTOM_DEV_HOSTS. I only had to add env[MAUTIC_CUSTOM_DEV_HOSTS] = '["192.168.1.152"]' in my php-fpm configuration file and it worked. If you are not using php-fpm, it is sufficient to export this environment variable in the usual way in your machine, for example, in your .profile file in linux. By the way, I tested this in the branch 5.2. There might be other issues in 6.x or later versions.

3

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.