Skip to content

fix(alliance): fall back Digevo prod endpoint to LATAM West - #990

Merged
zortos293 merged 1 commit into
devfrom
fix/alliance-digevo-latam-west-fallback
Sep 19, 2026
Merged

zortos293 merged 1 commit into
devfrom
fix/alliance-digevo-latam-west-fallback

Conversation

@zortos293

Copy link
Copy Markdown
Collaborator

Summary

Digevo accounts could not get past provider routing: NVIDIA discovery (\pcs.geforcenow.com/v1/serviceUrls) still advertises \https://prod.DIG.geforcenow.nvidiagrid.net/\, but that hostname has no DNS records globally (NODATA/NXDOMAIN on every resolver tested, including with LATAM EDNS client subnets). Region discovery, VPC lookup, and all CloudMatch session routing for Digevo therefore failed.

This routes Digevo to the working regional endpoint \https://latam-west.dig.geforcenow.nvidiagrid.net/\ (server \NPA-DIG-SCL-01, region LATAM West) whenever discovery returns the stale prod host. The fallback stays within the existing HTTPS
vidiagrid.net\ trust policy; no protocol or ABI change.

Changes


  • ative/opennow-core/src/gfn.rs: new \effective_provider_url()\ / \provider_streaming_base(); Digevo stale-host fallback applied in discovery normalization, \provider_regions, \�pc_id, and session validation.

  • ative/opennow-core/src/cloudmatch.rs:
    equested_streaming_base()\ uses the effective provider URL.

  • ative/opennow-core/src/gfn/routing_tests.rs: new test for the fallback mapping and passthrough.

Verification

  • \cargo test -p opennow-core --bin opennow-core: 478 passed, 0 failed; \cargo fmt --check\ clean; no new clippy warnings.
  • Live end-to-end with real Alliance accounts at 1080p60 H264 (device login through browser, regions, subscription, library, launch inspect, session create/poll, NVST transport, first video frame):
    • Digevo (ULTIMATE): full loop incl. first frame, via both headless core and the Qt GUI in-process streamer.
    • GFN Korea (FREE): full loop incl. first frame after FREE queue cleared.

NVIDIA discovery still advertises https://prod.DIG.geforcenow.nvidiagrid.net/
for Digevo, but that hostname has no DNS records globally, so region
discovery, VPC lookup, and all CloudMatch routing for Digevo accounts
failed. Route Digevo to the working regional endpoint
https://latam-west.dig.geforcenow.nvidiagrid.net/ (server NPA-DIG-SCL-01,
region LATAM West), verified live with serverInfo, session list, session
create, and first video frame at 1080p60 H264.

The fallback stays within the existing HTTPS nvidiagrid.net trust policy;
no protocol or ABI change.
@coderabbitai

coderabbitai Bot commented Sep 19, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: fdd9158a-125f-428d-afdb-dc0f619fda40

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@zortos293
zortos293 merged commit e36c709 into dev Sep 19, 2026
8 checks passed
@zortos293
zortos293 deleted the fix/alliance-digevo-latam-west-fallback branch September 19, 2026 16:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant