Grep Badger logoGrep Badger
← Back to docs

Troubleshooting

If something is not working as expected, these quick checks can help you narrow down the problem.

1. Cannot connect to an SSH host

Double-check:

  • host name or IP address
  • username
  • port
  • password or private key path
  • whether SSH access is enabled on the remote machine

If you are using a private key, make sure it matches the server and user you are connecting with.

If you are using Auto authentication and it does not behave as expected, try switching to Password or Private Key directly.

2. The app keeps asking for my password

Linux may not remember your passwords due to missing credential stores.

If the app cannot save your password or passphrase, it will prompt you when you connect.

In that case, Grep Badger holds the secret in memory for your session only and prompts you again next session.

3. A remote log feels slow

Remote log files are streamed through SSH/SFTP.

Performance may be affected by:

  • network speed
  • network latency
  • remote system load
  • file size

Very large files may take a moment to load, especially over a remote connection.

If you have issues streaming through SSH/SFTP, we recommend pulling the log locally first.

4. Tailing does not seem live

A short delay is normal when new lines are written.

If the log is not updating as expected:

  • make sure tailing is not paused
  • try Load Latest
  • confirm the file is still being written to
  • for remote files, confirm the SSH connection is still healthy

If you used chunk navigation, tailing will pause until you start it again.

5. Go to line is not exact

Grep Badger streams logs in chunks rather than loading the full file directly into memory.

Because of this, line numbers are estimated.

When using Go to a line, treat it as a ballpark rather than a definitive position.

6. AI is not working

Check the following:

  • your AI provider is enabled
  • the correct provider is selected
  • a valid model is selected
  • Ollama is installed and running if you are using Ollama
  • your API key and provider settings are correct if you are using OpenAI or Anthropic

If a provider or model is not available, Grep Badger will not be able to send your message.

7. AI responses are not useful

Try:

  • selecting the most relevant log lines
  • sending a more specific prompt
  • reducing unrelated context
  • asking focused questions about a single error or event
  • selecting a different model

Smaller, more relevant context often produces better results than sending too much log data at once.

8. The file I want is hard to reopen

If you plan to return to the same log later, save it to Quick Access.

Quick Access helps you reopen important logs without browsing through the file explorer again.

Tabs do not persist after closing the app.

Important notes

  • Local and remote logs are streamed rather than fully loaded into memory.
  • Very large files may affect performance.
  • Remote file access depends on SSH/SFTP connectivity.
  • External AI providers will see any data you send to them. Never send secrets unless you fully understand and accept that provider's data handling practices.