Extra configs on fresh install causes error

[agates]

Including extra configs (like trusted_proxies) on first install of the chart appears to result in Nextcloud failing with the following:

Error. It looks like you are trying to reinstall your NextCloud. However the file CAN_INSTALL is missing from your config directory. Please create the file CAN_INSTALL in your config folder to continue.

Adding the config after the fact works as intended.

[gjeusel]

Can confirm having faced the same issue, helm chart v2.3.2, docker tag 20.0.2

[lukasmrtvy]

I believe that You can use:

extraEnv:
- name: NEXTCLOUD_TRUSTED_DOMAINS
  value: nextcloud.local

[agates]

Perhaps, though I also have an s3.config.php for my primary storage, for example.

[steled]

I have a similar problem: #114

[fwmarcel]

got the same problem

[benedikt-bartscher]

same here

[kisdaniel]

Any solution? I have a same problem after fresh installation.

[jessebot]

If users are still having this issue, could you please give info about your setup? For instance, can you please post your values.yaml in a syntax highlighted code block (instructions here). Make sure to remove any sensitive data like passwords before posting. I have been using s3 as external storage with the extra configs block for a while and haven't run into any issues.

I can try to test your values locally, or someone else in the community can also try to validate your setup if they have time :)

[jessebot]

As I'm unable to reproduce this issue on a fresh install, there's not been any helm parameters/values.yaml posted here, and there hasn't been activity in over a year, I am going to close this issue as stale. If you're still having trouble with this, please feel free to open a new issue, and please follow the issue template so that we have all the tools we need to help you 🙏

[jessebot]

@agates, just noticed your thumbs down reaction. If you're still having trouble, could you please respond to #48 (comment) on this issue and I can reopen this? We can better help you if you provide what version of the chart you're using, and which values you used. This is important so we can see if you're using persistence, which configs this is an issue with, your env vars, etc. Right now, I'm unable to reproduce the error you originally posted, but with more info, we can try to create a test environment to replicate the error.

Additional info since 2020 when this was opened: We have also recently merged #464 which adds S3 directly via the helm parameters of this chart (nextcloud.objectStore.s3) - there's even some docs on it. (More S3 work coming in #614 too.) We also added the nextcloud.trustedDomains parameter.

We should also create a test for adding extra config files though regardless, as this is a common requirement. I'll create an Issue for that work to be done.

[agates]

Yes, the problem is I haven't had the problem since I created the issue as it only happens on first install.

I have to do a new install soon and will see if I can reproduce it then. I'm stuck on a pretty old version of the chart as it is due to the postgres upgrade (the one that was released as a minor helm chart version bump) that I've yet to get around to.

[disconn3ct]

It is still an issue with v6.2.1 helm chart. S3 config works (referenced above) but the proxy block breaks initial install. Commenting it out it works, and it can be uncommented after. (The only other value of note is 720 retries on the probes.)

configs:
   proxy.config.php: |-
      <?php
      $CONFIG = array (
        'trusted_proxies' => array(
          0 => '127.0.0.1',
          1 => '10.0.0.0/8',
        ),
        'forwarded_for_headers' => array('HTTP_X_FORWARDED_FOR'),
      );

I can stand up test instances as needed. It has been a while but I can still make time if the devs somehow can't reproduce this.