nextcloud / nextcloud/helm

Spinning loader won't go away.

Open
#116 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

apache
Dominant language
Go Template
Stars
534
Forks
314
Avg merge
42m
Merged PRs (30d)
1

Description

I've recently tried to deploy this helm chart and everything seems be stood up ok and answering requests.

However, when I login to the application, I get a loading spinner over the initial files and it won't go away. Also, document previews seem to act the same way.

I'm assuming that I need to enable persistent storage or something and perhaps it is having trouble actually service files, but I just can't figure out the problem.

I looked at nextcloud's main repo and knowledgebase, and it seems that people have suggested that this behavior is due to using rich workspaces, but disabling them doesn't seem to make the problem go away.

myvalues.yaml

fullnameOverride: hal-nextcloud
ingress:
  annotations:
    kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/whitelist-source-range: xxx.xxx.xxx.xxx/25,xxx.xxx.xxx.xxx/32
  enabled: true
  hosts:
  - host: hal-nextcloud.mydomain.org
    paths:
    - /
nextcloud:
  host: hal-nextcloud.mydomain.org
  username: admin
  password: foopassword
  extraEnv:
    - name: OVERWRITEPROTOCOL
      value: https
mariadb:
  enabled: true
  db:
    name: nextcloud
    user: nextcloud
    password: foopassword
  rootUser:
    password: foopassword

Any suggestions or maybe a point in the right direction would be greatly appreciated and please let me know if there is any additional information I can provide. Thanks to the maintainers for such providing this chart, it makes deployment trivial (I just can't get past this UI problem).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the deployment with the provided myvalues.yaml, including the ingress, HTTPS overwrite setting, MariaDB, and current storage configuration. Check the chart's handling of persistent storage and the rich-workspace setting, then verify that the initial files and document previews load without an endless spinner.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes
Domain
cloud, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.