Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- Separate a missing menu item from a failed API request.
- Update the app and confirm the active account and workspace.
- Network checks cover connectivity, not eligibility or UI rollout.
- Share only redacted version, reproduction, and timing details; never include tokens or hidden identifiers.
Separate a missing menu option from a failed request
If the app opens but a reasoning option is absent from the model picker, classify the symptom as a missing visible menu item. That differs from a timeout, authentication failure, or an unavailable API model. Reachability or HTTP 200 proves only that one request reached an endpoint; it does not prove that the desktop UI should display an option.
Record the app name, version, operating system, account workspace, and observation time. Do not include an email address, organization ID, access token, internal endpoint, or hidden feature identifier.
Update the app and confirm the active account context first
Check for an app update through the official channel, then fully quit and reopen it. Confirm the version and signed-in state. If you use personal and organizational workspaces, verify which context is active and reopen the picker after switching. Do not clear the entire user profile or delete session files just to refresh the list.
Visibility can depend on product version, account access, organization controls, or a staged rollout. This guide does not infer eligibility or provide a way around access checks. Confirm current scope with official help or an organization administrator.
Check whether the app is offline before changing network settings
If other screens and ordinary requests work while one menu entry is missing, connectivity is not the first established cause. Check whether the system proxy, app network settings, DNS, or enterprise TLS inspection changed recently. Observe one factor at a time; do not disable certificate checks or security software as a test.
A Windows WinHTTP proxy query shows WinHTTP configuration; it may not match the proxy used by a desktop app. Keep output local because a proxy address can reveal internal network details. Test only hosts listed in current official network requirements.
Read the Windows WinHTTP proxy
powershellnetsh winhttp show proxy
Verify each layer through the official UI and status information
Check the app version, active workspace, current model picker, service-status page, and organization controls in that order. If one account sees an option and another does not, ask an administrator to confirm access or rollout scope. If many users see errors, check official service status and app updates. Do not substitute an undocumented API, header, model ID, or hidden switch for the product UI.
A successful API request proves only that it succeeded under its own permissions and endpoint. It does not prove that the desktop UI has the same capability or that the picker should list the same name. Track UI verification, account access, and reachability as separate evidence.
Prepare minimal, redacted support details
If the option is still missing, prepare the app version, OS version, reproduction steps, workspace type, and time observed. Hide profile details, email, organization name, and notifications before taking screenshots. Share only diagnostics requested through official support, with tokens, full request headers, internal hostnames, and local paths removed.
Do not edit client files to add hidden models or guess feature switches. Wait for support or an administrator to confirm account scope, rollout, and version behavior, then follow public guidance. Recheck the same picker after each change; an API response is not proof that the UI was fixed.
Sources
Frequently Asked Questions
Why is the option still missing when an API request returns HTTP 200?
API access and the desktop UI capability list are separate layers. A successful request does not confirm account access, UI rollout, or picker data refresh.
Should I enable hidden settings or add a model ID manually?
No. Use only public product settings and current official guidance. Do not guess hidden switches or edit client files.
Does a proxy query prove the app network settings are correct?
No. Windows WinHTTP configuration may not be the proxy used by the app. Check the app’s public network settings and current official requirements separately.