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

Cron runs for a time then stops (kuma docker with nextcloud docker) #2215

Closed
scoop96 opened this issue May 6, 2024 · 3 comments
Closed

Cron runs for a time then stops (kuma docker with nextcloud docker) #2215

scoop96 opened this issue May 6, 2024 · 3 comments

Comments

@scoop96
Copy link

scoop96 commented May 6, 2024

At the end i will attach the docker-compose files.
image

I installed and configured nextcloud, after everything is fixed i go to continue setting it up, first the cron job.
I already had a kuma, so i configured it to connect to my domain.com/cron.php but the output (even when appears as working in kuma is still the same) this is weird, the logs (Even with level swiched to DEBUG) not showing any info.

image

OS: ubuntu
Docker with Nginx proxy manager, and cloudflare DNS

configurations made in nextcloud

.htcaccess file added these lines:

php_value upload_max_filesize 16G
php_value post_max_size 16G
php_value max_input_time 3600
php_value max_execution_time 3600
php_value memory_limit 2048M

config/config.php added these lines

'overwriteprotocol' => 'https',
'default_phone_region' => 'ES',
'loglevel' => 2,
'maintenance_window_start' => 1,

nextcloud docker compose

version: "3"

services:
  nextcloud_app:
    depends_on:
      - nextcloud_db
    container_name: nextcloud
    environment:
      - MYSQL_PASSWORD=$MYSQL_PASSWORD_NEXT
      - MYSQL_DATABASE=$MYSQL_DATABASE_NEXT
      - MYSQL_USER=$MYSQL_USER_NEXT
      - MYSQL_HOST=$MYSQL_HOST_NEXT
      - REDIS_HOST=$REDIS_HOST_NEXT
      - REDIS_HOST_PASSWORD=$REDIS_HOST_PASSWORD_NEXT
    image: nextcloud
    labels:
      - io.portainer.accesscontrol.public
    networks:
      - frontend
      - nextcloud
    links:
      - nextcloud_db
    #ports:
    #  - "8080:80"
    restart: always
    volumes:
      - "$PWD_NAS_DOCKER_VOLUMES/volumes/nextcloud/nextcloud_html:/var/www/html"
      - "$PWD_NAS_DOCKER_VOLUMES/volumes/nextcloud/nextcloud_apps:/var/www/html/custom_apps"
      - "$PWD_NAS_DOCKER_VOLUMES/volumes/nextcloud/nextcloud_config:/var/www/html/config"
      - "$PWD_NAS_DOCKER_VOLUMES/volumes/nextcloud/nextcloud_data:/var/www/html/data"
      - "$PWD_NAS_DOCKER_VOLUMES/volumes/nextcloud/nextcloud_theme:/var/www/html/themes/"



  nextcloud_db:
    command: "--transaction-isolation=READ-COMMITTED --binlog-format=ROW"
    environment:
      - MYSQL_ROOT_PASSWORD=$MYSQL_PASSWORD_NEXT
      - MYSQL_PASSWORD=$MYSQL_PASSWORD_NEXT
      - MYSQL_DATABASE=$MYSQL_DATABASE_NEXT
      - MYSQL_USER=$MYSQL_USER_NEXT
    image: "mariadb:10.5"
    restart: always
    labels:
      - io.portainer.accesscontrol.public
    networks:
      - nextcloud
    volumes:
      - "$PWD_NAS_DOCKER_VOLUMES/volumes/nextcloud/nextcloud_mariadb:/var/lib/mysql"


  go-vod:
    image: radialapps/go-vod
    restart: always
    depends_on:
      - nextcloud_app
    environment:
      - NEXTCLOUD_HOST=https://nextcloud.my-domain.com
      # - NEXTCLOUD_ALLOW_INSECURE=1 # (self-signed certs or no HTTPS)
      - NVIDIA_VISIBLE_DEVICES=all
    devices:
      - /dev/dri:/dev/dri # VA-API (omit for NVENC)
    volumes:
      - $PWD_NAS_DOCKER_VOLUMES/volumes/nextcloud/nextcloud_html:/var/www/html:ro
    # runtime: nvidia # (NVENC)


  redis:
    container_name: nc-redis
    image: "redis:alpine"
    command: redis-server --requirepass ${REDIS_HOST_PASSWORD_NEXT}
    labels:
      - io.portainer.accesscontrol.public
    ports:
      - "6379:6379"
    volumes:
      - "nextcloud_redis_data:/var/lib/redis"
      - "nextcloud_redis_conf:/usr/local/etc/redis/redis.conf"
    environment:
      - REDIS_REPLICATION_MODE=$REDIS_REPLICATION_MODE_NEXT
    networks:
      - nextcloud


volumes:
  nextcloud_redis_data:
    external: true
  nextcloud_redis_conf:
    external: true


networks:
  nextcloud:
  frontend:
    external: true
    

kuma config

version: '3.3'

volumes:
uptimekuma:

services:
uptime-kuma:
 image: louislam/uptime-kuma
 container_name: uptime-kuma
 restart: always
 volumes:
   - uptimekuma:/app/data
 ports:
   - 3001:3001
 networks:
   - frontend

networks:
frontend:
 external: true
@scoop96
Copy link
Author

scoop96 commented May 6, 2024

If i switch to webcron and execute the my-domain.com/cron.php, the message that pops out is this one

image

@scoop96
Copy link
Author

scoop96 commented May 6, 2024

I updated to latest nextcloud version 29.0.0

And the cron is still a problem plus this error regarding well-known.
image

In nginx proxy manager is configured with this (as requiered in the documentation):

location /.well-known/carddav {
    return 301 $scheme://$host/remote.php/dav;
}

location /.well-known/caldav {
    return 301 $scheme://$host/remote.php/dav;
}

location /.well-known/webfinger {
    return 301 $scheme://$host/index.php/.well-known/webfinger;
}

location /.well-known/nodeinfo {
    return 301 $scheme://$host/index.php/.well-known/nodeinfo;
}

@joshtrichards
Copy link
Member

Hi @scoop96 - Please post your queries over at the Help Forum - https://help.nextcloud.com

This channel is solely for reporting bugs in the image itself and these are configuration matters.

P.S. For the cron matters, you can see our config examples in this repository for the ways we suggest running cron.

@joshtrichards joshtrichards closed this as not planned Won't fix, can't repro, duplicate, stale May 6, 2024
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