[GH-ISSUE #100] Nextcloud config #88

Closed
opened 2026-02-26 05:34:19 +03:00 by kerem · 1 comment
Owner

Originally created by @WesSec on GitHub (Mar 11, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/100

Hey all.

Just switched from the letsencrypt docker to this one, and I love it so far.
The only thing I can't get to work is the nextcloud instance running in docker aswell. I read some other issues and a lot of people are mentioning nextcloud, is someone willing to share their config and/or how they got it to work?

My current config in the webUI is:
proxy host: subdomain.domain.com (i only want the subdomain to refer to the reverse proxy, but that isn't an issue)
custom location:
location: /nextcloud
scheme: https
ip: my nextcloud server ip
port: my nextcloud server port

This is my nextcloud config:
<?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'REDACTED', 'passwordsalt' => 'REDACTED', 'secret' => 'REDACTED', 'trusted_domains' => array ( 0 => 'INTERNAL IP OF MY NEXTCLOUD INSTANCE', 1 => 'subdomain.domain.com', ), 'dbtype' => 'mysql', 'version' => '15.0.2.0', 'overwrite.cli.url' => 'https://subdomain.domain.com/nextcloud', 'dbname' => 'nextcloud', 'dbhost' => 'REDACTED', 'dbport' => 'REDACTED', 'dbtableprefix' => 'oc_', 'mysql.utf8mb4' => true, 'dbuser' => 'REDACTED', 'dbpassword' => 'REDACTED', 'installed' => true, 'trusted_proxies' => array ( 0 => 'letsencrypt', 1 => 'INTERNAL IP OF MY NGINX PROXY', ), );

Originally created by @WesSec on GitHub (Mar 11, 2019). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/100 Hey all. Just switched from the letsencrypt docker to this one, and I love it so far. The only thing I can't get to work is the nextcloud instance running in docker aswell. I read some other issues and a lot of people are mentioning nextcloud, is someone willing to share their config and/or how they got it to work? My current config in the webUI is: proxy host: subdomain.domain.com (i only want the subdomain to refer to the reverse proxy, but that isn't an issue) custom location: location: /nextcloud scheme: https ip: my nextcloud server ip port: my nextcloud server port This is my nextcloud config: `<?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'REDACTED', 'passwordsalt' => 'REDACTED', 'secret' => 'REDACTED', 'trusted_domains' => array ( 0 => 'INTERNAL IP OF MY NEXTCLOUD INSTANCE', 1 => 'subdomain.domain.com', ), 'dbtype' => 'mysql', 'version' => '15.0.2.0', 'overwrite.cli.url' => 'https://subdomain.domain.com/nextcloud', 'dbname' => 'nextcloud', 'dbhost' => 'REDACTED', 'dbport' => 'REDACTED', 'dbtableprefix' => 'oc_', 'mysql.utf8mb4' => true, 'dbuser' => 'REDACTED', 'dbpassword' => 'REDACTED', 'installed' => true, 'trusted_proxies' => array ( 0 => 'letsencrypt', 1 => 'INTERNAL IP OF MY NGINX PROXY', ), );`
kerem closed this issue 2026-02-26 05:34:19 +03:00
Author
Owner

@WesSec commented on GitHub (Mar 11, 2019):

Solution: I was in the understanding that nextcloud had to be in a subfolder instead of a subdomain, I created a new proxy host with a subdomain for the nextcloud instance, set the certificate and it works!

<!-- gh-comment-id:471759107 --> @WesSec commented on GitHub (Mar 11, 2019): Solution: I was in the understanding that nextcloud had to be in a subfolder instead of a subdomain, I created a new proxy host with a subdomain for the nextcloud instance, set the certificate and it works!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#88
No description provided.