# Migration to Podman Quadlet - everything ok?

**URL:** <https://help.nextcloud.com/t/migration-to-podman-quadlet-everything-ok/223753>\
**Category:** ℹ️ Support\
**Tags:** caddy, reverseproxy, real-ip, nc31, setup\_warning\
**Created:** [April 28, 2025, 2:47pm UTC](https://help.nextcloud.com/t/migration-to-podman-quadlet-everything-ok/223753 "2025-04-28T14:47:10Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![beedaddy](https://help.nextcloud.com/user_avatar/help.nextcloud.com/beedaddy/32/175_2.png) [@beedaddy](https://help.nextcloud.com/u/beedaddy)\
**Post date:** [April 28, 2025, 2:47pm UTC](https://help.nextcloud.com/t/migration-to-podman-quadlet-everything-ok/223753/1 "2025-04-28T14:47:10Z")

</div>

Hello all. I’ve migrated my manual installation of Nextcloud 31.0.4 from vServer A ([nextcloud.mydomain.com](http://nextcloud.mydomain.com)) to a Podman quadlet on vServer B ([test.mydomain.com](http://test.mydomain.com)). I use the [docker.io/nextcloud:31](http://docker.io/nextcloud:31) image (so it is running apache). So far, it looks very good.

I have a Caddy server running on the host, just doing

```auto
test.mydomain.com {
        reverse_proxy 127.0.0.1:8086
}

```

And I added my local network to trusted proxies:

```auto
'trusted_proxies' =>
  array (
    0 => '10.0.0.0/8',
  ),

```

With that, I see no error messages in the log and I could connect to my calendar via (desktop) Thunderbird and my Andoid Nextcloud app to the new instance.

But before I actually flip the switch, I want to check again that everything is configured correctly. For example, I saw that some people have this in their Caddyfile:

```auto
redir /.well-known/carddav /remote.php/dav 301
redir /.well-known/caldav /remote.php/dav 301

```

But I don’t need this, because I use the apache-image (not php-fpm), right?

And can I somehow check whether Nexcloud sees the real IP of my clients or only that of the proxy? Or is that not important at all?

---

<div class="post-metadata">

**Author:** ![Erik\_Sjolund](https://help.nextcloud.com/user_avatar/help.nextcloud.com/erik_sjolund/32/55905_2.png) [@Erik\_Sjolund](https://help.nextcloud.com/u/Erik_Sjolund)\
**Post date:** [June 24, 2025, 6:35am UTC](https://help.nextcloud.com/t/migration-to-podman-quadlet-everything-ok/223753/2 "2025-06-24T06:35:03Z")

</div>

> [@beedaddy](#):
>
> And can I somehow check whether Nexcloud sees the real IP of my clients or only that of the proxy?

Yes, it should be possible. If you run a container with rootless podman on a custom network and publish a port with the quadlet directive `PublishPort=` then the program in the container will not see the correct source IP address. This problem can be solved by using _socket activation_ instead of using `PublishPort=`

I wrote a demo of how to run nextcloud with rootless Podman + nginx + socket activation:

> **[GitHub - eriksjolund/nextcloud-podman: Demo of running nextcloud with rootless podman....](https://github.com/eriksjolund/nextcloud-podman)**
>
> Demo of running nextcloud with rootless podman. Systemd services are generated from quadlets. Containers used: nextcloud, mariadb, redis, nginx

But you could probably get it working by using caddy because caddy supports socket activation.  
I wrote some examples (not related to nextcloud)

> **[GitHub - eriksjolund/podman-caddy-socket-activation: Demo of how to run socket-activated caddy with...](https://github.com/eriksjolund/podman-caddy-socket-activation)**
>
> Demo of how to run socket-activated caddy with Podman. Source IP address is preserved.

---

<div class="post-metadata">

**Author:** ![system](https://help.nextcloud.com/user_avatar/help.nextcloud.com/system/32/29333_2.png) [@system](https://help.nextcloud.com/u/system)\
**Post date:** [September 22, 2025, 6:35am UTC](https://help.nextcloud.com/t/migration-to-podman-quadlet-everything-ok/223753/3 "2025-09-22T06:35:51Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
