Closed techdixie closed 1 month ago
Hey, I see that you changed the container name of chrome to hoarder_chrome
, in that case, you'll need to change the BROWSER_WEB_URL
to http://hoarder_chrome:9222
I'm wondering if my container rename is messing more than that up. I'll remove those. I'm not getting tagging, homepage now says "Something went wrong". The app says its failing at crawling.
ok, this corrected ai tagging and the crawlers. Only thing that looks like its not working is the homepage that says "Something went Wrong"
Can you share the logs of the web container?
hoarder-web-1 | at async d (/app/apps/web/.next/server/chunks/624.js:4:32967) hoarder-web-1 | at async p (/app/apps/web/.next/server/chunks/624.js:4:33306) hoarder-web-1 | at async p (/app/apps/web/.next/server/app/dashboard/bookmarks/page.js:1:10468) { hoarder-web-1 | issues: [ [Object] ], hoarder-web-1 | addIssue: [Function (anonymous)], hoarder-web-1 | addIssues: [Function (anonymous)], hoarder-web-1 | errors: [ [Object] ] hoarder-web-1 | } hoarder-web-1 | } hoarder-web-1 | [Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] { hoarder-web-1 | digest: '2631817619' hoarder-web-1 | } hoarder-web-1 | m [TRPCError]: Output validation failed hoarder-web-1 | at p (/app/apps/web/.next/server/chunks/624.js:4:32429) hoarder-web-1 | at async d (/app/apps/web/.next/server/chunks/624.js:4:32967) hoarder-web-1 | ... 4 lines matching cause stack trace ... hoarder-web-1 | at async p (/app/apps/web/.next/server/app/dashboard/bookmarks/page.js:1:10468) { hoarder-web-1 | code: 'INTERNAL_SERVER_ERROR', hoarder-web-1 | [cause]: o [ZodError]: [ hoarder-web-1 | { hoarder-web-1 | "code": "invalid_type", hoarder-web-1 | "expected": "string", hoarder-web-1 | "received": "undefined", hoarder-web-1 | "path": [ hoarder-web-1 | "bookmarks", hoarder-web-1 | 2, hoarder-web-1 | "content", hoarder-web-1 | "url" hoarder-web-1 | ], hoarder-web-1 | "message": "Required" hoarder-web-1 | } hoarder-web-1 | ] hoarder-web-1 | at get error [as error] (/app/apps/web/.next/server/chunks/917.js:63:14269) hoarder-web-1 | at Q.parseAsync (/app/apps/web/.next/server/chunks/917.js:63:16752) hoarder-web-1 | at async p (/app/apps/web/.next/server/chunks/624.js:4:32378) hoarder-web-1 | at async d (/app/apps/web/.next/server/chunks/624.js:4:32967) hoarder-web-1 | at async d (/app/apps/web/.next/server/chunks/624.js:4:32967) hoarder-web-1 | at async d (/app/apps/web/.next/server/chunks/624.js:4:32967) hoarder-web-1 | at async d (/app/apps/web/.next/server/chunks/624.js:4:32967) hoarder-web-1 | at async p (/app/apps/web/.next/server/chunks/624.js:4:33306) hoarder-web-1 | at async p (/app/apps/web/.next/server/app/dashboard/bookmarks/page.js:1:10468) { hoarder-web-1 | issues: [ [Object] ], hoarder-web-1 | addIssue: [Function (anonymous)], hoarder-web-1 | addIssues: [Function (anonymous)], hoarder-web-1 | errors: [ [Object] ] hoarder-web-1 | } hoarder-web-1 | }
@techdixie did you figure this out?
Mine works perfectly now, but I did nothing to fix it unless there was an update at some point. Sorry I can't be of more assistance.
closing as it works now
hoarder_workers | 2024-08-23T19:24:44.650Z error: [Crawler] Failed to connect to the browser instance, will retry in 5 secs hoarder_workers | 2024-08-23T19:24:49.651Z info: [Crawler] Connecting to existing browser instance: http://chrome:9222
I was getting some errors so I upgraded to the latest release. Now I am getting a Crawler error. I haven't touched chrome. I am not using kubernetes.
`services: web: image: ghcr.io/hoarder-app/hoarder-web:latest container_name: hoarder_web restart: unless-stopped volumes:
Thanks! (edit: no clue how to keep formatting :/)