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

WS server doesn't start on Http4s since 1.4.2 #1419

Closed
gaspb opened this issue Jul 28, 2022 · 4 comments
Closed

WS server doesn't start on Http4s since 1.4.2 #1419

gaspb opened this issue Jul 28, 2022 · 4 comments

Comments

@gaspb
Copy link

gaspb commented Jul 28, 2022

Hello,

We just tried to update from 1.4.1 to 1.4.2, but our http4s websocket server stopped working (no error on the server, but the ws endpoint becomes unreachable)

❯ npx [email protected] --endpoint=wss://app/ws/graphql
Diagnosing wss://app/ws/graphql
⚠️  Could not resolve (ENOTFOUND)
Is the address correct?
Is the server running?

I get the same result with the http4s example app, the http endpoint works but the ws doesn't

@guizmaii
Copy link
Contributor

guizmaii commented Jul 28, 2022

Might be related to this recently-fixed-but-not-yet-released bug: #1417

@ghostdogpr
Copy link
Owner

Yeah it was fixed yesterday, not released yet (#1417).
Can you try with snapshot 1.4.2+6-5472838d-SNAPSHOT?

@gaspb
Copy link
Author

gaspb commented Jul 28, 2022

seems to fix it 👍 thanks

@gaspb gaspb closed this as completed Jul 28, 2022
@ghostdogpr
Copy link
Owner

In case anybody needs, the snapshot for 2.x is 2.0.0+5-66bf1858-SNAPSHOT.
I will probably release by the end of the week, just want to check a couple reported issues first.

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

3 participants