Cannot get through initial setup about jellyseerr HOT 6 CLOSED

Can you hop onto discord. We don't carry out troubleshooting on github issues.

(P.s I also use jellyseerr nixpkg but i use 1.8.1 from the unstable channel)

from jellyseerr.

Didn't have time to go on Discord yet, but this issue is indeed still relevant.

from jellyseerr.

This looks like a configuration issue. If after checking the configuration this is still a problem, we can reopen the issue.

from jellyseerr.

Didn't have time to go on Discord yet, but this issue is indeed still relevant.

This is definitely a configuration problem. I am running nixos on all my servers and it is indeed working. We don't carry out support issues on github issues so as to keep github clean for bugs and feature requests and other issues

from jellyseerr.

Hey, I don't wanna argue, but this is quite literally just default settings.

All Jellyfin/Jellyseerr related lines in my main server's config (does not use a flake):

  services.jellyfin.enable = true;
  services.jellyseerr.enable = true;

Here are all the relevant virtualhost definitions in services.nginx.virtualHosts on my reverse proxy (also doesn't use a flake) - Jellyseerr is currently commented out as it's not working:

      # Jellyfin
      "[domain redacted]" = {
        forceSSL = true;
        useACMEHost = "[domain redacted]";
        locations."/" = {
          proxyPass = "http://${hosts.ocean-server}:8096";
          proxyWebsockets = true;
          recommendedProxySettings = true;
        };
      };

      ## Jellyseerr
      #"[domain redacted]" = {
      #  forceSSL = true;
      #  useACMEHost = "[domain redacted]";
      #  locations."/" = {
      #    proxyPass = "http://${hosts.ocean-server}:5055";
      #    proxyWebsockets = true;
      #    recommendedProxySettings = true;
      #  };
      #};

Both are on stable Nixpkgs.

from jellyseerr.

Hey, I don't wanna argue, but this is quite literally just default settings.

All Jellyfin/Jellyseerr related lines in my main server's config (does not use a flake):

  services.jellyfin.enable = true;
  services.jellyseerr.enable = true;

Here are all the relevant virtualhost definitions in services.nginx.virtualHosts on my reverse proxy (also doesn't use a flake) - Jellyseerr is currently commented out as it's not working:

      # Jellyfin
      "[domain redacted]" = {
        forceSSL = true;
        useACMEHost = "[domain redacted]";
        locations."/" = {
          proxyPass = "http://${hosts.ocean-server}:8096";
          proxyWebsockets = true;
          recommendedProxySettings = true;
        };
      };

      ## Jellyseerr
      #"[domain redacted]" = {
      #  forceSSL = true;
      #  useACMEHost = "[domain redacted]";
      #  locations."/" = {
      #    proxyPass = "http://${hosts.ocean-server}:5055";
      #    proxyWebsockets = true;
      #    recommendedProxySettings = true;
      #  };
      #};

Both are on stable Nixpkgs.

Not arguing. But there's a lot of troubleshooting steps I want to carry out and we don't carry out support here. Including something went wrong which can be explained by steps.

If you dont want to comply, i really cant help you. Because i am also running nix, on all my machines and i cant reproduce this so i am going to need your cooperation to figure out whats wrong in your instance. Without troubleshooting and understanding what's going on your system i cannot help fix it. Especially something I cannot reproduce given we're on the same platform. It is not an issue. But a configuration problem. Which i can help. If you help me figure out what it is.

I believe this might an issue where jellyfin hostname is already set in settings.json so it's throwing a 500 saying that. A suggestion i could give then is, go to /var/lib/private/jellyseerr/ then clean out your entire config directory and Retry. And for best effect, try overlaying it to use unstable nixpkg for jellyseerr only. It should be 1.8.1

from jellyseerr.