Skip to content

docs(actors): sync from rivet-dev/actors #52

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

Merged
NathanFlurry merged 1 commit into from
Sep 10, 2026
Merged

docs(actors): sync from rivet-dev/actors #52

Show file tree
Hide file tree
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
2 changes: 1 addition & 1 deletion vendor/actors/docs/content/docs/debugging.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -199,7 +199,7 @@ Returns the configured provider settings per datacenter and the latest pool erro
}
```

`runner_pool_error` mirrors actor scheduling errors such as `serverless_http_error`, `serverless_connection_error`, and `serverless_stream_ended_early`.
`runner_pool_error` mirrors actor scheduling errors such as `serverless_http_error`, `serverless_connection_error`, `serverless_destination_blocked`, and `serverless_stream_ended_early`.

### Check Serverless Provider Health

Expand Down
4 changes: 2 additions & 2 deletions vendor/actors/docs/content/docs/limits.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,8 +132,8 @@ See [Actor Input](/actors/docs/input) for details.

| Name | Soft Limit | Hard Limit | Description |
|------|------------|------------|-------------|
| Rate limit | — | 1200 requests/minute | Default rate limit per actor per IP address with a 1 minute time bucket. |
| Max in-flight requests | — | 32 | Default maximum concurrent requests to an actor per IP address. |
| Rate limit | — | — | Disabled by default. Configure `guard.rate_limit` to apply a fixed-window limit per source IP. |
| Max in-flight requests | — | — | Disabled by default. Configure `guard.max_in_flight` to limit concurrent requests per source IP. |

### Timeouts

Expand Down
16 changes: 16 additions & 0 deletions vendor/actors/docs/content/docs/troubleshooting.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,6 +97,14 @@ Rivet was unable to connect to your serverless endpoint. Check that:
- Your server is publicly reachable from the internet.
- There are no DNS or firewall issues blocking the connection.

### `serverless_destination_blocked`

The configured serverless URL points at a destination Rivet is not allowed to reach. Rivet dials serverless endpoints from inside its own network, so by default it refuses any destination that is not publicly routable: private ranges, link-local and cloud metadata addresses, carrier-grade NAT, and other reserved ranges. Check that:

- Your endpoint URL is publicly reachable, and is not an internal hostname or address.
- The URL scheme is `http` or `https`, and the URL does not embed credentials.
- If you are self-hosting and intentionally point runners at an address on your own network, set `outbound.allow_private_networks` to `true` in your engine config, or list the specific range in `outbound.allow_cidrs`.

@the-company-company the-company-company Bot Sep 10, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Low · The new remediation uses retired deployment terms

This user-facing addition calls the control plane an “engine” and calls workers “runners,” both of which conflict with the site's required terminology. Say “control plane config” and “workers” so this guidance remains consistent with the rest of the website.


### `serverless_stream_ended_early`

The connection to your serverless endpoint was terminated before the actor finished. This usually means your serverless function hit its execution time limit. Ensure that your Rivet provider's request lifespan is configured to match the max duration of your serverless platform.
Expand All @@ -108,6 +116,14 @@ Rivet received an unexpected response from your serverless endpoint. This typica
- Your server routes requests to `registry.start()`, `registry.serve()`, or `registry.handler()` correctly.
- No middleware is modifying the request or response body.

### `serverless_destination_blocked`

@the-company-company the-company-company Bot Sep 10, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Low · The troubleshooting page repeats the same error section

This adds a second identical serverless_destination_blocked heading and remediation immediately after the first one. Readers see the same error twice, and the generated heading IDs/TOC acquire a redundant -1 entry. Keep a single section (the one at lines 100–106).


The configured serverless URL points at a destination Rivet is not allowed to reach. Rivet dials serverless endpoints from inside its own network, so by default it refuses any destination that is not publicly routable: private ranges, link-local and cloud metadata addresses, carrier-grade NAT, and other reserved ranges. Check that:

- Your endpoint URL is publicly reachable, and is not an internal hostname or address.
- The URL scheme is `http` or `https`, and the URL does not embed credentials.
- If you are self-hosting and intentionally point runners at an address on your own network, set `outbound.allow_private_networks` to `true` in your engine config, or list the specific range in `outbound.allow_cidrs`.

### `internal_error`

An unexpected error occurred within Rivet. If this persists, please [contact support](https://rivet.dev/actors/docs).
Expand Down
Loading
Loading