[GH-ISSUE #636] After configuring the tls certificate, webdav access fails #384

New Issue

zhus · 2026-04-08T16:52:30+03:00

zhus commented

2026-04-08 16:52:30 +03:00

Originally created by @sun0537 on GitHub (Oct 14, 2025).
Original GitHub issue: https://github.com/sigoden/dufs/issues/636

Problem

After configuring the tls certificate in the dufs configuration file, The certificate uses a wildcard domain name certificate, and the domain name accessed by the browser has been protected by tls. I can log in using the domain name in the browser, and can also successfully create and delete files, but webdav access fails.

Is there any configuration I haven't noticed?

Start dufs directly using the following command:

$sudo /usr/local/bin/dufs -c /usr/local/etc/dufs/config.yaml

Listening on:
  https://ip:443/
  https://127.0.0.1:443/

Configuration

Start with the following configuration file

serve-path: /var/lib/dufs

bind: 0.0.0.0
port: 443

auth:
  - asmin:admin@/:rw
  - user:pass@/books:rw,/share

allow-upload: true
allow-delete: true
allow-search: true
allow-archive: true

log-format: '$remote_addr "$request" $status $http_user_agent'
log-file: /var/log/dufs/dufs.log

compress: low

tls-cert: /usr/local/dufs/certs/cert.pem
ls-key: /usr/local/dufs/certs/key.pem

Log

The test log before configuring the tls certificate is accessed using http://ip:port, and there is no problem

2025-10-14T01:50:36+08:00 INFO - IP "PROPFIND /books/config" 404 okhttp/4.9.2
2025-10-14T01:50:37+08:00 INFO - IP "PROPFIND /books" 207 okhttp/4.9.2
2025-10-14T01:50:38+08:00 INFO - IP "PROPFIND /books/config" 404 okhttp/4.9.2
2025-10-14T01:50:39+08:00 INFO - IP "MKCOL /books/config/" 201 okhttp/4.9.2
2025-10-14T01:50:41+08:00 INFO - IP "PUT /books/config/test.txt" 201 okhttp/4.9.2
2025-10-14T01:50:42+08:00 INFO - IP "PROPFIND /books/config/" 207 okhttp/4.9.2
2025-10-14T01:50:43+08:00 INFO - IP "DELETE /books/config/test.txt" 204 okhttp/4.9.2
2025-10-14T01:51:23+08:00 INFO - IP "PROPFIND /books/config" 207 okhttp/4.9.2
2025-10-14T01:51:25+08:00 INFO - IP "PUT /books/config/test.txt" 201 okhttp/4.9.2
2025-10-14T01:51:26+08:00 INFO - IP "PROPFIND /books/config/" 207 okhttp/4.9.2
2025-10-14T01:51:27+08:00 INFO - IP "DELETE /books/config/test.txt" 204 okhttp/4.9.2

Test log after configuring tls certificate, accessed using https://sub.domain.tld, failed

2025-10-14T15:10:58+08:00 INFO - ip "PROPFIND https://sub.domain.tld/books/config" 207 okhttp/4.9.2
2025-10-14T15:11:01+08:00 INFO - ip "PROPFIND https://sub.domain.tld/books/config" 207 okhttp/4.9.2

Environment Information

Dufs version: dufs 0.45.0
Browser/Webdav info: WebDAV test in Koodo Reader book synchronization using WebADV
OS info:
Proxy: The domain name is resolved to cloudflare, and the proxy is closed.

Originally created by @sun0537 on GitHub (Oct 14, 2025). Original GitHub issue: https://github.com/sigoden/dufs/issues/636 **Problem** After configuring the tls certificate in the dufs configuration file, The certificate uses a wildcard domain name certificate, and the domain name accessed by the browser has been protected by tls. I can log in using the domain name in the browser, and can also successfully create and delete files, but webdav access fails. Is there any configuration I haven't noticed? <details> <summary>Start dufs directly using the following command: </summary> ```bash $sudo /usr/local/bin/dufs -c /usr/local/etc/dufs/config.yaml Listening on: https://ip:443/ https://127.0.0.1:443/ ``` </details> **Configuration** <details> <summary>Start with the following configuration file </summary> ```yaml serve-path: /var/lib/dufs bind: 0.0.0.0 port: 443 auth: - asmin:admin@/:rw - user:pass@/books:rw,/share allow-upload: true allow-delete: true allow-search: true allow-archive: true log-format: '$remote_addr "$request" $status $http_user_agent' log-file: /var/log/dufs/dufs.log compress: low tls-cert: /usr/local/dufs/certs/cert.pem ls-key: /usr/local/dufs/certs/key.pem ``` </details> **Log** <details> <summary>The test log before configuring the tls certificate is accessed using http://ip:port, and there is no problem </summary> ```log 2025-10-14T01:50:36+08:00 INFO - IP "PROPFIND /books/config" 404 okhttp/4.9.2 2025-10-14T01:50:37+08:00 INFO - IP "PROPFIND /books" 207 okhttp/4.9.2 2025-10-14T01:50:38+08:00 INFO - IP "PROPFIND /books/config" 404 okhttp/4.9.2 2025-10-14T01:50:39+08:00 INFO - IP "MKCOL /books/config/" 201 okhttp/4.9.2 2025-10-14T01:50:41+08:00 INFO - IP "PUT /books/config/test.txt" 201 okhttp/4.9.2 2025-10-14T01:50:42+08:00 INFO - IP "PROPFIND /books/config/" 207 okhttp/4.9.2 2025-10-14T01:50:43+08:00 INFO - IP "DELETE /books/config/test.txt" 204 okhttp/4.9.2 2025-10-14T01:51:23+08:00 INFO - IP "PROPFIND /books/config" 207 okhttp/4.9.2 2025-10-14T01:51:25+08:00 INFO - IP "PUT /books/config/test.txt" 201 okhttp/4.9.2 2025-10-14T01:51:26+08:00 INFO - IP "PROPFIND /books/config/" 207 okhttp/4.9.2 2025-10-14T01:51:27+08:00 INFO - IP "DELETE /books/config/test.txt" 204 okhttp/4.9.2 ``` </details> <details> <summary> Test log after configuring tls certificate, accessed using https://sub.domain.tld, failed </summary> ``` 2025-10-14T15:10:58+08:00 INFO - ip "PROPFIND https://sub.domain.tld/books/config" 207 okhttp/4.9.2 2025-10-14T15:11:01+08:00 INFO - ip "PROPFIND https://sub.domain.tld/books/config" 207 okhttp/4.9.2 ``` </details> **Environment Information** - Dufs version: dufs 0.45.0 - Browser/Webdav info: WebDAV test in Koodo Reader book synchronization using WebADV - OS info: - Proxy: The domain name is resolved to cloudflare, and the proxy is closed.

zhus closed this issue

2026-04-08 16:52:30 +03:00

zhus referenced this issue

2026-04-08 16:53:35 +03:00

[PR #384] [CLOSED] feat: add index page format #594

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: sigoden/dufs#384