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

obanSocket error unable to verify the first certificate #418

Closed
Dorus opened this issue Apr 18, 2024 · 5 comments
Closed

obanSocket error unable to verify the first certificate #418

Dorus opened this issue Apr 18, 2024 · 5 comments

Comments

@Dorus
Copy link
Contributor

Dorus commented Apr 18, 2024

Since yesterday my bots are crashing with the error

�[33mApr 17 18:26:02   main.ts:143          Disconnected from server�[39m
�[32mApr 17 18:26:02   GobanSocket.ts:289   GobanSocket reconnecting in 50ms�[39m
�[31m�[1mApr 17 18:26:02 ! GobanSocket.ts:206   GobanSocket error unable to verify the first certificate�[22m�[39m
�[33mApr 17 18:26:02   GobanSocket.ts:217   GobanSocket closed with code 1006: Abnormal Closure�[39m
�[33mApr 17 18:26:02   main.ts:143          Disconnected from server�[39m
�[32mApr 17 18:26:02   GobanSocket.ts:289   GobanSocket reconnecting in 258ms�[39m
�[31m�[1mApr 17 18:26:03 ! GobanSocket.ts:206   GobanSocket error unable to verify the first certificate�[22m�[39m
�[33mApr 17 18:26:03   GobanSocket.ts:217   GobanSocket closed with code 1006: Abnormal Closure�[39m
�[33mApr 17 18:26:03   main.ts:143          Disconnected from server�[39m

I'm not sure what causes this, there do seem to be other bots online.

@raylu
Copy link
Contributor

raylu commented Apr 18, 2024

perhaps you have some old CAs? what does this say?

openssl s_client -connect online-go.com:443 < /dev/null | openssl x509 -noout -text

I get this cert https://crt.sh/?id=12255514776
though it looks like a newer cert was issued 6 days later https://crt.sh/?id=12326863795
they were both issued in march, though, so I don't think anything has changed recently

@Dorus
Copy link
Contributor Author

Dorus commented Apr 18, 2024

Do you have a windows equivalent of that command at hand?

@raylu
Copy link
Contributor

raylu commented Apr 18, 2024

ah... on windows, node isn't patched to use the system's CA store nodejs/node#4175. so you might just need to upgrade node? unless you're using the brotli-built executables, in which case the project needs to upgrade something

@Dorus
Copy link
Contributor Author

Dorus commented Apr 18, 2024

Oh!

I was using a very old node

node -v
v18.13.0

Updated to the latest, 21.7.3, still the same error

@Dorus
Copy link
Contributor Author

Dorus commented May 12, 2024

Not sure what changed but it all works again.

@Dorus Dorus closed this as completed May 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants