(docker) Reoccurring 502 bad gateway error with letsencrypt reverse proxy

First, you should know I am new to NC. I installed it a month ago, everything worked at first but I noticed I couldnt upload ‘large’ so I admittedly altered a few conf files on NC and the letsencrypt reverse proxy to lift this silly restriction. I probably broke it. Im considering backing up and trying fresh if I cant get this solved easily.

My problem: I am now getting a reoccurring 502 Bad Gateway error most of the time with the web address but sometimes I will load and allow me to access the nextcloud server website. it will last for only a few minutes then I will get the 502 Bad gateway error again. I am seeing the following error in my /config/log/nginx/error.log

2019/02/11 08:36:48 [error] 313#313: *501 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 172.18.0.3, server: _, request: "POST /updater/index.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "nextcloud.mydomain.com:443"
2019/02/11 08:41:35 [error] 313#313: *614 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 172.18.0.3, server: _, request: "POST /updater/index.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "nextcloud.mydomain.com:443"

172.18.0.3 is the internal docker address of my letsencrypt reverse proxy. Any thoughts?