Connection Troubleshooting

Stash Mac DoH fails: fix in 5.0.0

Stash Mac DoH failing? Check HTTP/1.1-only upstreams, caches and DNS routing; back up, update to 5.0.0 (607), then verify fresh queries and recovery.

  • Stash
  • macOS
  • DoH
  • DNS
  • 5.0.0
On this page

Your proxy appears usable, but a custom DoH resolver fails; another DNS server works. Save the current configuration and the first error. Do not simultaneously switch proxy nodes, edit rules or disable certificate verification.

Confirm which DoH query is failing in native Stash Mac

This guide is for users of native Stash Mac who manage their own YAML, know which configuration is active and can keep a recoverable copy. It addresses compatibility with a DoH upstream that supports only HTTP/1.1.

The official Mac update feed for 5.0.0 (build 607) says that Stash uses HTTP/1.1 when the server does not support HTTP/2. This does not fix every DNS failure, and a version number from another platform cannot establish which Mac application you are running.

First check the upstream provider’s protocol documentation or server connection records to establish whether it supports only HTTP/1.1. Opening the DoH URL in a browser tells you about that browser request. It does not prove that Stash completed a DNS query or establish which HTTP versions the upstream supports.

Start with the stage that fails

What you observeWhat to check first
The same custom DoH upstream fails while another known working resolver succeedsCheck the target upstream’s protocol support and the actual query path
The proxy server’s own hostname cannot be resolvedCheck proxy-server-nameserver and the bootstrap resolution path separately
A connection times out or certificate verification failsCheck this upstream’s network path, address and certificate before attributing the failure to HTTP/1.1 compatibility
Websites still open, but no new DNS query is visibleCached answers may mask the result; this does not prove the target upstream works

Keep the original configuration and check the DNS path in a copy

Save the complete YAML you are using, your overrides and the original proxy selection. Keep the original configuration available to restore. Do not edit your only managed configuration or depend on cloud data whose recovery you have not confirmed; use a copy you control for this test.

When nameserver contains several upstreams, Stash queries them concurrently and uses the fastest response. Another upstream’s success may hide a continuing failure at the target DoH server. nameserver-policy and fallback can also change which resolver is used.

Enabled overrides may merge other upstreams back in: arrays are prepended by default. Check the effective nameserver list rather than relying on the original YAML text alone.

For a controlled comparison, temporarily keep only the original target DoH upstream under nameserver in the copy’s existing dns block. Choose a test domain that nameserver-policy or fallback will not redirect, and confirm that this copy is active. Stop editing if you cannot establish the actual path; a mixed result does not validate a single upstream.

Record the original follow-rule setting. By default, DNS requests do not follow proxy rules. If it is enabled, also check the connection rules and bootstrap resolution for the DNS upstream to avoid recursion. proxy-server-nameserver has a separate query path for proxy server hostnames; its success does not prove that nameserver resolved an ordinary destination domain.

Change only the upstream list needed for this comparison. Keep follow-rule, the proxy node and traffic capture mode unchanged, and do not treat forcing another HTTP transport as this fix. Do not disable TLS certificate verification merely to obtain an apparent success.

Update the native Mac application and keep the same DoH upstream

Compare before and after with the same configuration copy

  1. Record the application version and original failure

    Check the version and build of the native Stash Mac application that is actually running. Save the target DoH address, relevant DNS settings and a redacted error. A store page, subscription name or version on another device is not enough.

  2. Quit normally and update the native application

    First confirm that your system and license support the target version. When you can interrupt the current network session, stop and quit the application normally, then obtain the 5.0.0 (607) fix through the official native Mac update channel. If you cannot update, restore a working setup as described below. Keep your data and configuration; do not install old packages from unknown sources or substitute a core-file replacement for the full application update.

  3. Select the original test configuration again

    After reopening the application, verify the actual version and build, select the saved test copy, then start it in the same way as before. Keep the target DoH server, proxy node and rules unchanged. If configuration validation or application startup fails, address that stage first.

  4. Restore a working setup if you cannot update

    Switch back to the original configuration and an encrypted DNS upstream you previously verified works. Keep the failure record and test copy for the same comparison when an update becomes possible. Temporarily changing upstreams does not mean the compatibility issue is fixed.

This guide checks the official fix in 5.0.0 (607). If you later use a different version, check its release channel and evidence that it includes the same fix. Do not downgrade merely to match this version number; official channels are not guaranteed to offer every historical version.

Confirm a fresh query, then test real access

Stash caches DNS answers and may continue using an expired answer while refreshing it in the background. Reopening an old website, passing one latency test or simply waiting does not by itself prove the target DoH upstream has recovered.

Using a test domain you control and logs you are allowed to access, confirm that a new DNS query actually occurred and used the target DoH server. If you administer the upstream, its request records can help. Mark the check as unverified if you cannot establish a fresh query or the actual upstream; do not invent a successful result. Then initiate a new connection that needs this domain and confirm that the actual website or service is accessible.

Verification checklist

  • You are running native Stash Mac with the fix and have checked its version and build.
  • The test configuration, target DoH server and original proxy node are identified, and no other DNS path redirects the test domain.
  • A new query reached the target upstream rather than only reusing a cached answer.
  • The relevant resolution errors have stopped, and a new service connection that depends on the domain works.
  • After restoring the required normal configuration, you have checked again and can still return to the original configuration and working upstream.

These diagnostic and recovery suggestions are based on the official Mac update feed and DNS documentation. We have not reproduced the failure on your network or in a real Stash client. Checks of this website’s five languages, source and browser behavior are not device-level DoH or service connection tests.

If it still fails, restore the original configuration and follow the first error

The target DoH server still times out or reports a certificate error after updating

Restore the original configuration and known working encrypted DNS. Check the target address, reachability, certificate and provider status. Do not attribute every network error to protocol compatibility or disable certificate verification.

The proxy server’s hostname also fails to resolve after changing configurations

Return to the original configuration first. Check proxy-server-nameserver, bootstrap resolution of the DNS upstream’s hostname and the original follow-rule setting. Restore the previous working path rather than adding more DNS or routing changes at the same time.

The test works, but restoring the normal configuration brings the failure back

Check nameserver-policy, fallback and the effective settings after overrides, one item at a time. Keep the single-upstream test and original configuration for comparison. A different upstream’s success or a cache hit does not prove that the target DoH server keeps working.

The application cannot start or configuration validation fails

Restore the original working configuration and stop stacking changes. Save the application version, validation error and actions taken, then seek help for that failure stage. Do not delete your only data directory or rely on an unconfirmed older-version rollback.

When asking for help, include macOS, the Stash Mac version and build, evidence of the upstream’s protocol support, a redacted DNS fragment, the first error and the fresh-query verification result. Hide any token-bearing DoH URL, subscription addresses and private domains. Keep complete original records for your own recovery.

References