Troubleshooting Wisec Integration

This section provides solutions to common issues you might encounter while integrating and using Wisec.

---

1. Dashboard shows "Failed to load dashboard data." or is empty/broken after login.

Problem: You can log in, but the dashboard doesn't display correctly, showing loading spinners, error messages, or missing content.

Possible Causes & Solutions:

• API Connection Issue:

  • Symptom: Your browser console shows network errors when trying to reach https://app.wisec.io/api/v1/....

  • User Action:

    1. Verify the application URL: Ensure you are accessing the Wisec dashboard from the correct URL: https://app.wisec.io.

    2. Check for DNS issues: Ensure your DNS record for app.wisec.io is correctly pointing to the IP address provided during deployment. DNS changes can sometimes take time to propagate.

    3. Clear Browser Cache: Old settings can sometimes interfere. Try clearing your browser's cache or using an incognito/private window.

---

2. Agent pipeline fails with "Failed to decode private key..."

Problem: Your CI/CD pipeline job running the Wisec agent fails with an error message similar to Failed to decode private key from AGENT_PRIVATE_KEY_HEX: encoding/hex: invalid byte: U+005F '_'.

Possible Causes & Solutions:

• Incorrect Private Key Format:

  • Symptom: The error specifically mentions "invalid byte" and points to AGENT_PRIVATE_KEY_HEX.

  • User Action:

    1. Go to your Wisec dashboard's Settings page.

    2. In the "Agent Signing Keys" section, click "Generate New Signing Key".

    3. Copy the displayed privateKey (which will be a long hexadecimal string).

    4. Update the AGENT_PRIVATE_KEY_HEX variable in your CI/CD pipeline's settings with this correct private key. Ensure it's treated as a secret/masked variable.

---

3. Agent pipeline fails with "Project not found" or 404 Not Found for event submission.

Problem: The Wisec agent fails to submit events to the API Gateway, reporting "Project not found" or a 404 error.

Possible Causes & Solutions:

• Incorrect WISEC_PROJECT_ID:

  • Symptom: The error message indicates the project could not be found.

  • User Action: Verify the WISEC_PROJECT_ID in your CI/CD variables matches the ID displayed on your Wisec dashboard's "Projects" page.

• Incorrect WISEC_API_ENDPOINT:

  • Symptom: The agent cannot reach the API endpoint, possibly with a "connection refused" or "not found" error.

  • User Action:

1. Ensure the WISEC_API_ENDPOINT in your CI/CD variables is set correctly to https://app.wisec.io/api/v1/events. 2. Check for any network policies or firewalls in your CI/CD environment that might be blocking outbound traffic to app.wisec.io.

---

4. Dashboard shows "No dashboard data available for the selected period." even with projects.

Problem: You have created projects, but the dashboard still shows a message indicating no data is available, even if the application is otherwise healthy.

Possible Causes & Solutions:

• No Events Pushed Yet:

  • Symptom: Projects exist, but no pipeline runs are reflected on the dashboard.

  • User Action: Ensure your CI/CD pipeline with the Wisec agent is configured correctly and has executed at least once for a project. Check your CI/CD job logs for successful event submission messages from the Wisec agent.

• Incorrect Time Filter:

  • Symptom: You believe events should be visible, but the dashboard remains empty.

  • User Action: Try setting the time filter on the dashboard to "All Time" to see if any historical data is present.

---

5. "Copy" button for API Keys/Signing Keys does not work.

Problem: Clicking the "Copy" button for API Keys or Signing Keys in the Settings page does not copy the key to your clipboard.

Possible Causes & Solutions:

• Browser/UI Interference:

  • Symptom: Clicking the button has no effect.

  • User Action: The copy functionality relies on modern browser APIs that work best in secure (HTTPS) contexts. Now that the application is served over HTTPS, this should work correctly. If it still fails, try a different browser or disable any extensions that might interfere with clipboard access. If all else fails, you can always manually select the key text and copy it.