I need help with the setup!! PLS

[Uchowa]

First of all, this is so cool!!! Thank you for all your hard work!..

I set up the server on an old Android phone and can map it to other computers, but I can't find or access the server from my other phones (1 iOS and 1 Android).

I'm also unable to access it from another network via VPN, and I can't restrict access so that only specific IP addresses can connect to my server...

Could someone with more experience please help me?

If possible, please provide a template so I can adapt it to my server.

[yudin-s]

I would split this into three separate layers: LAN reachability, VPN routing, and copyparty permissions. A copyparty config can handle users/volumes and IP restrictions, but it cannot make the Android phone reachable if the WiFi/VPN route is not there.

For an Android-hosted setup, first make sure the server is actually reachable on the same network:

copyparty --qr -z -c cpc

Then from another phone, open the Android server's LAN address directly, for example:

http://192.168.1.50:3923/

If that works from a computer but not from phones, check the network first: guest WiFi/client isolation, mobile data instead of WiFi, Android hotspot isolation, or Termux being background-killed. The README notes that on Android the Termux process generally needs to stay on-screen to accept connections.

A minimal config template would look like this:

[global]
  p: 3923
  z, qr
  # allow this user only from your LAN and VPN CIDRs
  ipr: 192.168.1.0/24,10.8.0.0/24=me

[accounts]
  me: change-this-password

[/]
  /sdcard/copyparty
  accs:
    r: me
    rw: me

Start it with:

copyparty -c cpc

Replace /sdcard/copyparty with the folder you actually want to share, and replace the two CIDRs with your real LAN/VPN ranges. The important permission detail is that there is no r: * in that template, so anonymous users get no access; only the me account can read/write, and ipr rejects that user outside the listed CIDRs.

For access from another network through VPN, test routing outside copyparty first: while connected to the VPN, the client must be able to reach the Android phone's VPN IP or LAN IP and port 3923. If http://<phone-ip>:3923/ does not load at all, fix VPN routing/firewall/Android network restrictions before changing copyparty accounts.

If you put copyparty behind a reverse proxy or tunnel later, be careful with IP rules: configure real-client-IP handling first, otherwise copyparty may only see the proxy's IP and ipr/ipu rules will not mean what you expect.

If this template gets you unstuck, please mark the answer so other Android-hosted copyparty users can find it.

[Uchowa]

Your answer was exactly what I needed—thank you so much!