fix(mastodon): use working unix sockets for streaming api #98

Merged

b12f merged 2 commits from fix/mastodon-streaming-api into main

2024-01-18 15:08:25 +00:00

teutat3s commented

2024-01-17 09:24:39 +00:00

Owner

The mastodon streaming API is currently unusable because we still pass traffic to the old single unix socket path.
Since c82195d9e8 (diff-157b1ef68573bbec951d6e551513a555e2d1ca7a161a68f1978b11d39a0bef1eR789-R803)
there are multiple unix sockets involved.

Logs from nginx:

2024/01/16 17:14:24 [crit] 1701833#1701833: *58379673 connect() to unix:/run/mastodon-streaming/streaming.socket failed (2: No such file or directory) while connecting to upstream, client: <redacted>, server: mastodon.pub.solar, request: "GET /api/v1/streaming/? HTTP/1.1", upstream: "http://unix:/run/mastodon-streaming/streaming.socket:/api/v1/streaming/?", host: "mastodon.pub.solar"

The mastodon [streaming API](https://docs.joinmastodon.org/admin/scaling/#streaming) is currently unusable because we still pass traffic to the old single unix socket path. Since https://github.com/NixOS/nixpkgs/commit/c82195d9e82b28147e9a960f6d47ca9200228452#diff-157b1ef68573bbec951d6e551513a555e2d1ca7a161a68f1978b11d39a0bef1eR789-R803 there are multiple unix sockets involved. Logs from nginx: ``` 2024/01/16 17:14:24 [crit] 1701833#1701833: *58379673 connect() to unix:/run/mastodon-streaming/streaming.socket failed (2: No such file or directory) while connecting to upstream, client: <redacted>, server: mastodon.pub.solar, request: "GET /api/v1/streaming/? HTTP/1.1", upstream: "http://unix:/run/mastodon-streaming/streaming.socket:/api/v1/streaming/?", host: "mastodon.pub.solar" ```

teutat3s self-assigned this 2024-01-17 09:24:39 +00:00

teutat3s force-pushed fix/mastodon-streaming-api from 79ca777014 to 94ae6c9302

2024-01-17 09:32:24 +00:00

Compare

teutat3s added 1 commit 2024-01-17 14:17:12 +00:00

fix(nginx): [warn] could not build optimal proxy_headers_hash

Flake checks / Check (pull_request) Successful in 10m14s

Details

ffdf55993f

nginx: [warn] could not build optimal proxy_headers_hash, you should
increase either proxy_headers_hash_max_size: 2048 or
proxy_headers_hash_bucket_size: 64; ignoring
proxy_headers_hash_bucket_size