Skip to main content

Common Issues

Solutions to common problems you might encounter while using Nidra.

Installation Issues​

Windows: Application Won't Start​

Symptoms: Double-clicking the executable does nothing or shows an error.

Solutions:

  1. Run as Administrator:

    • Right-click the executable
    • Select "Run as administrator"

  2. Check Windows Defender:

    • Windows may block unknown applications
    • Go to Windows Security > Virus & threat protection
    • Allow the application

  3. Install Visual C++ Redistributables:

    • Download from Microsoft
    • Install both x64 and x86 versions

  4. Check Event Viewer:

    • Look for error details in Windows Event Viewer

macOS: "App is Damaged" Error​

Symptoms: macOS says the app is damaged or can't be opened.

Solutions:

  1. Remove Quarantine Flag:

    xattr -cr /Applications/Nidra.app

  2. Allow in Security Settings:

    • System Preferences > Security & Privacy
    • Click "Open Anyway"

  3. Re-download:

    • Delete the current download
    • Download again (may have been corrupted)

Linux: Permission Denied​

Symptoms: Cannot execute the AppImage.

Solutions:

  1. Make Executable:

    chmod +x Nidra-*.AppImage

  2. Check Dependencies:

    ldd Nidra-*.AppImage

    Install any missing libraries.

  3. FUSE Issues:

    • Install FUSE: sudo apt install fuse libfuse2
    • Or extract: ./Nidra-*.AppImage --appimage-extract
    • Run: ./squashfs-root/AppRun

Request Issues​

Request Fails with Network Error​

Symptoms: "Network Error", "Connection Refused", or timeout.

Solutions:

  1. Check URL:

    • Verify the URL is correct
    • Ensure protocol (http/https) is correct
    • Check for typos

  2. Check Internet Connection:

    • Test with browser
    • Ping the server: ping api.example.com

  3. Proxy Settings:

    • Check if behind a proxy
    • Configure proxy in Settings > Network

  4. Firewall:

    • Firewall may be blocking Nidra
    • Add exception for Nidra

  5. VPN Issues:

    • VPN may interfere
    • Test with VPN off

  6. DNS Issues:

    • Try IP address instead of domain
    • Check DNS resolution: nslookup api.example.com

SSL/TLS Certificate Errors​

Symptoms: "Certificate verification failed", "SSL error"

Solutions:

  1. Self-Signed Certificates:

    • Settings > SSL > Disable certificate verification (development only)
    • Or add certificate to system trust store

  2. Expired Certificates:

    • Contact API provider
    • Check server configuration

  3. Hostname Mismatch:

    • Verify URL matches certificate
    • Check for redirects

401 Unauthorized Errors​

Symptoms: Request returns 401 status code.

Solutions:

  1. Check Authentication:

    • Verify credentials are correct
    • Check token hasn't expired
    • Ensure header name is correct

  2. Environment:

    • Verify correct environment selected
    • Check variable resolution

  3. Token Expiration:

    • Refresh authentication token
    • Check token expiry time

  4. Permissions:

    • Verify account has required permissions
    • Check API key scope

Request Body Not Sent​

Symptoms: Server doesn't receive body data.

Solutions:

  1. Content-Type Header:

    • Add: Content-Type: application/json
    • Or appropriate type for your data

  2. HTTP Method:

    • GET requests typically don't have bodies
    • Use POST, PUT, or PATCH

  3. Body Format:

    • Verify JSON is valid
    • Check for syntax errors

Variable Issues​

Variables Not Resolving​

Symptoms: Variables show as {{varName}} in requests/responses.

Solutions:

  1. Check Variable Name:

    • Verify spelling (case-sensitive)
    • No spaces or special characters (unless supported)

  2. Check Scope:

    • Ensure variable exists in active environment
    • Or in global/collection scope

  3. Environment Selection:

    • Verify environment is selected
    • Check environment dropdown

  4. Variable Syntax:

    • Use {{varName}} not {varName} or $varName

Extracted Variables Not Available​

Symptoms: Can't use extracted variable in subsequent steps.

Solutions:

  1. Check Extraction Path:

    • Verify JSON path is correct
    • Test with actual response data

  2. Step Order:

    • Extraction must be in earlier step
    • Variables not available in same step

  3. Step Execution:

    • Ensure extraction step executed successfully
    • Check for errors in step

  4. Variable Name:

    • Check for typos
    • Verify it's saved with expected name

Conduit Issues​

Conduit Fails Immediately​

Symptoms: Conduit stops on first step.

Solutions:

  1. Check First Step:

    • Run step manually
    • Check request configuration

  2. Variable Dependencies:

    • Ensure required variables exist
    • Check variable resolution

  3. Network Issues:

    • Check internet connection
    • Verify server is accessible

Assertions Always Fail​

Symptoms: Assertions fail despite response looking correct.

Solutions:

  1. Check Data Types:

    • String "42" vs number 42
    • Boolean true vs string "true"

  2. Field Path:

    • Verify path is correct: data.user.id not user.id
    • Check for typos

  3. Response Structure:

    • View actual response
    • Response may differ from expected

  4. Case Sensitivity:

    • Field names are case-sensitive
    • userId ≠ userid

Environment Issues​

Parent Environment Variables Not Inherited​

Symptoms: Child environment doesn't have parent's variables.

Solutions:

  1. Check Parent Selection:

    • Verify parent is selected in child settings
    • Save child environment after setting parent

  2. Restart Application:

    • Close and reopen Nidra
    • Re-select environment

  3. Variable Scope:

    • Check if overridden in child
    • Verify parent has the variable

Performance Issues​

Application is Slow​

Symptoms: Nidra is sluggish or unresponsive.

Solutions:

  1. Too Many Collections:

    • Archive unused collections
    • Organize into workspaces

  2. Large Responses:

    • Limit response size
    • Paginate large requests

  3. Memory Usage:

    • Restart Nidra
    • Close unused tabs
    • Check system resources

  4. Database Corruption:

    • Export collections
    • Clear application data
    • Re-import collections

Requests are Slow​

Symptoms: Requests take longer than expected.

Solutions:

  1. Check Server:

    • Test with browser or curl
    • Server may be slow

  2. Network:

    • Check internet speed
    • Test without VPN

  3. Proxy:

    • Disable proxy if not needed
    • Use direct connection

Sync Issues​

Team Sync Not Working​

Symptoms: Changes don't sync to team members.

Solutions:

  1. Check Internet:

    • Verify connection
    • Test other network features

  2. Login Status:

    • Ensure logged in
    • Re-authenticate if needed

  3. Permissions:

    • Verify team membership
    • Check collection permissions

  4. Manual Sync:

    • Force sync: Right-click > Sync Now

Sync Conflicts​

Symptoms: Conflict resolution dialog appears frequently.

Solutions:

  1. Communicate:

    • Coordinate with team
    • Work on different areas

  2. Sync Often:

    • Pull changes before editing
    • Push changes immediately after

  3. Resolve Carefully:

    • Review both versions
    • Choose appropriate resolution

Import/Export Issues​

Import Fails​

Symptoms: Can't import Postman/Swagger file.

Solutions:

  1. Verify Format:

    • Ensure file is valid JSON/YAML
    • Check file is not corrupted

  2. Version:

    • Postman v2.1 supported
    • OpenAPI 3.0 supported
    • Update export if older version

  3. File Size:

    • Very large files may fail
    • Split into smaller collections

Exported File Missing Data​

Symptoms: Export doesn't include all data.

Solutions:

  1. Export Options:

    • Check "Include environments"
    • Select appropriate options

  2. Format Limitations:

    • Some formats don't support all features
    • Use Nidra format for full fidelity

Data Loss Prevention​

Request/Collection Disappeared​

Symptoms: Can't find previously saved request.

Solutions:

  1. Check Filters:

    • Clear search filters
    • Show all collections

  2. Check Collection:

    • May be in different collection
    • Use global search

  3. Sync Issues:

    • Check sync status
    • Force sync if using Team Sync

  4. Restore from Backup:

    • Check auto-backups (if enabled)
    • Import from export

Getting Help​

If you can't resolve your issue:

  1. Check Documentation:

    • Search this documentation
    • Review relevant tutorials

  2. Check GitHub Issues:

  3. Report Bug:

    • Use Help > Report Bug in Nidra
    • Include error details and steps to reproduce

  4. Community:

    • Check discussions
    • Ask for help

Diagnostic Information​

When reporting issues, include:

  • Nidra version
  • Operating system and version
  • Error messages (exact text)
  • Steps to reproduce
  • Screenshots if applicable

Get Version:

  • Help > About Nidra

Export Logs:

  • Help > Export Logs
  • Attach to bug report

See Also​