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

401 errors #1204

Open
opa-rudi opened this issue Oct 4, 2023 · 3 comments
Open

401 errors #1204

opa-rudi opened this issue Oct 4, 2023 · 3 comments

Comments

@opa-rudi
Copy link

opa-rudi commented Oct 4, 2023

Hi everyone,

I am running current baikal server and getting these 401 errors alternating with 207:

"PROPFIND /dav.php/calendars/klmn/inbox/ HTTP/1.1" 401 2673 "-" "macOS/13.1 (22C65) dataaccessd/1.0"
"PROPFIND /dav.php/calendars/klmn/inbox/ HTTP/1.1" 207 2512 "-" "macOS/13.1 (22C65) dataaccessd/1.0"
"PROPFIND /dav.php/calendars/klmn/inbox/ HTTP/1.1" 401 2673 "-" "macOS/13.1 (22C65) dataaccessd/1.0"
"PROPFIND /dav.php/calendars/klmn/inbox/ HTTP/1.1" 207 2512 "-" "macOS/13.1 (22C65) dataaccessd/1.0"
"PROPFIND /dav.php/calendars/klmn/inbox/ HTTP/1.1" 401 2673 "-" "macOS/13.1 (22C65) dataaccessd/1.0"
"PROPFIND /dav.php/calendars/klmn/inbox/ HTTP/1.1" 207 2512 "-" "macOS/13.1 (22C65) dataaccessd/1.0"

This error pattern also occurs when using Android. Calendar sync is working on all devices.

my apache config:

    <VirtualHost 10.8.0.1:443>

    ServerName baikal.vpn
    DocumentRoot "/var/www/baikal/html"

    <Directory "/var/www/baikal/html">
            Require all granted
            AllowOverride None
            Options None
    </Directory>

    RewriteEngine On
    RewriteRule /.well-known/carddav /dav.php [R=308,L]
    RewriteRule /.well-known/caldav  /dav.php [R=308,L]

    SSLEngine on
    SSLCertificateFile /etc/ssl/certs/apache-selfsigned.crt
    SSLCertificateKeyFile /etc/ssl/private/apache-selfsigned.key

    </VirtualHost>
@arminwedler
Copy link

Authentification for users Fail after update.

I hope this problem has not been reported before and it is not just a stupid failure on my part, sorry this is possible.
Anyway, it seam to be the same issue that opa-rudi has reported, thus I post this also here.

Using:
Baikal 0.9.3
PHP 8.2

I updated my server to php 8.2, after realizing failure with baikal 0.9.2, I updated to 0.9.3 and also implemented the fixes from #1154.
Still, all clients are failing to log in, Failure 401. This is the response message of the clients:

Response status code does not indicate success: '401' ('Unauthorized'). Message:
<d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns">
<s:sabredav-version>4.3.1</s:sabredav-version>
<s:exception>Sabre\DAV\Exception\NotAuthenticated</s:exception>
<s:message>No 'Authorization: Digest' header found. Either the client didn't send one, or the server is misconfigured. Login was needed for privilege: {DAV:}read on addressbooks/armin/default</s:message>
</d:error>

Same for 'Authorization: Basic', I tried with prio existing users and new users, no login. Also, after downgrading back to 0.9.2. no authorization.
Admin login works without failure, all entries (users, cal, card) are present.

What do I miss?
Is it related to PHP 8.2?

Prosa:
I was running Baikal for more than 5 years without problems, amazing piece of software!

@opa-rudi
Copy link
Author

opa-rudi commented Oct 5, 2023

I am also using Baikal 0.9.3 and PHP 8.2

@arminwedler
Copy link

This issue is closed for me, update to baikal 9.4 made it, thank you!

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