Skip to content

failure on the scrape #5

Description

@mrman486

Loving degoog so far so I thought I would give the mcp a go.

the search works, however when the llm tries to go deeper I am seeing this

example from the log

degoog-mcp-1 | 2026-06-26 09:30:19 [INFO ] search: q="ASX200 index today June 26 2026" type="web" page=1 time="" lang="" engines=[] max=5
degoog-mcp-1 | 2026-06-26 09:30:20 [INFO ] degoog: ok q="ASX200 index today June 26 2026" type="web" engines=0 hits=5 capped=10 took=1003ms
degoog-mcp-1 | 2026-06-26 09:38:45 [INFO ] scrape: dispatching 1 url(s)
degoog-mcp-1 | 2026-06-26 09:38:46 [WARN ] scraper: fetch url=https://www.asx200.com/search?q=ASX200: Get "https://www.asx200.com/search?q=ASX200": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-06-26T09:38:46Z is after 2024-07-16T23:59:59Z
degoog-mcp-1 | 2026-06-26 09:38:46 [WARN ] scraper: failed url=https://www.asx200.com/search?q=ASX200 reason=fetch: Get "https://www.asx200.com/search?q=ASX200": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-06-26T09:38:46Z is after 2024-07-16T23:59:59Z

Seems the date is wrong from somewhere. I am connected to llama.cpp so I am unsure if that is pushing the wrong date or the mcp docker is wrong.

Thank you

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions