Bug:

by ADMIN 5 views

Overview

When attempting to access the Realdebrid webdav folder using the Realdebrid API, an error occurs. However, manually logging in to Rclone and entering the username and password successfully connects to the webdav folder. This article explores the possibility of using username/password instead of API to resolve the issue.

Expected Behavior

The expected behavior is to access the Realdebrid webdav folder using the Realdebrid API.

Actual Behavior

The actual behavior is that the Realdebrid API fails to connect to the webdav folder, resulting in an error.

Detailed Steps

The installation of the Realdebrid API was performed as stated in the guide. System startup was normal, but there was a problem connecting to the webdav folder.

Operating System

The operating system used is Ubuntu 24.04.

Environment Setup

The environment setup is as follows:

Docker-Compose.yml

version: '3.8'

services:
  zurg:
    image: ghcr.io/debridmediamanager/zurg-testing:latest
    container_name: zurg
    restart: unless-stopped
    ports:
      - 9999:9999
    volumes:
      - ./scripts/plex_update.sh:/app/plex_update.sh
      - ./config.yml:/app/config.yml
      - zurgdata:/app/data

  rclone:
    image: rclone/rclone:latest
    container_name: rclone
    restart: unless-stopped
    environment:
      TZ: Europe/Istanbul
      PUID: 1000
      PGID: 1000
    volumes:
      - /mnt/realdebrid:/data:rshared # CHANGE /mnt/zurg WITH YOUR PREFERRED MO>
      - ./rclone.conf:/config/rclone/rclone.conf
    cap_add:
      - SYS_ADMIN
    security_opt:
      - apparmor:unconfined
    devices:
      - /dev/fuse:/dev/fuse:rwm
    depends_on:
      - zurg
    command: "mount zurg: /data --allow-other --allow-non-empty --dir-cache-time 10s --vfs-cache-mode full"

volumes:
  zurgdata:

Logs

The logs are as follows:

http://ZURGIP:9999/logs/upload not reachable
zurg logs:Logging to logs/zurg-2025-03-10.log

2025-03-10T07:48:36.391Z	DEBUG	zurg	PID: 1

2025-03-10T07:48:36.391Z	INFO	zurg	Version: v0.9.3-final

2025-03-10T07:48:36.391Z	INFO	zurg	GitCommit: 4179c2745b4fb22fcb37f36de27b3daa39f114f0

2025-03-10T07:48:36.391Z	INFO	zurg	BuiltAt: 2024-07-14T09:48:32

2025-03-10T07:48:36.391Z	INFO	zurg	Debug logging is enabled; if you are not debugging please set LOG_LEVEL=info in your environment

2025-03-10T07:48:36.391Z	DEBUG	config	Loading config file ./config.yml

2025-03-10T07:48:36.391Z	DEBUG	config	Config version: v1

2025-03-10T07:48:36.392Z	INFO	zurg	Starting server on [::]:9999

2025-03-10T08:04:41.667Z	ERROR	realdebrid	Error when executing the user information request: Get "https://api.real-debrid.com/rest/1.0/user": http: server gave HTTP response to HTTPS client

2025-03-10T08:04:41.668Z	ERROR	zurg	Failed to get user information: Get "https://api.real-debrid.com/rest/1.0/user": http: server gave HTTP response to HTTPS client

2025-03-10T08:04:41.783Z	ERROR	realdebrid	Error when executing the get torrents request: Get "https://api.real-debrid.com/rest/1.0/torrents?limit=100&page=1": http: server gave HTTP response to HTTPS client

2025-03-10T08:04:41.783Z	WARN	manager	Cannot get torrents: Get "https://api.real-debrid.com/rest/1.0/torrents?limit=100&page=1": http: server gave HTTP response to HTTPS client

Rclone Configuration

The Rclone configuration is as follows:

type = webdav
url = http://zurg:9999/dav
vendor = other
pacer_min_sleep = 0

Zurg Configuration

The Zurg configuration is as follows:

zurg: v1
token: Vxx
# host: "[::]"
# port: 9999
# username:
# password:
# proxy:
# concurrent_workers: 20
check_for_changes_every_secs: 10
# repair_every_mins: 60
# ignore_renames: false
# retain_rd_torrent_name: false
# retain_folder_name_extension: false
enable_repair: true
auto_delete_rar_torrents: true
# api_timeout_secs: 15
# download_timeout_secs: 10
# enable_download_mount: false
# rate_limit_sleep_secs: 6
# retries_until_failed: 2
# network_buffer_size: 4194304 # 4MB
# serve_from_rclone: false
# verify_download_link: false
# force_ipv6: false
on_library_update: sh plex_update.sh "$@"
#for windows comment the line above and uncomment the line below:
#on_library_update: '& powershell -ExecutionPolicy Bypass -File .\plex_update.p>

directories:
  anime:
    group_order: 10
    group: media
    filters:
      - regex: /\b[a-fA-F0-9]{8}\b/
      - any_file_inside_regex: /\b[a-fA-F0-9]{8}\b/

  shows:
    group_order: 20
    group: media
    filters:
      - has_episodes: true

  movies:
    group_order: 30
    group: media
    only_show_the_biggest_file: true
    filters:
      - regex: /.*/

Screenshots

Image

Possible Solution

One possible solution to this issue is to use username/password instead of API to connect to the webdav folder. This can be achieved by modifying the Rclone configuration to use the username and password instead of the API token.

Conclusion

In conclusion, the Realdebrid API error for webdav is a complex issue that requires a thorough investigation. The possible solution of using username/password instead of API to connect to the webdav folder is a viable option. However, further testing and validation are required to confirm the effectiveness of this solution.

Future Work

Future work includes:

  • Further testing and validation of the possible solution
  • Investigation of other possible causes of the issue
  • Development of a more robust and reliable solution to the issue

References

  • Realdebrid API documentation
  • Rclone documentation
  • Zurg documentation

Acknowledgments

The author would like to acknowledge the contributions of the following individuals:

  • [Name 1]
  • [Name 2]
  • [Name 3]

License

This work is licensed under the [License Name] license.

Overview

In our previous article, we explored the issue of the Realdebrid API error for webdav and possible solutions. In this article, we will provide a Q&A section to address common questions and concerns related to this issue.

Q&A

Q: What is the Realdebrid API error for webdav?

A: The Realdebrid API error for webdav is an issue where the Realdebrid API fails to connect to the webdav folder, resulting in an error.

Q: What are the possible causes of the Realdebrid API error for webdav?

A: The possible causes of the Realdebrid API error for webdav include:

  • Incorrect API token or username/password
  • Incorrect webdav URL or configuration
  • Network issues or connectivity problems
  • Realdebrid API or webdav server issues

Q: How can I troubleshoot the Realdebrid API error for webdav?

A: To troubleshoot the Realdebrid API error for webdav, you can try the following:

  • Check the API token or username/password for correctness
  • Verify the webdav URL and configuration
  • Check for network issues or connectivity problems
  • Check the Realdebrid API or webdav server status

Q: Can I use username/password instead of API to connect to the webdav folder?

A: Yes, you can use username/password instead of API to connect to the webdav folder. This can be achieved by modifying the Rclone configuration to use the username and password instead of the API token.

Q: How do I modify the Rclone configuration to use username/password instead of API?

A: To modify the Rclone configuration to use username/password instead of API, you can follow these steps:

  1. Open the Rclone configuration file
  2. Change the type to webdav
  3. Change the url to the webdav URL
  4. Change the vendor to other
  5. Add the username and password fields
  6. Save the changes

Q: What are the benefits of using username/password instead of API to connect to the webdav folder?

A: The benefits of using username/password instead of API to connect to the webdav folder include:

  • Improved security
  • Simplified configuration
  • Reduced reliance on API tokens

Q: Are there any potential drawbacks to using username/password instead of API to connect to the webdav folder?

A: Yes, there are potential drawbacks to using username/password instead of API to connect to the webdav folder, including:

  • Increased complexity
  • Potential security risks
  • Reduced flexibility

Q: How can I ensure the security of my Realdebrid API credentials?

A: To ensure the security of your Realdebrid API credentials, you can follow these best practices:

  • Use a secure API token or username/password
  • Store the API token or username/password securely
  • Use two-factor authentication
  • Regularly update and rotate the API token or username/password

Q: Can I use a third-party service to manage my Realdebrid API credentials?

A: Yes, you can use a third-party service to manage your Realdebrid API credentials. This can include services such as password managers or API management platforms.

Q: How can I troubleshoot issues with my Realdebrid API credentials?

A: To troubleshoot issues with your Realdebrid API credentials, you can try the following:

  • Check the API token or username/password for correctness
  • Verify the webdav URL and configuration
  • Check for network issues or connectivity problems
  • Check the Realdebrid API or webdav server status

Conclusion

In conclusion, the Realdebrid API error for webdav is a complex issue that requires a thorough investigation. By following the Q&A section above, you can better understand the possible causes and solutions to this issue. Remember to always follow best practices for security and to troubleshoot issues promptly to ensure the smooth operation of your Realdebrid API credentials.