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

WebDAV: Error: Invalid response: 401 #360

Open
wjjessen opened this issue Aug 21, 2024 · 9 comments
Open

WebDAV: Error: Invalid response: 401 #360

wjjessen opened this issue Aug 21, 2024 · 9 comments

Comments

@wjjessen
Copy link

wjjessen commented Aug 21, 2024

Bug report

Steps to reproduce - current behaviour

I have an issue with Tusk v2024.8.10. I had to reinstall Tusk and when I try to add a WebDAV server I get the following error:

"Error: Cannot request origin permission for https://<KeePass_folder_path> since it was not declared in the manifest".

What is the expected behaviour

After clicking "Add Server", I expect to see a list of KeePass databases found by Tusk under the entered URL to select from.

Additional remarks

Previously, Tusk worked as expected. Existing setups with v2024.8.10 continue to work, they just can't discover the databases under the previously entered URL when clicking "Scan". When "Scan" is clicked for an existing setup with Tusk v2024.8.10, it shows "Error: Invalid response: 401".

Environment

Operating System:

Manjaro Linux 6.9.12-3

Browser vendor and version:

LibreWolf v128.0.3-2

Storage Provider:

Storage: Nextcloud

@wjjessen
Copy link
Author

Tusk was updated to v2024.8.20 in the FF Add-on store, so it automatically updated in LibreWolf. Now, when I try to "Add Server" it shows "Error: Invalid response: 401".

@subdavis subdavis changed the title Error: Cannot request origin permission for https://<KeePass_folder_path> since it was not declared in the manifest WebDAV: Error: Invalid response: 401 Aug 22, 2024
@subdavis
Copy link
Owner

The permission error is fixed. I cannot reproduce the 401 error (without entering invalid credentials, of course).

Please provide more information about your webDAV configration, including the authentication mechanism (Digest? Basic?)

Does it work on regular Firefox? Does it work on Chrome?

@tibacher
Copy link

Hi,

i have a almost the same behavior. I get 401 almost all time in my "main firefox" window but in a "private window" it works seamless! It only occours on my Windows 10 PC not on my MacBook. Reinstalling Tusk didn't fix it.
grafik

WebDAV: Nextcloud (29.0.5) WebDAV
Firefox Version: 129.0.2 (64-Bit) (Windows)

@Horst12345
Copy link

Horst12345 commented Aug 27, 2024

Same here:
Normal Firefox Window (Version 129.0.2 -64-bit) error 401:
grafik

When i integrate the WebDav connection in private mode everything is working like a charm:
grafik

The problems started with current updated Tusk version. Before august update everything was working.

WebDAV Sever = Nextcloud Hub 8 (29.0.5)
Error Log from Nextcloud:
NotAuthenticated - No public access to this resource., No 'Authorization: Basic' header found. Either the client didn't send one, or the server is misconfigured, No 'Authorization: Bearer' header found. Either the client didn't send one, or the server is mis-configured, No 'Authorization: Basic' header found. Either the client didn't send one, or the server is misconfigured

@Horst12345
Copy link

Microsoft Edge - Version 128.0.2739.42 (64-bit) - Working

grafik

@subdavis
Copy link
Owner

NotAuthenticated - No public access to this resource., No 'Authorization: Basic' header found. Either the client didn't send one, or the server is misconfigured, No 'Authorization: Bearer' header found. Either the client didn't send one, or the server is mis-configured, No 'Authorization: Basic' header found. Either the client didn't send one, or the server is misconfigured

Thank you , that's helpful context.

@Horst12345
Copy link

Problem is solved. Tusk can open the database without any problem.
What has happen? Version of tusk is furthermore 2024.8.2

@subdavis
Copy link
Owner

subdavis commented Sep 4, 2024

The latest version on firefox is 2024.8.20 which did have some fixes, but it seemed this thread was still having a problem after that.

@bigdestroyer
Copy link

Agreed, same error here. Have the Chrome extension added to Vivaldi browser installed. Work PC which has been set up prior to 2024.8.2 still works even though now on that version. Try to set it up on 2024.8.2 does not work

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

No branches or pull requests

5 participants