# \[SOLVED\] Trying to run Nextcloud-AIO behind a Caddy Reverse Proxy

**URL:** <https://help.nextcloud.com/t/solved-trying-to-run-nextcloud-aio-behind-a-caddy-reverse-proxy/176277>\
**Category:** ℹ️ Support\
**Tags:** caddy, docker, aio, cloudflare\
**Created:** [December 9, 2023, 9:28pm UTC](https://help.nextcloud.com/t/solved-trying-to-run-nextcloud-aio-behind-a-caddy-reverse-proxy/176277 "2023-12-09T21:28:27Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![kromsam](https://help.nextcloud.com/user_avatar/help.nextcloud.com/kromsam/32/14632_2.png) [@kromsam](https://help.nextcloud.com/u/kromsam)\
**Post date:** [December 9, 2023, 10:38pm UTC](https://help.nextcloud.com/t/solved-trying-to-run-nextcloud-aio-behind-a-caddy-reverse-proxy/176277/9 "2023-12-09T22:38:15Z")

</div>

Just to see what would happen I changed it to `127.0.0.1`.

This is the outcome.

Nextcloud logs:

“”"

```auto
System config value trusted_proxies => 0 set to string 127.0.0.1

System config value trusted_proxies => 1 set to string ::1

Config value base_endpoint for app notify_push set to https://cloud.domain.tld/push

richdocuments 8.2.3 installed

richdocuments enabled

Config value wopi_url for app richdocuments set to https://cloud.domain.tld/

System config value allow_local_remote_servers set to boolean true

No ipv6-address found for cloud.domain.tld.

Config value wopi_allowlist for app richdocuments set to <public_ip>,127.0.0.1/8,192.168.0.0/16,172.16.0.0/12,10.0.0.0/8,fd00::/8,::1

spreed 17.1.3 installed

spreed enabled

Added cloud.domain.tld:3478.

Added cloud.domain.tld:3478.

There is nothing to delete.

Added signaling server https://cloud.domain.tld/standalone-signaling/.

Config value recording_servers of app spreed deleted

System config value enabledPreviewProviders => 0 set to string OC\Preview\Imaginary

System config value preview_imaginary_url set to string http://nextcloud-aio-imaginary:9000

+ '[' true = true ']'

+ '[' 11000 = 443 ']'

+ '[' 127.0.0.1 = 127.0.0.1 ']'

++ dig nextcloud-aio-apache A +short +search

++ grep '^[0-9.]\+$'

++ sort

++ head -n1

+ IPv4_ADDRESS_APACHE=192.168.96.10

++ dig nextcloud-aio-apache AAAA +short +search

++ grep '^[0-9a-f:]\+$'

++ sort

++ head -n1

+ IPv6_ADDRESS_APACHE=

++ dig nextcloud-aio-mastercontainer A +short +search

++ grep '^[0-9.]\+$'

++ sort

++ head -n1

+ IPv4_ADDRESS_MASTERCONTAINER=192.168.96.2

++ dig nextcloud-aio-mastercontainer AAAA +short +search

++ grep '^[0-9a-f:]\+$'

++ sort

++ head -n1

+ IPv6_ADDRESS_MASTERCONTAINER=

+ sed -i 's|^;listen.allowed_clients|listen.allowed_clients|' /usr/local/etc/php-fpm.d/www.conf

+ sed -i 's|listen.allowed_clients.*|listen.allowed_clients = 127.0.0.1,::1,192.168.96.10,,192.168.96.2,|' /usr/local/etc/php-fpm.d/www.conf

+ sed -i '/^listen.allowed_clients/s/,,/,/g' /usr/local/etc/php-fpm.d/www.conf

+ sed -i '/^listen.allowed_clients/s/,$//' /usr/local/etc/php-fpm.d/www.conf

+ grep listen.allowed_clients /usr/local/etc/php-fpm.d/www.conf

listen.allowed_clients = 127.0.0.1,::1,192.168.96.10,192.168.96.2

+ set +x

[09-Dec-2023 23:33:20] NOTICE: fpm is running, pid 710

[09-Dec-2023 23:33:20] NOTICE: ready to handle connections

Activating Collabora config...

Failed to activate any config changes

Server error: `GET https://cloud.domain.tld/hosting/discovery` resulted in a `502 Bad Gateway` response

```

Caddy logs haven’t changed.

---

_[View the full topic](https://help.nextcloud.com/t/solved-trying-to-run-nextcloud-aio-behind-a-caddy-reverse-proxy/176277)._