installing via helm chart login issue #5976

hadifarnoud · 2025-01-27T09:01:52Z

hadifarnoud
Jan 27, 2025

Steps to reproduce

go through helm install instructions

Expected behavior

to work properly

Actual behavior

fails install because of missing NEXTCLOUD_DATADIR in values.yaml

DATABASE_PASSWORD: ****
FULLTEXTSEARCH_PASSWORD: ****
IMAGINARY_SECRET: ****
NC_DOMAIN: next.domain.com
NEXTCLOUD_PASSWORD: ****
ONLYOFFICE_SECRET: ****
RECORDING_SECRET: ****
REDIS_PASSWORD: ****
SIGNALING_SECRET: ****
TALK_INTERNAL_SECRET: ****
TIMEZONE: Asia/Tehran          
TURN_SECRET: ****
WHITEBOARD_SECRET: ****
CLAMAV_ENABLED: "yes"          # Setting this to "yes" (with quotes) enables the option in Nextcloud automatically.
COLLABORA_ENABLED: "no"          # Setting this to "yes" (with quotes) enables the option in Nextcloud automatically.
FULLTEXTSEARCH_ENABLED: "yes"          # Setting this to "yes" (with quotes) enables the option in Nextcloud automatically.
IMAGINARY_ENABLED: "yes"          # Setting this to "yes" (with quotes) enables the option in Nextcloud automatically.
ONLYOFFICE_ENABLED: "no"          # Setting this to "yes" (with quotes) enables the option in Nextcloud automatically.
TALK_ENABLED: "yes"          # Setting this to "yes" (with quotes) enables the option in Nextcloud automatically.
TALK_RECORDING_ENABLED: "yes"          # Setting this to "yes" (with quotes) enables the option in Nextcloud automatically.
WHITEBOARD_ENABLED: "no"          # Setting this to "yes" (with quotes) enables the option in Nextcloud automatically.

APACHE_MAX_SIZE: "17179869184"          # This needs to be an integer and in sync with NEXTCLOUD_UPLOAD_LIMIT
APACHE_PORT: 80          
COLLABORA_DICTIONARIES: de_DE en_GB en_US es_ES fr_FR it nl pt_BR pt_PT ru        # You can change this in order to enable other dictionaries for collabora
COLLABORA_SECCOMP_POLICY: --o:security.seccomp=true          
INSTALL_LATEST_MAJOR: no        # Setting this to yes will install the latest Major Nextcloud version upon the first installation
NEXTCLOUD_ADDITIONAL_APKS: imagemagick        
NEXTCLOUD_ADDITIONAL_PHP_EXTENSIONS: imagick       
NEXTCLOUD_MAX_TIME: 3600          # This allows to change the upload time limit of the Nextcloud container
NEXTCLOUD_MEMORY_LIMIT: 512M          # This allows to change the PHP memory limit of the Nextcloud container
NEXTCLOUD_STARTUP_APPS: deck twofactor_totp tasks calendar contacts notes       
NEXTCLOUD_TRUSTED_CACERTS_DIR:        # Setting this to any value allows to automatically import root certificates into the Nextcloud container
NEXTCLOUD_UPLOAD_LIMIT: 16G          # This allows to change the upload limit of the Nextcloud container
REMOVE_DISABLED_APPS: yes        # Setting this to no keep Nextcloud apps that are disabled via their switch and not uninstall them if they should be installed in Nextcloud.
TALK_PORT: 3478          # This allows to adjust the port that the talk container is using. It should be set to something higher than 1024! Otherwise it might not work!
UPDATE_NEXTCLOUD_APPS: no          # When setting to yes (with quotes), it will automatically update all installed Nextcloud apps upon container startup on saturdays.

STORAGE_CLASS: nfs       
APACHE_STORAGE_SIZE: 1Gi      
CLAMAV_STORAGE_SIZE: 5Gi       
DATABASE_STORAGE_SIZE: 5Gi       # You can change the size of the database volume that default to 1Gi with this value
DATABASE_DUMP_STORAGE_SIZE: 1Gi       # You can change the size of the database-dump volume that default to 1Gi with this value
ELASTICSEARCH_STORAGE_SIZE: 1Gi       # You can change the size of the elasticsearch volume that default to 1Gi with this value
NEXTCLOUD_STORAGE_SIZE: 5Gi       # You can change the size of the nextcloud volume that default to 1Gi with this value
NEXTCLOUD_DATA_STORAGE_SIZE: 5Gi       # You can change the size of the nextcloud-data volume that default to 1Gi with this value
NEXTCLOUD_TRUSTED_CACERTS_STORAGE_SIZE: 1Gi      
ONLYOFFICE_STORAGE_SIZE: 1Gi       # You can change the size of the onlyoffice volume that default to 1Gi with this value
REDIS_STORAGE_SIZE: 1Gi       # You can change the size of the redis volume that default to 1Gi with this value
TALK_RECORDING_STORAGE_SIZE: 1Gi       # You can change the size of the talk-recording volume that default to 1Gi with this value

NAMESPACE: nextcloud      # By changing this, you can adjust the namespace of the installation which allows to install multiple instances on one kubernetes cluster
NAMESPACE_DISABLED: "no"      
NETWORK_POLICY_ENABLED: "no"        
SUBSCRIPTION_KEY:        # This allows to set the Nextcloud Enterprise key via ENV
SERVERINFO_TOKEN:        # This allows to set the serverinfo app token for monitoring your Nextcloud via the serverinfo app
APPS_ALLOWLIST:        
ADDITIONAL_TRUSTED_PROXY:    
ADDITIONAL_TRUSTED_DOMAIN:      
NEXTCLOUD_DEFAULT_QUOTA: "10 GB"       # Allows to adjust the default quota that will be taken into account in Nextcloud for new users. Setting it to "unlimited" will set it to unlimited
NEXTCLOUD_MAINTENANCE_WINDOW:   
SMTP_HOST: smtp.domain.com
SMTP_SECURE: STARTTLS
SMTP_PORT: 587
SMTP_AUTHTYPE: PLAIN
SMTP_NAME: [email protected]
SMTP_PASSWORD: ****
MAIL_FROM_ADDRESS: noreply
MAIL_DOMAIN: kamva.ir
TALK_MAX_STREAM_BITRATE: "1048576"         # This allows to adjust the max stream bitrate of the talk hpb
TALK_MAX_SCREEN_BITRATE: "2097152"         # This allows to adjust the max stream bitrate of the talk hpb

Answered by hadifarnoud

Jan 27, 2025

I found out why it's not working. since I do have a load balancer on my cluster (nginx for ingress controller). I assume most people already have ingress controller like nginx on their cluster.

the frustrating part is, when I disabled the nginx controller (and all my services went down because of it), it did load correctly with ssl but still could not login with admin and the password I set in values.yaml

so my original issue of logging in is still not fixed.

View full answer

szaimen · 2025-01-27T09:14:15Z

szaimen
Jan 27, 2025
Maintainer

Hi, can you please post the exact error message here?

0 replies

hadifarnoud · 2025-01-27T09:28:22Z

hadifarnoud
Jan 27, 2025
Author

I get this error:

Connection to nextcloud-aio-database (10.103.250.174) 5432 port [tcp/postgresql] succeeded!
               now                
----------------------------------
 2025-01-27 11:20:55.030874+03:30
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Enabling Imagick...
WARNING: opening from cache https://dl-cdn.alpinelinux.org/alpine/v3.21/main: No such file or directory
WARNING: opening from cache https://dl-cdn.alpinelinux.org/alpine/v3.21/community: No such file or directory
Connection to nextcloud-aio-redis (10.110.25.179) 6379 port [tcp/redis] succeeded!
Nextcloud is not installed - only a limited number of commands are available
Nextcloud is not installed - only a limited number of commands are available
Appdata is not present. Did you maybe change the datadir after the initial Nextcloud installation? This is not supported!
See https://github.com/nextcloud/all-in-one#how-to-change-the-default-location-of-nextclouds-datadir
If you adjusted the datadir to be located on an external drive, make sure that the drive is still mounted!
In the datadir was found:
total 8
drwxrwxrwx 2 root     root     4096 Jan 27 11:20 .
drwxr-xr-x 1 root     root     4096 Jan 27 11:20 ..

0 replies

szaimen · 2025-01-27T09:35:10Z

szaimen
Jan 27, 2025
Maintainer

Can you please try to use a different namespace for testing and check if it suceeds to install? If not, can you please post the logs here?

0 replies

hadifarnoud · 2025-01-27T10:20:45Z

hadifarnoud
Jan 27, 2025
Author

failed again

Waiting for database to start...
Waiting for database to start...
Waiting for database to start...
Waiting for database to start...
Waiting for database to start...
Waiting for database to start...
Waiting for database to start...
Waiting for database to start...
Waiting for database to start...
Connection to nextcloud-aio-database (10.110.251.114) 5432 port [tcp/postgresql] succeeded!
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Enabling Imagick...
WARNING: opening from cache https://dl-cdn.alpinelinux.org/alpine/v3.21/main: No such file or directory
WARNING: opening from cache https://dl-cdn.alpinelinux.org/alpine/v3.21/community: No such file or directory
Connection to nextcloud-aio-redis (10.107.67.114) 6379 port [tcp/redis] succeeded!
Initializing nextcloud 30.0.5.1 ...

I waited 20 minutes. stuck at Initializing nextcloud

0 replies

szaimen · 2025-01-27T10:22:30Z

szaimen
Jan 27, 2025
Maintainer

You need to wait longer. if you use nfs, this might take a very long time to extract the files to your share.

1 reply

hadifarnoud Jan 27, 2025
Author

this fixed the first issue.

hadifarnoud · 2025-01-27T10:57:37Z

hadifarnoud
Jan 27, 2025
Author

it worked. I did set up ingress for apache on port 80 and 8080 in order to get user/pass. it does not load on 8080

am I doing anything wrong? the docs doesn't mention anything

0 replies

hadifarnoud · 2025-01-27T11:42:44Z

hadifarnoud
Jan 27, 2025
Author

UPDATE: I did port-forward on 8080. it still didn't work
also tried grep password /mnt/docker-aio-config/data/configuration.json and sudo grep NEXTCLOUD_PASSWORD /var/lib/docker/volumes/nextcloud_aio_mastercontainer/_data/data/configuration.json. neither worked

I'm asking because ADMIN_USER and ADMIN_PASSWORD (which is NEXTCLOUD_PASSWORD in values.yaml) do not work. I cannot login with those

0 replies

szaimen · 2025-01-27T11:47:16Z

szaimen
Jan 27, 2025
Maintainer

The helm chart publishes its own port on the server: https://github.com/nextcloud/all-in-one/blob/main/nextcloud-aio-helm-chart/templates/nextcloud-aio-apache-service.yaml. If you use apache_port 443, it will be able to generate its own certificate.

2 replies

hadifarnoud Jan 27, 2025
Author

I changed the port to 443 and reinstalled it. I also noticed no ingress. I waited for 20 minutes. SSL was not generated, then I made the ingress myself.

{"level":"error","ts":1737982128.7326024,"msg":"challenge failed","identifier":"nextcloud.domain.com","challenge_type":"tls-alpn-01","problem":{"type":"urn:ietf:params:acme:error:tls","title":"","detail":"49.13.62.161: remote error: tls: no application protocol","instance":"","subproblems":null},"stacktrace":"github.com/mholt/acmez/v3.(*Client).pollAuthorization\n\tgithub.com/mholt/acmez/[email protected]/client.go:557\ngithub.com/mholt/acmez/v3.(*Client).solveChallenges\n\tgithub.com/mholt/acmez/[email protected]/client.go:378\ngithub.com/mholt/acmez/v3.(*Client).ObtainCertificate\n\tgithub.com/mholt/acmez/[email protected]/client.go:136\ngithub.com/caddyserver/certmagic.(*ACMEIssuer).doIssue\n\tgithub.com/caddyserver/[email protected]/acmeissuer.go:477\ngithub.com/caddyserver/certmagic.(*ACMEIssuer).Issue\n\tgithub.com/caddyserver/[email protected]/acmeissuer.go:371\ngithub.com/caddyserver/caddy/v2/modules/caddytls.(*ACMEIssuer).Issue\n\tgithub.com/caddyserver/caddy/[email protected]/modules/caddytls/acmeissuer.go:249\ngithub.com/caddyserver/certmagic.(*Config).obtainCert.func2\n\tgithub.com/caddyserver/[email protected]/config.go:626\ngithub.com/caddyserver/certmagic.doWithRetry\n\tgithub.com/caddyserver/[email protected]/async.go:104\ngithub.com/caddyserver/certmagic.(*Config).obtainCert\n\tgithub.com/caddyserver/[email protected]/config.go:700\ngithub.com/caddyserver/certmagic.(*Config).ObtainCertAsync\n\tgithub.com/caddyserver/[email protected]/config.go:505\ngithub.com/caddyserver/certmagic.(*Config).manageOne.func1\n\tgithub.com/caddyserver/[email protected]/config.go:415\ngithub.com/caddyserver/certmagic.(*jobManager).worker\n\tgithub.com/caddyserver/[email protected]/async.go:73"}
{"level":"error","ts":1737982128.7327144,"msg":"validating authorization","identifier":"nextcloud.domain.com","problem":{"type":"urn:ietf:params:acme:error:tls","title":"","detail":"49.13.62.161: remote error: tls: no application protocol","instance":"","subproblems":null},"order":"https://acme-staging-v02.api.letsencrypt.org/acme/order/182043524/22245937974","attempt":1,"max_attempts":3,"stacktrace":"github.com/mholt/acmez/v3.(*Client).ObtainCertificate\n\tgithub.com/mholt/acmez/[email protected]/client.go:152\ngithub.com/caddyserver/certmagic.(*ACMEIssuer).doIssue\n\tgithub.com/caddyserver/[email protected]/acmeissuer.go:477\ngithub.com/caddyserver/certmagic.(*ACMEIssuer).Issue\n\tgithub.com/caddyserver/[email protected]/acmeissuer.go:371\ngithub.com/caddyserver/caddy/v2/modules/caddytls.(*ACMEIssuer).Issue\n\tgithub.com/caddyserver/caddy/[email protected]/modules/caddytls/acmeissuer.go:249\ngithub.com/caddyserver/certmagic.(*Config).obtainCert.func2\n\tgithub.com/caddyserver/[email protected]/config.go:626\ngithub.com/caddyserver/certmagic.doWithRetry\n\tgithub.com/caddyserver/[email protected]/async.go:104\ngithub.com/caddyserver/certmagic.(*Config).obtainCert\n\tgithub.com/caddyserver/[email protected]/config.go:700\ngithub.com/caddyserver/certmagic.(*Config).ObtainCertAsync\n\tgithub.com/caddyserver/[email protected]/config.go:505\ngithub.com/caddyserver/certmagic.(*Config).manageOne.func1\n\tgithub.com/caddyserver/[email protected]/config.go:415\ngithub.com/caddyserver/certmagic.(*jobManager).worker\n\tgithub.com/caddyserver/[email protected]/async.go:73"}
{"level":"error","ts":1737982128.7327611,"logger":"tls.obtain","msg":"could not get certificate from issuer","identifier":"nextcloud.domain.com","issuer":"acme-v02.api.letsencrypt.org-directory","error":"HTTP 400 urn:ietf:params:acme:error:tls - 49.13.62.161: remote error: tls: no application protocol"}
{"level":"error","ts":1737982128.7327874,"logger":"tls.obtain","msg":"will retry","error":"[nextcloud.domain.com] Obtain: [nextcloud.domain.com] solving challenge: nextcloud.domain.com: [nextcloud.domain.com] authorization failed: HTTP 400 urn:ietf:params:acme:error:tls - 49.13.62.161: remote error: tls: no application protocol (ca=https://acme-staging-v02.api.letsencrypt.org/directory)","attempt":6,"retrying_in":600,"elapsed":1208.300045929,"max_duration":2592000}

hadifarnoud Jan 27, 2025
Author

I found out why it's not working. since I do have a load balancer on my cluster (nginx for ingress controller). I assume most people already have ingress controller like nginx on their cluster.

the frustrating part is, when I disabled the nginx controller (and all my services went down because of it), it did load correctly with ssl but still could not login with admin and the password I set in values.yaml

so my original issue of logging in is still not fixed.

Answer selected by szaimen

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

installing via helm chart login issue #5976

{{title}}

Replies: 8 comments 3 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

installing via helm chart login issue #5976

hadifarnoud Jan 27, 2025

Steps to reproduce

Expected behavior

Actual behavior

Replies: 8 comments · 3 replies

szaimen Jan 27, 2025 Maintainer

hadifarnoud Jan 27, 2025 Author

szaimen Jan 27, 2025 Maintainer

hadifarnoud Jan 27, 2025 Author

szaimen Jan 27, 2025 Maintainer

hadifarnoud Jan 27, 2025 Author

hadifarnoud Jan 27, 2025 Author

hadifarnoud Jan 27, 2025 Author

szaimen Jan 27, 2025 Maintainer

hadifarnoud Jan 27, 2025 Author

hadifarnoud Jan 27, 2025 Author

hadifarnoud
Jan 27, 2025

Replies: 8 comments 3 replies

szaimen
Jan 27, 2025
Maintainer

hadifarnoud
Jan 27, 2025
Author

szaimen
Jan 27, 2025
Maintainer

hadifarnoud
Jan 27, 2025
Author

szaimen
Jan 27, 2025
Maintainer

hadifarnoud Jan 27, 2025
Author

hadifarnoud
Jan 27, 2025
Author

hadifarnoud
Jan 27, 2025
Author

szaimen
Jan 27, 2025
Maintainer

hadifarnoud Jan 27, 2025
Author

hadifarnoud Jan 27, 2025
Author