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.

Sign up for GitHub

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

Jump to bottom

Cannot start using beacon address with domain path #18293

Closed
rayn316 opened this issue Oct 24, 2024 · 1 comment · Fixed by #18295
Closed

Cannot start using beacon address with domain path #18293

rayn316 opened this issue Oct 24, 2024 · 1 comment · Fixed by #18295
Assignees
@YoGhurt111 @mask-pp
Labels
area.client

Comments

@rayn316
Copy link

rayn316 commented Oct 24, 2024

Describe the bug

mainnet node
When using parameters to specify beacon, this error occurs when starting.

/node/archive/taiko/bin/taiko-client driver --l1.beacon http://xxx.xxx/ethereum/beacon

Oct 24 16:43:59 taiko-client[1007123]: ERROR[10-24|16:43:59.808] Failed to connect to L1 beacon endpoint, retrying endpoint=http://xxx.xxx/ethereum/beacon err="error requesting configSpecPath: code=404, url=http://xxx.xxx/eth/v1/config/spec, body=response body:\n<html>\r\n<head><title>404 Not Found</title></head>\r\n<body>\r\n<center><h1>404 Not Found</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n: recv 404 NotFound response from API: did not receive 2xx response from API"

Steps to reproduce

Steps to reproduce here.
@YoGhurt111 YoGhurt111 mentioned this issue Oct 24, 2024
Merged
@YoGhurt111 YoGhurt111 linked a pull request Oct 24, 2024 that will close this issue
fix(taiko-client): fix path parsing in /eth/v1/config/spec #18295
Merged
@davidtaikocha
Copy link
Member

Should have been fixed in v0.39.2, plz give a try.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@YoGhurt111 YoGhurt111

@mask-pp mask-pp

Labels
area.client
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(taiko-client): fix path parsing in /eth/v1/config/spec taikoxyz/taiko-mono
4 participants
@YoGhurt111 @rayn316 @mask-pp @davidtaikocha