Skip to content

Update services.html.markerb #1977

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update services.html.markerb #1977

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions networking/services.html.markerb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@
A new Fly App running a public service configured in [`fly.toml`](/docs/reference/configuration/) automatically gets a dedicated Anycast IPv6 address when it's first deployed.

<div class="note icon">
If you create apps with public services in their Machine config by using [`fly machine` commands](/docs/machines/flyctl/fly-machine-run/#define-a-fly-proxy-network-service) or the [Machines API](https://fly.io/docs/machines/api/), then you need to run `fly ips allocate-v6` to get a dedicated IPv6 address.

Check warning on line 24 in networking/services.html.markerb

View workflow job for this annotation

GitHub Actions / Vale linter 

[vale] reported by reviewdog 🐶
[Fly.Machine] Use 'Machine' instead of 'machine'.

Raw Output:
{"message": "[Fly.Machine] Use 'Machine' instead of 'machine'.", "location": {"path": "networking/services.html.markerb", "range": {"start": {"line": 24, "column": 79}}}, "severity": "INFO"}

Check failure on line 24 in networking/services.html.markerb

View workflow job for this annotation

GitHub Actions / Vale linter 

[vale] reported by reviewdog 🐶
[Vale.Terms] Use 'Fly.io' instead of 'fly.io'.

Raw Output:
{"message": "[Vale.Terms] Use 'Fly.io' instead of 'fly.io'.", "location": {"path": "networking/services.html.markerb", "range": {"start": {"line": 24, "column": 204}}}, "severity": "ERROR"}

Check failure on line 24 in networking/services.html.markerb

View workflow job for this annotation

GitHub Actions / Vale linter 

[vale] reported by reviewdog 🐶
[Vale.Terms] Use 'APIs?\b' instead of 'api'.

Raw Output:
{"message": "[Vale.Terms] Use 'APIs?\\b' instead of 'api'.", "location": {"path": "networking/services.html.markerb", "range": {"start": {"line": 24, "column": 225}}}, "severity": "ERROR"}

Check failure on line 24 in networking/services.html.markerb

View workflow job for this annotation

GitHub Actions / Vale linter 

[vale] reported by reviewdog 🐶
[Vale.Terms] Use 'IPs' instead of 'ips'.

Raw Output:
{"message": "[Vale.Terms] Use 'IPs' instead of 'ips'.", "location": {"path": "networking/services.html.markerb", "range": {"start": {"line": 24, "column": 258}}}, "severity": "ERROR"}
</div>

### Shared IPv4
Expand All @@ -44,7 +44,7 @@
```

<div class= "note icon">
If you create apps with public services in their Machine config using [`fly machine` commands](/docs/machines/flyctl/fly-machine-run/#define-a-fly-proxy-network-service) or the [Machines API](https://fly.io/docs/machines/api/), then you need to run `fly ips allocate-v4 --shared` to get a shared IPv4 address.

Check warning on line 47 in networking/services.html.markerb

View workflow job for this annotation

GitHub Actions / Vale linter 

[vale] reported by reviewdog 🐶
[Fly.Machine] Use 'Machine' instead of 'machine'.

Raw Output:
{"message": "[Fly.Machine] Use 'Machine' instead of 'machine'.", "location": {"path": "networking/services.html.markerb", "range": {"start": {"line": 47, "column": 76}}}, "severity": "INFO"}

Check failure on line 47 in networking/services.html.markerb

View workflow job for this annotation

GitHub Actions / Vale linter 

[vale] reported by reviewdog 🐶
[Vale.Terms] Use 'Fly.io' instead of 'fly.io'.

Raw Output:
{"message": "[Vale.Terms] Use 'Fly.io' instead of 'fly.io'.", "location": {"path": "networking/services.html.markerb", "range": {"start": {"line": 47, "column": 201}}}, "severity": "ERROR"}

Check failure on line 47 in networking/services.html.markerb

View workflow job for this annotation

GitHub Actions / Vale linter 

[vale] reported by reviewdog 🐶
[Vale.Terms] Use 'APIs?\b' instead of 'api'.

Raw Output:
{"message": "[Vale.Terms] Use 'APIs?\\b' instead of 'api'.", "location": {"path": "networking/services.html.markerb", "range": {"start": {"line": 47, "column": 222}}}, "severity": "ERROR"}

Check failure on line 47 in networking/services.html.markerb

View workflow job for this annotation

GitHub Actions / Vale linter 

[vale] reported by reviewdog 🐶
[Vale.Terms] Use 'IPs' instead of 'ips'.

Raw Output:
{"message": "[Vale.Terms] Use 'IPs' instead of 'ips'.", "location": {"path": "networking/services.html.markerb", "range": {"start": {"line": 47, "column": 255}}}, "severity": "ERROR"}
</div>

### Dedicated IPv4
Expand Down Expand Up @@ -128,7 +128,7 @@
Fly-Prefer-Region: region-code
```

You can force routing to a specific machine instance:

Check warning on line 131 in networking/services.html.markerb

View workflow job for this annotation

GitHub Actions / Vale linter 

[vale] reported by reviewdog 🐶
[Fly.Machine] Use 'Machine' instead of 'machine'.

Raw Output:
{"message": "[Fly.Machine] Use 'Machine' instead of 'machine'.", "location": {"path": "networking/services.html.markerb", "range": {"start": {"line": 131, "column": 36}}}, "severity": "INFO"}

```
Fly-Force-Instance-Id: instance-number
Expand Down Expand Up @@ -212,9 +212,11 @@

Fly Machines have IPv6 addresses from which they make requests to the wider internet without going through the Fly Proxy.

We don’t offer static IPs or regional IP ranges, and we discourage the use of our outbound IPs to bypass firewalls. A Machine's outbound IP is liable to change without notice. This shouldn't be a daily occurrence, but it will happen if a Machine is moved for whatever reason, such as a load-balancing of Fly Machines between servers in one region.
By default, we don’t offer static IPs or regional IP ranges, and we discourage the use of our outbound IPs to bypass firewalls. A Machine's outbound IP is liable to change without notice. This shouldn't be a daily occurrence, but it will happen if a Machine is moved for whatever reason, such as a load-balancing of Fly Machines between servers in one region.

Check warning on line 215 in networking/services.html.markerb

View workflow job for this annotation

GitHub Actions / Vale linter 

[vale] reported by reviewdog 🐶
[Fly.WordList] Consider using 'firewall rules' instead of 'firewalls'.

Raw Output:
{"message": "[Fly.WordList] Consider using 'firewall rules' instead of 'firewalls'.", "location": {"path": "networking/services.html.markerb", "range": {"start": {"line": 215, "column": 118}}}, "severity": "INFO"}

If you depend on knowing this address for some reason, it's up to you to monitor it for changes.
If you do need a static outbound IP, you can assign one on a per-machine basis. You can allocate one to a machine with `fly machine egress-ip allocate <machine-id>. This will assign both an IPv4 and IPv6 address to the machine. Like dedicated IPv4 addresses, these are [billed](/docs/about/pricing/#static-machine-ip) monthly.

Check warning on line 217 in networking/services.html.markerb

View workflow job for this annotation

GitHub Actions / Vale linter 

[vale] reported by reviewdog 🐶
[Fly.Machine] Use 'Machine' instead of 'machine'.

Raw Output:
{"message": "[Fly.Machine] Use 'Machine' instead of 'machine'.", "location": {"path": "networking/services.html.markerb", "range": {"start": {"line": 217, "column": 106}}}, "severity": "INFO"}

Check warning on line 217 in networking/services.html.markerb

View workflow job for this annotation

GitHub Actions / Vale linter 

[vale] reported by reviewdog 🐶
[Fly.Machine] Use 'Machine' instead of 'machine'.

Raw Output:
{"message": "[Fly.Machine] Use 'Machine' instead of 'machine'.", "location": {"path": "networking/services.html.markerb", "range": {"start": {"line": 217, "column": 124}}}, "severity": "INFO"}

Check warning on line 217 in networking/services.html.markerb

View workflow job for this annotation

GitHub Actions / Vale linter 

[vale] reported by reviewdog 🐶
[Fly.Machine] Use 'Machine' instead of 'machine'.

Raw Output:
{"message": "[Fly.Machine] Use 'Machine' instead of 'machine'.", "location": {"path": "networking/services.html.markerb", "range": {"start": {"line": 217, "column": 219}}}, "severity": "INFO"}

You can also use the `fly machine egress-ip list` command to see all the IPs assigned to your machines, and release IPs with `fly machine egress-ip release <egress-ip>`.

Check warning on line 219 in networking/services.html.markerb

View workflow job for this annotation

GitHub Actions / Vale linter 

[vale] reported by reviewdog 🐶
[Fly.Machine] Use 'Machines' instead of 'machines'.

Raw Output:
{"message": "[Fly.Machine] Use 'Machines' instead of 'machines'.", "location": {"path": "networking/services.html.markerb", "range": {"start": {"line": 219, "column": 94}}}, "severity": "INFO"}

### Find your Machine's outbound IP

Expand Down
Loading