Spinning loader won't go away.

[hlesesne]

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

[tvories]

So to clarify, you are able to log in, but then it hangs after login? Or is it hanging on the login screen?

Anything relevant in the Nextcloud pod logs?

You may get more helpful log info by exec-ing into the Nextcloud pod and running the occ command: On the Nextcloud pod:

su www-data -s /bin/bash

./occ status

[hlesesne]

Correct - I am able to login and see menus, files, etc... But, on the main page, the spinning loader is in front of them.

I've torn down the environment, but will stand it back up and take a look again this morning and try to post additional logs and the output of the cli command. Thanks for the response - I'm sorry mine was so delayed.

[hlesesne]

 ./occ status
  - installed: true
  - version: 19.0.3.1
  - versionstring: 19.0.3
  - edition: 

I also pulled the logs and don't believe any of it is relevant. Perhaps the Apache config for fully qualified domain name, but that seems normal when it can't reverse the IP.

Initializing nextcloud 19.0.3.1 ...
Initializing finished
New nextcloud instance
Installing with SQLite database
starting nextcloud installation
Nextcloud was successfully installed
setting trusted domains…
System config value trusted_domains => 1 set to string hal-nextcloud.foo.com
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 10.207.177.86. Set the 'ServerName' directive globally to suppress this message
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 10.207.177.86. Set the 'ServerName' directive globally to suppress this message
[Thu May 27 12:52:13.132371 2021] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.38 (Debian) PHP/7.4.11 configured -- resuming normal operations
[Thu May 27 12:52:13.132452 2021] [core:notice] [pid 1] AH00094: Command line: 'apache2 -D FOREGROUND'
10.101.42.231 - - [27/May/2021:12:52:18 +0000] "GET /status.php HTTP/1.1" 200 1629 "-" "kube-probe/1.20"
10.101.42.231 - - [27/May/2021:12:52:23 +0000] "GET /status.php HTTP/1.1" 200 1635 "-" "kube-probe/1.20"
10.101.42.231 - - [27/May/2021:12:52:28 +0000] "GET /status.php HTTP/1.1" 200 1629 "-" "kube-probe/1.20"
10.101.42.231 - - [27/May/2021:12:52:33 +0000] "GET /status.php HTTP/1.1" 200 1627 "-" "kube-probe/1.20"
10.101.42.231 - - [27/May/2021:12:52:34 +0000] "GET / HTTP/1.1" 302 1108 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36"
...