Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Duplicate user for different server #1364

Open
vfairon opened this issue Dec 16, 2024 · 1 comment
Open

Duplicate user for different server #1364

vfairon opened this issue Dec 16, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@vfairon
Copy link

vfairon commented Dec 16, 2024

Describe the bug

When creating new user on diffrent server I get the error Duplicate User, "..." is already saved.
This bug was reported on two servers which are the same but should be detected as diffrent since one is accessed through private ip (through vpn) and the other through url.
The username and password of the user were thus the same which might cause the confusion

Application version

3.8

Where did you install the app from?

App Store

Device information

Iphone 15 normal version

OS version

18.1.1

Jellyfin server version

10.10.3

@vfairon vfairon added the bug Something isn't working label Dec 16, 2024
@JPKribs
Copy link
Member

JPKribs commented Feb 7, 2025

Just to confirm, is this second server a clone of the first server? We save the credentials with the server ID. So, if the server ID is the same, it will treat it as the same server, regardless of the URL.

The reason that we do this is because users will often have multiple URL for a single server. Often times, this is an internal IP and an external FQDN. So, saving using the server ID allows us to unify those credentials under a single entity instead of having every server be treated different based on the URL.

If your second server is a clone of the first server they will have the same server ID, even though they are separate machines. I DO NOT recommend attempting to change the server ID after the server has been created. I've tried this personally and unfortunately, it seems fairly easy to accidentally corrupt your database by doing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants