Run private applications with Flycast

[mayailurus]

@madsciai

Am I correct that a WireGuard jack-in would not be necessary if I’m not intending to ping my Ollama server on Flycast from my local machine for now?

Right, the instructions mentioned in your other thread should have resulted in your Ollama app having both a Flycast address and an [http_service] block in its fly.toml, which should be enough to make it reachable from all your other Fly.io machines.

Try the curl test that @TheXe (wisely) included. (You should use the default port 80 here, not the more intuitive internal_port.)

@TheXe

$ fly machine run --shell ubuntu
# apt update && apt install -y curl iputils-ping dnsutils
# time curl http://xe-ollama.flycast  # *not* 11434.

Hope this helps a little!

---

Note: Commands preceded by an octothorpe/number-sign (#) prompt in the first column execute within the temporary machine that fly machine run created. Thus, they have access to the internal network—without additional fiddling.

Note²: Also, obviously replace xe-ollama with your own Ollama name, .