Cannot get through initial setup #756
Comments
|
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) |
|
Didn't have time to go on Discord yet, but this issue is indeed still relevant. |
|
This looks like a configuration issue. If after checking the configuration this is still a problem, we can reopen the issue. |
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 |
|
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 # 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 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 |
Description
When trying to sign in for the first time, the web interface shows a "Something went wrong while trying to sign in." and in Chromium DevTools all I can see is a 500 for
api/v1/auth/jellyfin.journactl -fu jellyseerrdoes not yield any useful information. (see logs section)I have tried nuking all off Jellyseerr's saved data that I could find several times already, including deleting all site cookies in my browser with no result. I've tried configuring it both through my reverse proxy and directly with no change. Using local IP/public URL for Jellyfin also didn't change anything.
I did get to the second step once, but was unable to replicate this.
Version
Nixpkgs for my system version reports version 1.7.0
Steps to Reproduce
My server runs NixOS
This runs the Jellyseerr executable through systemd, the exact service configuration used can be found here (it is Nix code, but should be readable for anyone with systemd experience).
Screenshots
Logs
Platform
desktop
Device
n/a
Operating System
GNU/Linux based
Browser
Brave (Chromium)
Additional Context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: