using Wireguard / connecting to a port on an app

I’m also using "::1" for the host on the nrepl-server instead of "localhost".

If the intention is to connect to nrepl-server over 6pn, then nrepl-server must listen on :: or _local_ip.internal or fly-local-6pn to accept connections tunneled in Fly’s wireguard overlay (6pn).

See also: Private networking not working - #4 by kurt

…also added a line to my Dockerfile, EXPOSE 7888.

Fly doesn’t respect dockerfile’s EXPOSE directive. If you intend the port be exposed to the public internet, you need to specify so in fly.toml (ref). If you intend the port be exposed on the vm, there’s nothing to be done, as your Fly app has a free reign to open as many ports it likes.