Hey @Wpq ,
There could be an error in your webserver setup. If your Nextcloud configuration remains unchanged with an exception that is what I have added to my previous post, it sounds pretty much like that.
If we assume a setup for cloud.example.com like
browser (a) -> reverse proxy (b) -> Nextcloud with it’s own webserver running https (c)
then the configuration is something like (be aware, you absolutely need to add a few more things regarding security concerns, it just is an excerpt of my configuration):
For http:
# (b)
# http
# 000.conf
…
ProxyRequests Off
ProxyPreserveHost On
RewriteEngine on
RewriteCond %{HTTP_HOST} ^([a-z.]*)?example.com$ [NC]
RewriteRule .? https://%1example.com/%{REQUEST_URI} [R=301,L]
…
And for https:
# (b)
# https
# cloud.conf
<IfModule mod_ssl.c>
<VirtualHost _default_:443>
ServerAdmin admin@example.com
ServerName cloud.example.com
ProxyRequests Off
ProxyPreserveHost On
RemoteIPHeader X-Forwarded-For
<Proxy *>
Require all granted
</Proxy>
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
SSLEngine on
SSLProxyEngine on
SSLProxyVerify none
SSLProxyCheckPeerCN off
SSLProxyCheckPeerName off
SSLProxyCheckPeerExpire off
SSLCertificateFile …
SSLCertificateKeyFile …
ProxyPass / https://111.222.333.444/
ProxyPassReverse / https://111.222.333.444/
</VirtualHost>
</IfModule>
You see RemoteIPHeader X-Forwarded-For in the file cloud.conf This setup works pretty well for me, and the Nextcloud logfile includes the remote ip.