search

NixOS / nixpkgs

Nix Packages collection & NixOS
MIT License
17.93k stars 13.96k forks source link

Discourse: SSL causes nginx worker processs to enter infinite loop #349485

Open ethindp opened 4 days ago

ethindp commented 4 days ago

Describe the bug

Currently, when using Discourse (and seemingly only Discourse), trying to use it with nginx causes the worker process to enter an infinite loop. This even occurs on nixpkgs unstable (Nginx 1.27.2). Granted, for my system I selectively enable unstable packages, but I'm not sure how much that matters. It was diagnosed by a user in this topic. Disabling SSL on Nginx solves this problem, but that isn't exactly the wisest idea for a public-facing service.

Steps To Reproduce

Steps to reproduce the behavior:

  1. Configure Discourse with incoming/outgoing email and other things as you normally might.
  2. Try to log in to the default admin account.
  3. The app should hang indefinitely at "Signing in...". If you have other web apps running, they should also immediately become inaccessible, but SSH and other internet services should be unaffected. Unlike most errors or problems, this one is from my experience rather annoying to find, because no errors or anything else is printed to logs, nor is OOM invoked.

Expected behavior

Discourse should work fine.

Screenshots

N/A

Additional context

I am using Postgresql 16, not the "supported" version, but taht shouldn't matter.

Notify maintainers

@fpletz @RaitoBezarius

Metadata

Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.

[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.53-hardened1, NixOS, 24.05 (Uakari), 24.05.5744.dc2e0028d274`
 - multi-user?: `no`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.8`
 - channels(root): `"nixos-24.05"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Add a :+1: reaction to issues you find important.

Atemu commented 4 days ago

On a related note: The NixOS test I just tried to run in order to see if it reproduces the issue has been broken since 9c50de8b57f060144c676654d9773db934a2b2c6.