Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Checksetup request timed out - increase timeout fix it #2213

Closed
web-sash opened this issue Apr 30, 2024 · 3 comments
Closed

Checksetup request timed out - increase timeout fix it #2213

web-sash opened this issue Apr 30, 2024 · 3 comments

Comments

@web-sash
Copy link

web-sash commented Apr 30, 2024

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

fastcgi_read_timeout 120s;
proxy_connect_timeout 120s;
proxy_read_timeout 120s;

update Dockerfile to:

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.


My environment:

Hardware: Odroid HC-1

Dockerfile:

version: '3'

services:
  db:
    image: postgres:alpine
    restart: always
    volumes:
      - db:/var/lib/postgresql/data:Z
    env_file:
      - db.env

  redis:
    image: redis:alpine
    restart: always

  app:
    image: nextcloud:apache
    restart: always
    volumes:
      - nextcloud:/var/www/html:z
    environment:
      - VIRTUAL_HOST=
      - LETSENCRYPT_HOST=
      - LETSENCRYPT_EMAIL=
      - POSTGRES_HOST=db
      - REDIS_HOST=redis
    env_file:
      - db.env
    depends_on:
      - db
      - redis
    networks:
      - proxy-tier
      - default

  cron:
    image: nextcloud:apache
    restart: always
    volumes:
      - nextcloud:/var/www/html:z
    entrypoint: /cron.sh
    depends_on:
      - db
      - redis

  proxy:
    build: ./proxy
    restart: always
    ports:
      - 80:80
      - 443:443
    labels:
      com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy: "true"
    volumes:
      - certs:/etc/nginx/certs:z,ro
      - vhost.d:/etc/nginx/vhost.d:z
      - html:/usr/share/nginx/html:z
      - /var/run/docker.sock:/tmp/docker.sock:z,ro
    networks:
      - proxy-tier

  letsencrypt-companion:
    image: nginxproxy/acme-companion
    restart: always
    volumes:
      - certs:/etc/nginx/certs:z
      - acme:/etc/acme.sh:z
      - vhost.d:/etc/nginx/vhost.d:z
      - html:/usr/share/nginx/html:z
      - /var/run/docker.sock:/var/run/docker.sock:z,ro
    networks:
      - proxy-tier
    depends_on:
      - proxy

volumes:
  db:
    driver: local
    driver_opts:
      type: none
      device: /mnt/hdd/postgresdb
      o: bind
  nextcloud:
    driver: local 
    driver_opts:
      type: none
      device: /mnt/hdd/ncdata
      o: bind
  certs:
  acme:
  vhost.d:
  html:

networks:
  proxy-tier:

Server config:


{
    "system": {
        "htaccess.RewriteBase": "\/",
        "memcache.local": "\\OC\\Memcache\\APCu",
        "apps_paths": [
            {
                "path": "\/var\/www\/html\/apps",
                "url": "\/apps",
                "writable": false
            },
            {
                "path": "\/var\/www\/html\/custom_apps",
                "url": "\/custom_apps",
                "writable": true
            }
        ],
        "memcache.distributed": "\\OC\\Memcache\\Redis",
        "memcache.locking": "\\OC\\Memcache\\Redis",
        "redis": {
            "host": "***REMOVED SENSITIVE VALUE***",
            "password": "***REMOVED SENSITIVE VALUE***",
            "port": 6379
        },
        "upgrade.disable-web": true,
        "instanceid": "***REMOVED SENSITIVE VALUE***",
        "passwordsalt": "***REMOVED SENSITIVE VALUE***",
        "secret": "***REMOVED SENSITIVE VALUE***",
        "trusted_domains": [
            "***REMOVED SENSITIVE VALUE***"
        ],
        "trusted_proxies": "***REMOVED SENSITIVE VALUE***",
        "datadirectory": "***REMOVED SENSITIVE VALUE***",
        "dbtype": "pgsql",
        "version": "29.0.0.19",
        "overwrite.cli.url": "***REMOVED SENSITIVE VALUE***",
        "dbname": "***REMOVED SENSITIVE VALUE***",
        "dbhost": "***REMOVED SENSITIVE VALUE***",
        "dbport": "",
        "dbtableprefix": "oc_",
        "dbuser": "***REMOVED SENSITIVE VALUE***",
        "dbpassword": "***REMOVED SENSITIVE VALUE***",
        "installed": true,
        "loglevel": 2,
        "maintenance": false,
        "mail_smtpmode": "smtp",
        "mail_sendmailmode": "smtp",
        "mail_smtpauth": 1,
        "mail_smtphost": "***REMOVED SENSITIVE VALUE***",
        "mail_smtpport": "465",
        "mail_from_address": "***REMOVED SENSITIVE VALUE***",
        "mail_domain": "***REMOVED SENSITIVE VALUE***",
        "mail_smtpname": "***REMOVED SENSITIVE VALUE***",
        "mail_smtppassword": "***REMOVED SENSITIVE VALUE***",
        "mail_smtpsecure": "ssl"
    }
}

@joshtrichards
Copy link
Member

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?

This is probably a good query to post at the Community Help Forum (https://help.nextcloud.com) and/or if you think it's a bug, to check for bug reports covering (and/or submit one) in the server repository: https://github.com/nextcloud/server

@web-sash
Copy link
Author

@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.

@web-sash
Copy link
Author

The issue is not related to the docker images

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants