Fresh, boilerplate Phoenix application, new Fly.io account
It appears locally there’s an issue with Wireguard - fly doctor seems to switch between these two:
fly doctor
Testing authentication token... PASSED
Testing flyctl agent... PASSED
Testing local Docker instance... Nope
Pinging WireGuard gateway (give us a sec)... FAILED
(Error: ping gateway: pinger: Post "https://api.fly.io/graphql": read tcp [2a02:6b61:da2a:0:dca0:150f:921b:17b4]:55200->[2a09:8280:1:f28:246e:d6a:949:dbbf]:443: read: no route to host)
We can't establish connectivity with WireGuard for your personal organization.
WireGuard runs on 51820/udp, which your local network may block.
If this is the first time you've ever used 'flyctl' on this machine, you
can try running 'flyctl doctor' again.
If this was working before, you can ask 'flyctl' to create a new peer for
you by running 'flyctl wireguard reset'.
If your network might be blocking UDP, you can run 'flyctl wireguard websockets enable',
followed by 'flyctl agent restart', and we'll run WireGuard over HTTPS.
or
fly doctor
Testing authentication token... PASSED
Testing flyctl agent... PASSED
Testing local Docker instance... Nope
Pinging WireGuard gateway (give us a sec)... FAILED
(Error: ping gateway: no response from gateway received)
We can't establish connectivity with WireGuard for your personal organization.
WireGuard runs on 51820/udp, which your local network may block.
If this is the first time you've ever used 'flyctl' on this machine, you
can try running 'flyctl doctor' again.
If this was working before, you can ask 'flyctl' to create a new peer for
you by running 'flyctl wireguard reset'.
If your network might be blocking UDP, you can run 'flyctl wireguard websockets enable',
followed by 'flyctl agent restart', and we'll run WireGuard over HTTPS.
I couldn’t get it to work, I tried allowing it on my router and tried the same from my phone’s 5G, neither worked. The firewall rules on the router (I was kinda guessing, but I disabled IPv6 protection too to try)
I also tried restarting the agent, enabling websockets etc., none of it worked
Now, I don’t need it to work locally, but GitHub action shows the following:
Run flyctl deploy --remote-only
==> Verifying app config
Validating /home/runner/work/emilingo/emilingo/fly.toml
Error: Your fly.toml referenced an attribute 'vm' but it is unknown. Double check the accepted attributes in fly.toml https://fly.io/docs/reference/configuration
WARNING: Failed to fetch platform version: Could not find App "emilingo"
Error: Process completed with exit code 1.
fly.toml as follows, generated by the CLI
# fly.toml app configuration file generated for emilingo on 2023-12-04T22:20:22Z
#
# See https://fly.io/docs/reference/configuration/ for information about how to use this file.
#
app = "emilingo"
primary_region = "lhr"
kill_signal = "SIGTERM"
[build]
[deploy]
release_command = "/app/bin/migrate"
[env]
PHX_HOST = "emilingo.fly.dev"
PORT = "8080"
[http_service]
internal_port = 8080
force_https = true
auto_stop_machines = true
auto_start_machines = true
min_machines_running = 0
processes = ["app"]
[http_service.concurrency]
type = "connections"
hard_limit = 1000
soft_limit = 1000
[[vm]]
cpu_kind = "shared"
cpus = 1
memory_mb = 1024