Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Firecrawl doesn´t work, have to check api key, but key is correct #288

Open
2 of 6 tasks
Japhys opened this issue Sep 22, 2024 · 1 comment
Open
2 of 6 tasks

Firecrawl doesn´t work, have to check api key, but key is correct #288

Japhys opened this issue Sep 22, 2024 · 1 comment
Labels
investigating Bugs that are still being investigated whether they are valid

Comments

@Japhys
Copy link

Japhys commented Sep 22, 2024

Description

Signed up for firecrawl. Started off with a free plan to try it out. Got an api key.
In docker compose I added:

  - FIRECRAWL_API_KEY=&FIRECRAWL_API_KEY

In .env file

  - FIRECRAWL_API_KEY=the actualkey from the firecrawl website

When I try to crawl a site I get an error straight away

Import for website failed: Reader Firecrawl failed with: Firecrawl was not able to load any documents, please check your API Key and settings

I should be able to do this with the free 500 credits. It's a site with only a 100 pages or so.

There is no way of setting the key via GUI for firecrawl right? Like you can for OpenAI and Cohere.

btw import from pdf in combination with OpenAI api key does work.

Installation

  • pip install goldenverba
  • pip install from source
  • Docker installation

Weaviate Deployment

  • Local Deployment
  • Docker Deployment
  • Cloud Deployment

Configuration

Reader: Firecrawl
Chunker: Sentence
Embedder: OpenAI (this key do work!)
Retriever: Advanced
Generator: OpenAI

Steps to Reproduce

Whenever I click import selected I get an error straight away. But the key is correct.

Additional context

@thomashacker
Copy link
Collaborator

Thanks for the issue! I'll try to reproduce it
If you set environment variables through the .env and Verba detects them on startup, they won't be shown to the UI, but I might change this so that you can always edit those.

I'll let you know once we have an update on this 🚀

@thomashacker thomashacker added the investigating Bugs that are still being investigated whether they are valid label Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
investigating Bugs that are still being investigated whether they are valid
Projects
None yet
Development

No branches or pull requests

2 participants