-
Notifications
You must be signed in to change notification settings - Fork 183
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
PWA is not available when HTTP Auth is enabled #221
Comments
Added site.webmanifest to always accessible path, and can't reproduce on Android PWA app added from Chrome with HTTP auth enabled. So probably it's Safari issue and can't be fixed on TorrServer side. |
I found 2 similar issues: Maybe we need to implement the same? |
Hi, I use v120 and can't use auth. I use docker with config:
and file accs.db
I tried put accs.db in /ts, /db, /ts/config, /db/config. What I do wrong? Torrserver does't ask autentification |
Hi @apnagaev It's thread related to PWA, not issues with HTTP Auth. Besides, you are using image Please, better use a docker image from current repository with an exact version, which is Answering your question, I can confirm Here is an example of
You must ensure that you have the file Besides, you bind |
Sorry, youre are right, when I change image to ghcr.io/yourok/torrserver:matrix.120 torrserver started working |
probably fixed in MatriX.121 release |
Reopen if issue is still active |
Still not fixed for me |
My server is configured to use HTTP Auth as described here https://github.com/YouROK/TorrServer#authorization
I tried to add PWA on iOS to use VLC link, but there is no Mobile App configuration view. I can't use VLC in PWA.
Steps to reproduce:
0. Use iOS
Expected result:
HTTP Auth is requested, PWA view is loaded, Mobile config page is available.
Actual result:
HTTP Auth is requested, PWA is not available, standard view is shown, Mobile config page is not available
I noticed: if I disable HTTP Auth, add PWA according to the steps, enable HTTP Auth again, all works as expected.
I suppose the issue may appear because PWA manifest is not available to Safari because of HTTP Auth header.
The text was updated successfully, but these errors were encountered: