… mmmh … wohl nicht …
Proxy Configurations
‘overwritehost’ => ‘’,
The automatic hostname detection of Nextcloud can fail in certain reverse proxy and CLI/cron situations. This option allows you to manually override the automatic detection; for example www.example.com
, or specify the port www.example.com:8080
.
‘overwriteprotocol’ => ‘’,
When generating URLs, Nextcloud attempts to detect whether the server is accessed via https
or http
. However, if Nextcloud is behind a proxy and the proxy handles the https
calls, Nextcloud would not know that ssl
is in use, which would result in incorrect URLs being generated.
Valid values are http
and https
.
‘overwritewebroot’ => ‘’,
Nextcloud attempts to detect the webroot for generating URLs automatically.
For example, if www.example.com/nextcloud
is the URL pointing to the Nextcloud instance, the webroot is /nextcloud
. When proxies are in use, it may be difficult for Nextcloud to detect this parameter, resulting in invalid URLs.
‘overwritecondaddr’ => ‘’,
This option allows you to define a manual override condition as a regular expression for the remote IP address. For example, defining a range of IP addresses starting with 10.0.0.
and ending with 1 to 3: ^10\.0\.0\.[1-3]$
Defaults to ''
(empty string)
‘overwrite.cli.url’ => ‘’,
Use this configuration parameter to specify the base URL for any URLs which are generated within Nextcloud using any kind of command line tools (cron or occ). The value should contain the full base URL: https://www.example.com/nextcloud
Defaults to ''
(empty string)
‘htaccess.RewriteBase’ => ‘/’,
To have clean URLs without /index.php this parameter needs to be configured.
This parameter will be written as “RewriteBase” on update and installation of Nextcloud to your .htaccess file. While this value is often simply the URL path of the Nextcloud installation it cannot be set automatically properly in every scenario and needs thus some manual configuration.
In a standard Apache setup this usually equals the folder that Nextcloud is accessible at. So if Nextcloud is accessible via “https://mycloud.org/nextcloud” the correct value would most likely be “/nextcloud”. If Nextcloud is running under “https://mycloud.org/” then it would be “/”.
Note that the above rule is not valid in every case, as there are some rare setup cases where this may not apply. However, to avoid any update problems this configuration value is explicitly opt-in.
After setting this value run occ maintenance:update:htaccess. Now, when the following conditions are met Nextcloud URLs won’t contain index.php:
- mod_rewrite is installed
- mod_env is installed
Defaults to ''
(empty string)