lionep
lionep
Nice work @lucasheld, the clean way to proceed IMO
Did you change the `timeout` option in the middleware ? It defaults to 5000 ms, it might be short in some cases.
Same. Big Sur 11.1, zsh 5.8
Same here, I just have the logs : app_1 | [24-Apr-2020 13:39:46] NOTICE: fpm is running, pid 1 app_1 | [24-Apr-2020 13:39:46] NOTICE: ready to handle connections Port 9000 is...
The port is exposed, in docker-compose.yml, and app is on the same network as nginx. To test it, I inspected the container, to get it's private ip, and tried from...
Hello, I had the same issue for several days, and it was due to react-native-reanimated which I installed in a beta version (2.3.0-beta). Maybe have a look at [this issue](https://github.com/software-mansion/react-native-reanimated/issues/2460)....
Thanks @JeffGuKang On my side, I didn't have the tab "Signing & Capabilities" for the Pod, I had to set the "Development Team" in build settings for this Pod.
I had the same issue, and it was my env var ALLOWED_HOSTNAMES that was not a valid JSON. I update it with : ALLOWED_HOSTNAMES=["https://cal.domain.com"] and this error is gone, on...
Maybe coolify is escaping some chars in environment ? Can you try do enter your container (if any?) and print the output of : ``` env | grep ALLOWED_HOSTNAMES ```
Can confirm here : Even when starting disabled, I need to enable then disable it again to get internet access on browser (maybe this is a second issue).