It took a while and it was starting at me in the face but I did figure it
out. The script that starts the container would make changes to some
php-fpm7 (fastcgi process manager) after it got started. Obviously, this
did not take effect until the restart of the container. This explains the
differ
On Tue, Feb 08, 2022 at 12:31:55AM -0500, marioja2 wrote:
Hi there,
> error.log.2: https://1drv.ms/u/s!ApcymW6zCVpnuxyYecXcaIlqrVWu?e=WmgaVO
> error.log.1: https://1drv.ms/u/s!ApcymW6zCVpnuxt2oIE3eLklkND0?e=ZlJNGH
> access.log.2: https://1drv.ms/u/s!ApcymW6zCVpnuxgl1jCmHH8O-Pmi?e=GJGQgI
> access.
It just dawned on me that the difference between the case where result is
attachment and the case with result is error code is most likely related to
the application reacting to a difference in the environment. Maybe a file or
folder permission. I did check both directory tree and could not see a
d
See below for more questions (I snipped repetitive stuff that was not
necessary for understanding):
Francis Daly Wrote:
---
> On Sun, Feb 06, 2022 at 10:08:49PM -0500, marioja2 wrote:
>
(snip)
> The request that you care about is a POST to a url
Hi, I ran another case with error_log debug. Here are 4 files:
error.log.2: https://1drv.ms/u/s!ApcymW6zCVpnuxyYecXcaIlqrVWu?e=WmgaVO
error.log.1: https://1drv.ms/u/s!ApcymW6zCVpnuxt2oIE3eLklkND0?e=ZlJNGH
access.log.2: https://1drv.ms/u/s!ApcymW6zCVpnuxgl1jCmHH8O-Pmi?e=GJGQgI
access.log.1: https:
On Sun, Feb 06, 2022 at 10:08:49PM -0500, marioja2 wrote:
Hi there,
> I checked and the output when starting from docker-compose up -d or
> docker-compose restart is identical. I include it here:
> https://1drv.ms/u/s!ApcymW6zCVpnuwKQOFFbSCLiZhn9?e=bvrpJU
Thanks; that is useful to see what nginx
Francis, see my response inline:
Hi there,
There's lots of information here, and I'm not sure what specific parts
relate to an nginx issue.
I don't have a full answer, but there are some suggestions below that might
help point at where the problem and fix might be.
> I am running nginx in a c
Fyi - I too am having issues with client_body_max_size in a docker
container, and in fact I just signed up for this mailing list just because
of that.
Restarting docker seems to have no effect for me.
I will send a detailed email about the issue if I'm not able to figure it
out myself soon.
Regards
On Fri, Feb 04, 2022 at 06:33:08PM -0500, marioja2 wrote:
Hi there,
There's lots of information here, and I'm not sure what specific parts
relate to an nginx issue.
I don't have a full answer, but there are some suggestions below that
might help point at where the problem and fix might be.
> I
I am running nginx in a container created with a docker-compose yaml file.
Here is a sample docker-compose.yml and environment file:
https://github.com/marioja/Mailu/tree/test-mailu/test-mailu-docker-compose.
The marioja/rainloop:1.9.TEST image is created using this Dockerfile in
GitHub:
https:
10 matches
Mail list logo