starred/floccus

Fork 0

mirror of https://github.com/floccusaddon/floccus.git synced 2026-04-26 06:35:59 +03:00

[GH-ISSUE #997] Android WebDAV unable to connect E17 - Self Signed Cetificate #652

New issue

Closed

opened 2026-02-25 22:37:44 +03:00 by kerem · 4 comments

kerem commented

2026-02-25 22:37:44 +03:00

Owner

Originally created by @elmodor on GitHub (Nov 17, 2021).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/997

Describe the bug

I'm unable to connect to my webdav on the android app.
I believe the issue is that I use a self signed certificate on my webdav server for https. The certificate is installed as "user" certificate in my android system. However, the default setting for Android apps is to allow only "system" certificates. For "user" certificates to be accepted, this has to be stated in the AndroidManifest.xml. I recently found this out because I run into this issue in a different app.

To Reproduce

Steps to reproduce the behavior:

Spin up a caddy server as reverse proxy and redirect to the webdav server
Spin up a webdav server
Install the root.crt form caddy in the android phone
Try to connect to the webdav server in the android app

Expected behavior

Able to connect to the webdav server with a self signed certificate.

Screenshots

Desktop

Android

Floccus 4.8.4

Server

OS: Debian 10
Webdav Server

Debug log

Debug log provided

Additional context

The "behavior" is described here:
https://developer.android.com/training/articles/security-config#base-config
https://developer.android.com/training/articles/security-config#certificates

A fix would be to add this to the AndroidManifest.xml:

<network-security-config>
    <base-config cleartextTrafficPermitted="true">
        <trust-anchors>
           <certificates src="system" />
           <certificates src="user" />
        </trust-anchors>
    </base-config>
</network-security-config>

This is a MR that fixed this issue in a different app where I found the same problem:
github.com/advplyr/audiobookshelf-app@44f535020d

This allows that certificates added by the user to the android system are allowed to be used to verify the https certificates.

Originally created by @elmodor on GitHub (Nov 17, 2021). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/997 ### Describe the bug I'm unable to connect to my webdav on the android app. I believe the issue is that I use a self signed certificate on my webdav server for https. The certificate is installed as "user" certificate in my android system. However, the default setting for Android apps is to allow only "system" certificates. For "user" certificates to be accepted, this has to be stated in the AndroidManifest.xml. I recently found this out because I run into this issue in a different app. ### To Reproduce Steps to reproduce the behavior: 1. Spin up a caddy server as reverse proxy and redirect to the webdav server 2. Spin up a webdav server 3. Install the root.crt form caddy in the android phone 4. Try to connect to the webdav server in the android app ### Expected behavior Able to connect to the webdav server with a self signed certificate. ### Screenshots - ### Desktop - ### Android - Floccus 4.8.4 ### Server - OS: Debian 10 - Webdav Server ### Debug log - [ ] Debug log provided ### Additional context The "behavior" is described here: https://developer.android.com/training/articles/security-config#base-config https://developer.android.com/training/articles/security-config#certificates A fix would be to add this to the AndroidManifest.xml: ``` <network-security-config> <base-config cleartextTrafficPermitted="true"> <trust-anchors> <certificates src="system" /> <certificates src="user" /> </trust-anchors> </base-config> </network-security-config> ``` This is a MR that fixed this issue in a different app where I found the same problem: https://github.com/advplyr/audiobookshelf-app/commit/44f535020d591ee56038c6d7ab9792ff29ce7445 This allows that certificates added by the user to the android system are allowed to be used to verify the https certificates.

kerem

2026-02-25 22:37:44 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 22:37:45 +03:00

Author

Owner

@nagyrobi commented on GitHub (Nov 30, 2021):

I have the same problem. Please add support for self signed certs.

@nagyrobi commented on GitHub (Nov 30, 2021): I have the same problem. Please add support for self signed certs.

kerem commented

2026-02-25 22:37:45 +03:00

Author

Owner

@marcelklehr commented on GitHub (Dec 6, 2021):

Can you confirm, whether this works in the latest version?

@marcelklehr commented on GitHub (Dec 6, 2021): Can you confirm, whether this works in the latest version?

kerem commented

2026-02-25 22:37:45 +03:00

Author

Owner

@elmodor commented on GitHub (Dec 6, 2021):

I can confirm that it works now, thank you very much ❤️
Had to uninstall and install the app again for it to work.

@elmodor commented on GitHub (Dec 6, 2021): I can confirm that it works now, thank you very much :heart: Had to uninstall and install the app again for it to work.

kerem commented

2026-02-25 22:37:45 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 20, 2023):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions[bot] commented on GitHub (Mar 20, 2023): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

kerem referenced this issue

2026-02-25 23:30:31 +03:00

[PR #652] [MERGED] Bump @babel/preset-env from 7.10.4 to 7.11.5 #1687

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/floccus#652

No description provided.

Rows
Columns