L3dgr Support

Export a support bundle from the L3dgr Docker extension, then contact the right Fors33 mailbox or submit the form below. Do not paste API keys, file paths, or production secrets in email.

Support Bundle What to Include Hosted Continuity Contact Submit Request

Export a support bundle

Start in Docker Desktop. The bundle is l3dgr_support_bundle_v1 JSON with extension version, Docker Desktop OS, tier, preflight summary, and Readout export text. It does not include raw emails, file paths, or hashes.

  1. Open the L3dgr extension in Docker Desktop.
  2. Go to Settings → Help & Support.
  3. Select Run Preflight and resolve any blocking items when possible.
  4. Select Download Support Bundle to export the JSON file.
  5. Attach the file to your email, or paste its contents in the form below.

What to include

Attach the bundle when you have it. Add only what the bundle does not already capture.

Bundle or Readout

Support bundle JSON is preferred. Otherwise include a Readout excerpt with Job ref: when available.

Environment

Extension version and Docker Desktop OS or build (also in the bundle when exported).

License tier

Pro, Lab, institution, or L3dgr Beta cohort, plus a short description of the issue.

Reproduction

Steps to reproduce, expected behavior, and actual behavior.

Fors33 Relay / Hosted Continuity

Hosted Continuity runs promoted L3dgr releases on Fors33 Relay. Identify your plan mode first so we can triage quickly. Check service status for the portal API and Fors33 Relay plane before you write in. Product overview: L3dgr.

Paid Burst or Always

This L3dgr Beta wave does not include a complimentary Burst perk. Confirm Plans and Billing for paid Fors33 Relay entitlements. Cohort questions: l3dgr-beta@fors33.com. Promote, demote, or meter defects: use program Fors33 Relay / Hosted Continuity below.

Burst

Event-scoped relay with an approximate eight-hour window per promotion. Include whether the issue is promote, demote, meter reporting, or stream delivery during the burst.

Always

Continuous relay entitlement with included stream capacity. Include whether relay is stuck promoted, regulated unattended behavior, or spool retention after demote.

In your message, include release_id, whether you are on Burst or Always, the approximate time window (UTC if possible), and Job ref when the Readout shows one. Do not paste API keys, file paths, spool payloads, or production secrets.

Billing, meter usage, and relay entitlements are in the account portal under Plans and Billing (Stripe). For invoice or subscription questions, start there before opening a support thread.

Contact

L3dgr Beta

Cohort participants: l3dgr-beta@fors33.com

General

Product and routing: support@fors33.com

Beta Resources

Bug template and known issues

Hosted Continuity

Fors33 Relay promote, demote, and meter issues: support@fors33.com

Billing

Relay usage and seats: Plans and Billing

We route L3dgr Beta requests to l3dgr-beta@fors33.com. Fors33 Relay / Hosted Continuity (Burst or Always) goes to support@fors33.com with program Fors33 Relay / Hosted Continuity in the form below. All other L3dgr issues also go to support@fors33.com.

Submit a request

Prefer the form when you already have a support bundle. Select your program so we route to the correct mailbox.