Troubleshooting
This page covers common problems and how to resolve them. If your issue is not listed here, see the FAQ or report it on GitHub.
TLS and certificate errors
Section titled “TLS and certificate errors”If a request fails with a certificate error, the server is likely using a self-signed certificate or one issued by a certificate authority Vegha does not trust.
- For a custom internal CA, add it under Settings → Network so Vegha trusts certificates it issues.
- Avoid disabling SSL/TLS verification globally; trust the specific CA instead.
See Proxy and TLS for full configuration details.
Proxy problems
Section titled “Proxy problems”If requests time out or fail to connect on a corporate network, check the HTTP proxy configuration in Settings → Network. Make sure the proxy host and port are correct and that the proxy itself can reach the target host.
OAuth2 loopback and redirect issues
Section titled “OAuth2 loopback and redirect issues”OAuth2 flows often fail because the redirect URI is not registered. If a flow does not complete:
- Register the loopback redirect URI Vegha uses with your identity provider.
- Confirm that the local loopback port is not blocked by a firewall.
See OAuth2 for the full flow setup.
Import quirks
Section titled “Import quirks”Imported specs and collections do not always map one-to-one. After an import, review the generated requests for unmapped auth, variables, or body formats. See Importing overview for format-specific notes.
Where settings and logs live
Section titled “Where settings and logs live”Settings are stored per-user:
| OS | Location |
|---|---|
| Windows | %AppData%\Vegha |
| macOS | ~/Library/Application Support/Vegha |
| Linux | ~/.config/Vegha |
Resetting settings
Section titled “Resetting settings”To return Vegha to its defaults, close the app and delete the settings folder for your OS shown above. The next launch recreates it with default values.
Windows SmartScreen and macOS Gatekeeper
Section titled “Windows SmartScreen and macOS Gatekeeper”When you first launch a direct-download build, the operating system may warn that the app is from an unrecognized publisher:
- Windows SmartScreen — choose More info, then Run anyway.
- macOS Gatekeeper — open the app from System Settings → Privacy & Security, or right-click the app and choose Open.
Microsoft Store and Mac App Store builds are signed and distributed by the store, so these prompts do not appear.