Unable to set 'overwriteprotocol' => 'https', in config.php from nextcloud-values.yaml
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 534
- Forks
- 314
- Avg merge
- 42m
- Merged PRs (30d)
- 1
Description
Describe your Issue
I need 'overwriteprotocol' => 'https', in my nextcloud config.php in order to use desktop client with my k3s nextcloud. phpClientHttpsFix doesn't seem to work.
Logs and Errors
No errors. Everything works if I manually add "overwriteprotocol..." to the config.php
Describe your Environment
-
Kubernetes distribution: k3s
-
Helm Version (or App that manages helm): version.BuildInfo{Version:"v3.16.4", GitCommit:"7877b45b63f95635153b29a42c0c2f4273ec45ca", GitTreeState:"clean", GoVersion:"go1.22.7"}
-
Helm Chart Version: 6.6.10
-
values.yaml:
nextcloud:
host: "<DOMAIN>"
username: "nc_admin"
password: "<PASSWORD>"
redis:
enabled: true
host: "nextcloud-redis-master"
password: '<PASSWORD>'
config:
overwriteprotocol: "https"
trusted_domains:
- "<DOMAIN>"
- "localhost"
phpClientHttpsFix:
enabled: true
protocol: "https"
replicaCount: 1
ingress:
enabled: true
className: "nginx"
annotations:
cert-manager.io/cluster-issuer: "letsencrypt-prod"
nginx.ingress.kubernetes.io/proxy-body-size: "10G"
hosts:
- host: "<DOMAIN>"
paths: "/"
pathType: "Prefix"
tls:
- secretName: <DOMAIN>-tls
hosts:
- <DOMAIN>
persistence:
enabled: true
storageClass: longhorn
accessMode: ReadWriteOnce
size: 2Ti
internalDatabase:
enabled: false
mariadb:
enabled: true
auth:
database: "nextcloud_db"
username: "nc_user"
password: '<PASSWORD>'
rootPassword: '<PASSWORD>'
architecture: "standalone"
primary:
persistence:
enabled: true
storageClass: "longhorn"
accessMode: "ReadWriteOnce"
size: "10Gi"
redis:
enabled: true
auth:
enabled: true
password: '<PASSWORD>'
master:
persistence:
enabled: true
storageClass: "longhorn"
accessMode: "ReadWriteOnce"
size: "1Gi"
replica:
replicaCount: 0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Render the Helm chart with the supplied values.yaml and inspect the generated config.php for overwriteprotocol. Compare the nextcloud.config and phpClientHttpsFix settings, then verify that the generated configuration contains overwriteprotocol set to https and supports the desktop client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100