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

basic auth question #3

Open
clach04 opened this issue Jun 9, 2023 · 1 comment
Open

basic auth question #3

clach04 opened this issue Jun 9, 2023 · 1 comment

Comments

@clach04
Copy link

clach04 commented Jun 9, 2023

Is basic auth expected to work with Party-Up?

I setup Copyparty behind a Caddy reverse proxy, 9001/copyparty#38.

Works great in the web browser.

Doesn't work in Party-Up.

Thing's I've tried:

Configure Party-Up to point to https url, e.g.; https://myserver:1234 I get error:

Screenshot_20230608-203142_Party+UP!+dbg-noauthprovided

Configure Party-Up to point to https url with basic auth in the url, e.g. https://user:password@myserver:1234 , I get error:

Screenshot_20230608-203328_Party+UP!+dbg-authinurl

I've had some issues getting a working CopyParty password protected area - which seems like the logical solution to this if wanting to use Party-Up.

@9001
Copy link
Owner

9001 commented Jun 9, 2023

Say, what happens if you change the password in the party-up settings into the username:password which is expected by your basic-auth config? So the username and password separated by a colon?

I'm asking because, like you said, the expected / intended auth method is by using copyparty's built-in account stuff, and not having an additional basic-auth in front of copyparty.

But just from looking at the app code, it looks like this should have worked, unintended as it is :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants