You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey there, i am using the the compose/apache/postgres example. Last time i checked the admin panel, i noticed that the checksetup request to see the server config summary was timing out after 600ms (/settings/ajax/checksetup).
It was working before, so i guess it was update related.
Everhow i just patched the timeout settings from the proxy container to 1200ms. Now the request is not timing out anymore.
What i did to fix it:
run 'docker-compose down' to stop
FROM nginxproxy/nginx-proxy:alpine
COPY uploadsize.conf /etc/nginx/conf.d/uploadsize.conf
COPY timeout.conf /etc/nginx/conf.d/timeout.conf
remove the proxy container and child dependencies.
run 'docker-compose up -d' to start again
BUT:
could it take more than 600ms to execute the checksetup request on devices like on my Odroid HC-1, Raspi... or is something else is going wrong?
In my logs i could just see the timeout error in the proxy container.
@joshtrichards you are totally right. I just thought the avg request time could be close to 600ms. In this case providing this configs and mentioned it in the documentation would make sense. But i compared it with a fresh installation on bigger machine and had a response time of less than a second.
I'll close it.
Hey there, i am using the the compose/apache/postgres example. Last time i checked the admin panel, i noticed that the checksetup request to see the server config summary was timing out after 600ms (/settings/ajax/checksetup).
It was working before, so i guess it was update related.
Everhow i just patched the timeout settings from the proxy container to 1200ms. Now the request is not timing out anymore.
What i did to fix it:
run 'docker-compose down' to stop
Add new file proxy/timeout.conf
update Dockerfile to:
remove the proxy container and child dependencies.
run 'docker-compose up -d' to start again
BUT:
could it take more than 600ms to execute the checksetup request on devices like on my Odroid HC-1, Raspi... or is something else is going wrong?
In my logs i could just see the timeout error in the proxy container.
My environment:
Hardware: Odroid HC-1
Dockerfile:
Server config:
The text was updated successfully, but these errors were encountered: