Call to /wave is failing, locally

[edalzell]

Locally I see the call to /wave timeout, all the time, makes testing the chat feature I have very difficult, any ideas how to resolve?

I'm on the latest version, running Herd.

Is there an nginx thing maybe?

[slavarazum]

Output buffering? 🤔😀

#35 (comment)

[edalzell]

Nope I have that on, and not getting an error anywhere I can see.

[slavarazum]

Herd's nginx is not configurable. Seems like it has 10s timeout for inactive connections.
To preserve connection active, try to use ping command with 8s interval:

php artisan sse:ping --interval=8

[edalzell]

it is configurable, I added the same lines you mention in the instructions, no change.

[slavarazum]

I missed that we can configure in the same way as Valet or change general config in /Users/razum/Library/Application Support/Herd/config/nginx

Have you tried the ping command?

[slavarazum]

It seems that the instructions in the readme are not suitable for Herd. Upon investigating Herd's nginx configs, I discovered that it has a default timeout of 60 seconds. Therefore, you can leave the configurations as they are by default, which will provide a stable connection of 60 seconds, usually sufficient for testing purposes.

If you need to extend the connection time, you can add fastcgi_read_timeout 1h, for instance, to the location ~ [^/]\.php(/|$) { section. Alternatively, you can run php artisan sse:ping --interval=50 to maintain the connection.

I will rewrite docs for Herd setup soon.

[edalzell]

Seeing this in Firefox and Safari, locally, any ideas?

[slavarazum]

Configuration issue resolved.

[hotmeteor]

What was the problem / resolution? I have a team member hitting the same thing.

[edalzell]

I don't remember sorry it was a while back...