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

Protected domains #7

Open
sbruggmann opened this issue Nov 7, 2022 · 3 comments
Open

Protected domains #7

sbruggmann opened this issue Nov 7, 2022 · 3 comments

Comments

@sbruggmann
Copy link

If the domain is protected, like on stage domains with a basic auth, it does need additional server config, to make it work.

One way could be a static url prefix which can be opened on the server by default, or just something /.well-known/synco-token

@skurfuerst
Copy link
Member

good point :) I'll try to add to the wizard that it asks for the user and password in this case.

@jonnitto
Copy link

jonnitto commented Mar 4, 2024

Hi there, my script hero!

Any progress on this?

@skurfuerst
Copy link
Member

Hey @jonnitto ,

The workaround for URLs behind HTTP basic authentication is to specify the URL with:

https://user:[email protected] - we have recently tested this and it works. As soon as I find some time I also want to include this in synco; but it is hard to estimate currently.

All the best,
Sebastian

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

3 participants