t0: 1772481804.527
argv: /usr/bin/python3 /usr/lib/python3.12/site-packages/copyparty/__main__.py -c /z/initcfg --chdir=/w --no-crt -e2dsa -e2ts --shr-adm=chamook -sss --no-robots --xff-src=10.42.0.0/16

[36mcopyparty v1.20.10 "[35msftp is fine too[36m" (2026-02-25)
  CPython v3.12.12 on Linux64  [90m[GCC 15.2.0][0;36m
   sqlite 3.51.2*1 | jinja 3.1.6 | pyftpd 1.5.10 | tftp 0.4.0 | miko 4.0.0
[0m
[+] opened logfile [cpp-2026-0302-200324.txt.xz]
2026-03-02
20:03:24.825 root                   LOG: creating new sessions-db /cfg/copyparty/sessions.db
20:03:24.843 root                   LOG: created new sessions-db
20:03:24.847 auth                   BTW: discovered config files in /cfg => ['party.conf']
20:03:24.847 auth                   LOG: loaded 2 config files:
└/z/initcfg
 └/cfg/party.conf
20:03:24.849 auth                   LOG: volumes and permissions:

"/"  /w
|    read:  chamook
|   write:  chamook
|    move:  chamook
|  delete:  chamook
|    dots:  chamook
|     get:  --none--
|   upGet:  --none--
|    html:  --none--
|  uadmin:  chamook

20:03:24.849 auth                   BTW: hint: enable upload deduplication with --dedup (but see readme for consequences)
20:03:24.852 auth                   LOG: added 1 new sessions (chamook)
20:03:24.863 auth                   LOG: {'users': ['chamook', '*'], 'vols': ['/'], 'flags': ['ln', 'p', 'r']}
20:03:24.863 auth                   LOG: /: read({'chamook'}) write({'chamook'}) move({'chamook'}) del({'chamook'}) dots({'chamook'}) get(set()) upGet(set()) html(set()) uadmin({'chamook'})
20:03:24.863 auth                   LOG: checking / as chamook
20:03:24.865 auth                   LOG: checking / as *
20:03:24.865 root                   LOG: max clients: 1024
20:03:24.866 tcpsrv                 LOG: available @  http://127.0.0.1:3923/  (1-lo)
20:03:24.866 tcpsrv                 LOG: available @  http://[::1]:3923/  (1-lo)
20:03:24.866 tcpsrv                 LOG: available @  http://10.42.1.226:3923/  (2-eth0, external)
20:03:24.866 tcpsrv                 LOG: available @  http://[fe80::8c8c:d7ff:febd:5eca]:3923/  (2-eth0, external)
20:03:24.868 optional-dependencies  BTW: OK: sqlite, pillow, vips, pillow-webp, ffmpeg, ffprobe, argon2, pyzmq, rawpy, NG: mutagen, pillow-heif, pillow-avif, see --deps (this is fine btw)
20:03:24.868 thumb                  BTW: setting --no-acode because --no-thumb (sorry)
20:03:24.949 tcpsrv                 LOG: listening @ [::]:3923  f4 p1
20:03:24.949 hsrv                   LOG: subscribed @ [::]:3923  f4 p1
20:03:24.949 root                   LOG: workers OK

20:03:24.950 cert                  WARN: using default TLS certificate; https will be insecure: /cfg/copyparty/cert.pem
20:03:24.952 up2k                   LOG: / dathumb dithumb dvthumb nodupe casechk:n fk:4 fsnt:lin lifetime:864000
20:03:24.976 up2k                   LOG:   /w/.hist/up2k.db |2|
20:03:24.976 mtag                  WARN: could not load Mutagen, trying FFprobe instead
20:03:24.976 mtag                  WARN: found FFprobe but it was disabled by --no-mtag-ff
20:03:24.976 mtag                  CRIT: need Mutagen or FFprobe to read media tags so please run this:
                                     python3 -m pip install --user mutagen

20:03:24.976 up2k                  WARN: uploads temporarily blocked due to indexing
20:03:24.978 up2k                   LOG: reindex '/w' => 'cpp-2026-0302-200102.txt.xz' mtime(1772481662/1772481803) size(0/3288)
20:03:24.986 up2k                   LOG: commit 2 new files; 4 updates
20:03:24.989 up2k                   LOG: uploads are now possible
20:03:24.989 up2k                   LOG: online (reading tags) [/w]
20:03:25.018 up2k                   LOG: 1 volumes in 0.07 sec
20:03:25.018 up2k                  CRIT: could not read tags because no backends are available (Mutagen or FFprobe)
20:03:45.631 10.42.1.213 50786     WARN: could not determine the client's IP-address because the global-option --rproxy has not been configured, so the request-header [x-forwarded-for] specified by global-option --xff-hdr cannot be used safely! The raw header value was [10.42.0.0]. Please see the "reverse-proxy" section in the readme. The best approach is to configure your reverse-proxy to give copyparty the exact IP-address to assume (perhaps in another header), but you may also try the following:

  rproxy: -1   if this client's IP-address is [10.42.0.0]

Furthermore, the following request-headers are also relevant, and you should check that the values below are sensible:

  request-header [x-forwarded-proto] (configured with global-option --xf-proto) has the value [https]; this should be the protocol that the webbrowser is using, so either 'http' or 'https'

  request-header [x-forwarded-host] (configured with global-option --xf-host) has the value [copyparty.chaminy.house]; this should be the website domain or external IP-address which the webbrowser is accessing



20:03:45.631 10.42.1.213 50786      LOG: HEAD / @*
20:03:50.009 10.42.1.213 50786     WARN: could not determine the client's IP-address because the global-option --rproxy has not been configured, so the request-header [x-forwarded-for] specified by global-option --xff-hdr cannot be used safely! The raw header value was [10.42.0.0]. Please see the "reverse-proxy" section in the readme. The best approach is to configure your reverse-proxy to give copyparty the exact IP-address to assume (perhaps in another header), but you may also try the following:

  rproxy: -1   if this client's IP-address is [10.42.0.0]

Furthermore, the following request-headers are also relevant, and you should check that the values below are sensible:

  request-header [x-forwarded-proto] (configured with global-option --xf-proto) has the value [https]; this should be the protocol that the webbrowser is using, so either 'http' or 'https'

  request-header [x-forwarded-host] (configured with global-option --xf-host) has the value [copyparty.chaminy.house]; this should be the website domain or external IP-address which the webbrowser is accessing



20:03:50.010 10.42.1.213 50786      LOG: GET  / @*
20:03:50.043 10.42.1.213 50786     WARN: could not determine the client's IP-address because the global-option --rproxy has not been configured, so the request-header [x-forwarded-for] specified by global-option --xff-hdr cannot be used safely! The raw header value was [10.42.0.0]. Please see the "reverse-proxy" section in the readme. The best approach is to configure your reverse-proxy to give copyparty the exact IP-address to assume (perhaps in another header), but you may also try the following:

  rproxy: -1   if this client's IP-address is [10.42.0.0]

Furthermore, the following request-headers are also relevant, and you should check that the values below are sensible:

  request-header [x-forwarded-proto] (configured with global-option --xf-proto) has the value [https]; this should be the protocol that the webbrowser is using, so either 'http' or 'https'

  request-header [x-forwarded-host] (configured with global-option --xf-host) has the value [copyparty.chaminy.house]; this should be the website domain or external IP-address which the webbrowser is accessing



20:03:50.045 10.42.1.213 50818     WARN: could not determine the client's IP-address because the global-option --rproxy has not been configured, so the request-header [x-forwarded-for] specified by global-option --xff-hdr cannot be used safely! The raw header value was [10.42.0.0]. Please see the "reverse-proxy" section in the readme. The best approach is to configure your reverse-proxy to give copyparty the exact IP-address to assume (perhaps in another header), but you may also try the following:

  rproxy: -1   if this client's IP-address is [10.42.0.0]

Furthermore, the following request-headers are also relevant, and you should check that the values below are sensible:

  request-header [x-forwarded-proto] (configured with global-option --xf-proto) has the value [https]; this should be the protocol that the webbrowser is using, so either 'http' or 'https'

  request-header [x-forwarded-host] (configured with global-option --xf-host) has the value [copyparty.chaminy.house]; this should be the website domain or external IP-address which the webbrowser is accessing



20:03:50.047 10.42.1.213 50804     WARN: could not determine the client's IP-address because the global-option --rproxy has not been configured, so the request-header [x-forwarded-for] specified by global-option --xff-hdr cannot be used safely! The raw header value was [10.42.0.0]. Please see the "reverse-proxy" section in the readme. The best approach is to configure your reverse-proxy to give copyparty the exact IP-address to assume (perhaps in another header), but you may also try the following:

  rproxy: -1   if this client's IP-address is [10.42.0.0]

Furthermore, the following request-headers are also relevant, and you should check that the values below are sensible:

  request-header [x-forwarded-proto] (configured with global-option --xf-proto) has the value [https]; this should be the protocol that the webbrowser is using, so either 'http' or 'https'

  request-header [x-forwarded-host] (configured with global-option --xf-host) has the value [copyparty.chaminy.house]; this should be the website domain or external IP-address which the webbrowser is accessing



20:03:50.048 10.42.1.213 50790     WARN: could not determine the client's IP-address because the global-option --rproxy has not been configured, so the request-header [x-forwarded-for] specified by global-option --xff-hdr cannot be used safely! The raw header value was [10.42.0.0]. Please see the "reverse-proxy" section in the readme. The best approach is to configure your reverse-proxy to give copyparty the exact IP-address to assume (perhaps in another header), but you may also try the following:

  rproxy: -1   if this client's IP-address is [10.42.0.0]

Furthermore, the following request-headers are also relevant, and you should check that the values below are sensible:

  request-header [x-forwarded-proto] (configured with global-option --xf-proto) has the value [https]; this should be the protocol that the webbrowser is using, so either 'http' or 'https'

  request-header [x-forwarded-host] (configured with global-option --xf-host) has the value [copyparty.chaminy.house]; this should be the website domain or external IP-address which the webbrowser is accessing



20:03:55.365 10.42.1.213 50790     WARN: could not determine the client's IP-address because the global-option --rproxy has not been configured, so the request-header [x-forwarded-for] specified by global-option --xff-hdr cannot be used safely! The raw header value was [10.42.0.0]. Please see the "reverse-proxy" section in the readme. The best approach is to configure your reverse-proxy to give copyparty the exact IP-address to assume (perhaps in another header), but you may also try the following:

  rproxy: -1   if this client's IP-address is [10.42.0.0]

Furthermore, the following request-headers are also relevant, and you should check that the values below are sensible:

  request-header [x-forwarded-proto] (configured with global-option --xf-proto) has the value [https]; this should be the protocol that the webbrowser is using, so either 'http' or 'https'

  request-header [x-forwarded-host] (configured with global-option --xf-host) has the value [copyparty.chaminy.house]; this should be the website domain or external IP-address which the webbrowser is accessing



20:03:55.366 10.42.1.213 50790      LOG: HEAD / @*
20:03:56.034 10.42.1.213 50790     WARN: could not determine the client's IP-address because the global-option --rproxy has not been configured, so the request-header [x-forwarded-for] specified by global-option --xff-hdr cannot be used safely! The raw header value was [10.42.0.0]. Please see the "reverse-proxy" section in the readme. The best approach is to configure your reverse-proxy to give copyparty the exact IP-address to assume (perhaps in another header), but you may also try the following:

  rproxy: -1   if this client's IP-address is [10.42.0.0]

Furthermore, the following request-headers are also relevant, and you should check that the values below are sensible:

  request-header [x-forwarded-proto] (configured with global-option --xf-proto) has the value [https]; this should be the protocol that the webbrowser is using, so either 'http' or 'https'

  request-header [x-forwarded-host] (configured with global-option --xf-host) has the value [copyparty.chaminy.house]; this should be the website domain or external IP-address which the webbrowser is accessing



20:03:56.034 10.42.1.213 50790      LOG: GET  / @* [0-2048]
20:03:57.364 10.42.1.213 50790     WARN: could not determine the client's IP-address because the global-option --rproxy has not been configured, so the request-header [x-forwarded-for] specified by global-option --xff-hdr cannot be used safely! The raw header value was [10.42.0.0]. Please see the "reverse-proxy" section in the readme. The best approach is to configure your reverse-proxy to give copyparty the exact IP-address to assume (perhaps in another header), but you may also try the following:

  rproxy: -1   if this client's IP-address is [10.42.0.0]

Furthermore, the following request-headers are also relevant, and you should check that the values below are sensible:

  request-header [x-forwarded-proto] (configured with global-option --xf-proto) has the value [https]; this should be the protocol that the webbrowser is using, so either 'http' or 'https'

  request-header [x-forwarded-host] (configured with global-option --xf-host) has the value [copyparty.chaminy.house]; this should be the website domain or external IP-address which the webbrowser is accessing



20:03:57.364 10.42.1.213 50790      LOG: HEAD /_next @*
20:03:57.364 10.42.1.213 50790      LOG: @* has no access to '/_next'
20:04:01.805 10.42.1.213 50790     WARN: could not determine the client's IP-address because the global-option --rproxy has not been configured, so the request-header [x-forwarded-for] specified by global-option --xff-hdr cannot be used safely! The raw header value was [10.42.0.0]. Please see the "reverse-proxy" section in the readme. The best approach is to configure your reverse-proxy to give copyparty the exact IP-address to assume (perhaps in another header), but you may also try the following:

  rproxy: -1   if this client's IP-address is [10.42.0.0]

Furthermore, the following request-headers are also relevant, and you should check that the values below are sensible:

  request-header [x-forwarded-proto] (configured with global-option --xf-proto) has the value [https]; this should be the protocol that the webbrowser is using, so either 'http' or 'https'

  request-header [x-forwarded-host] (configured with global-option --xf-host) has the value [copyparty.chaminy.house]; this should be the website domain or external IP-address which the webbrowser is accessing



20:04:01.805 10.42.1.213 50790      LOG: GET  / @*
20:04:01.951 10.42.1.213 50790     WARN: could not determine the client's IP-address because the global-option --rproxy has not been configured, so the request-header [x-forwarded-for] specified by global-option --xff-hdr cannot be used safely! The raw header value was [10.42.0.0]. Please see the "reverse-proxy" section in the readme. The best approach is to configure your reverse-proxy to give copyparty the exact IP-address to assume (perhaps in another header), but you may also try the following:

  rproxy: -1   if this client's IP-address is [10.42.0.0]

Furthermore, the following request-headers are also relevant, and you should check that the values below are sensible:

  request-header [x-forwarded-proto] (configured with global-option --xf-proto) has the value [https]; this should be the protocol that the webbrowser is using, so either 'http' or 'https'

  request-header [x-forwarded-host] (configured with global-option --xf-host) has the value [copyparty.chaminy.house]; this should be the website domain or external IP-address which the webbrowser is accessing



20:04:01.952 10.42.1.213 50786     WARN: could not determine the client's IP-address because the global-option --rproxy has not been configured, so the request-header [x-forwarded-for] specified by global-option --xff-hdr cannot be used safely! The raw header value was [10.42.0.0]. Please see the "reverse-proxy" section in the readme. The best approach is to configure your reverse-proxy to give copyparty the exact IP-address to assume (perhaps in another header), but you may also try the following:

  rproxy: -1   if this client's IP-address is [10.42.0.0]

Furthermore, the following request-headers are also relevant, and you should check that the values below are sensible:

  request-header [x-forwarded-proto] (configured with global-option --xf-proto) has the value [https]; this should be the protocol that the webbrowser is using, so either 'http' or 'https'

  request-header [x-forwarded-host] (configured with global-option --xf-host) has the value [copyparty.chaminy.house]; this should be the website domain or external IP-address which the webbrowser is accessing



20:04:58.289 10.42.1.213 50786     WARN: could not determine the client's IP-address because the global-option --rproxy has not been configured, so the request-header [x-forwarded-for] specified by global-option --xff-hdr cannot be used safely! The raw header value was [10.42.0.0]. Please see the "reverse-proxy" section in the readme. The best approach is to configure your reverse-proxy to give copyparty the exact IP-address to assume (perhaps in another header), but you may also try the following:

  rproxy: -1   if this client's IP-address is [10.42.0.0]

Furthermore, the following request-headers are also relevant, and you should check that the values below are sensible:

  request-header [x-forwarded-proto] (configured with global-option --xf-proto) has the value [https]; this should be the protocol that the webbrowser is using, so either 'http' or 'https'

  request-header [x-forwarded-host] (configured with global-option --xf-host) has the value [copyparty.chaminy.house]; this should be the website domain or external IP-address which the webbrowser is accessing



20:04:58.289 10.42.1.213 50786      LOG: HEAD / @*
20:04:59.056 10.42.1.213 50786     WARN: could not determine the client's IP-address because the global-option --rproxy has not been configured, so the request-header [x-forwarded-for] specified by global-option --xff-hdr cannot be used safely! The raw header value was [10.42.0.0]. Please see the "reverse-proxy" section in the readme. The best approach is to configure your reverse-proxy to give copyparty the exact IP-address to assume (perhaps in another header), but you may also try the following:

  rproxy: -1   if this client's IP-address is [10.42.0.0]

Furthermore, the following request-headers are also relevant, and you should check that the values below are sensible:

  request-header [x-forwarded-proto] (configured with global-option --xf-proto) has the value [https]; this should be the protocol that the webbrowser is using, so either 'http' or 'https'

  request-header [x-forwarded-host] (configured with global-option --xf-host) has the value [copyparty.chaminy.house]; this should be the website domain or external IP-address which the webbrowser is accessing



20:04:59.056 10.42.1.213 50786      LOG: GET  / @* [0-2048]
20:05:00.646 10.42.1.213 50786     WARN: could not determine the client's IP-address because the global-option --rproxy has not been configured, so the request-header [x-forwarded-for] specified by global-option --xff-hdr cannot be used safely! The raw header value was [10.42.0.0]. Please see the "reverse-proxy" section in the readme. The best approach is to configure your reverse-proxy to give copyparty the exact IP-address to assume (perhaps in another header), but you may also try the following:

  rproxy: -1   if this client's IP-address is [10.42.0.0]

Furthermore, the following request-headers are also relevant, and you should check that the values below are sensible:

  request-header [x-forwarded-proto] (configured with global-option --xf-proto) has the value [https]; this should be the protocol that the webbrowser is using, so either 'http' or 'https'

  request-header [x-forwarded-host] (configured with global-option --xf-host) has the value [copyparty.chaminy.house]; this should be the website domain or external IP-address which the webbrowser is accessing



20:05:00.646 10.42.1.213 50786      LOG: HEAD /_next @*
20:05:00.646 10.42.1.213 50786      LOG: @* has no access to '/_next'
20:05:53.859 hsrv                   LOG: ok bye
20:05:53.859 tcpsrv                 LOG: ok bye
20:05:53.859 up2k                   LOG: writing snapshot
20:05:53.865 root                   LOG: nailed it
