All-In-One video library & player for iOS/macOS/tvOS
...
Best local and net disk movie/tv player on Mac, creating a local personal media library.
Price reduced to Free Trial!
  • $29.99
  • 0
How to Mount Cloud Drives with Alist for Beginners? A Comprehensive Guide!
How to Mount Cloud Drives with Alist for Beginners? A Comprehensive Guide!
  • mini
  • 2026-02-18 18:51:50


How to Mount Cloud Drives with Alist for Beginners? A Comprehensive Guide!

Are you looking to mount cloud storage services like Quark Drive and 115 but unsure how to set up AList? Look no further than the software 'AListServer'.

AListServer is a launcher based on AList, a paid software available for download on the App Store. It supports a variety of storage services such as Alibaba Cloud, OneDrive, Tianyi Cloud Disk, 115 Cloud Disk, Quark Cloud Disk, PikPak, Xunlei Cloud Disk, China Mobile Cloud Disk, China Unicom Cloud Disk, Sichuan Telecom Magic Disk, 123 Cloud Disk, Tencent Weiyun, Lanzou Cloud, Little Airplane Cloud Disk, Baidu Cloud Disk, Google Cloud Disk, Cookie Cloud, and UC, among others.

How to Use AListServer Software?

After downloading from the App Store, go to the home page and select the service status. Provide the login credentials for Alist in the account information section.

Click on 'Manage' and then 'Add'. The specific operations will vary depending on the cloud drive you want to mount. For detailed instructions, refer to this link: VidHub User Guide.

Example: How to Mount 115 Cloud Disk? Let's Go Step by Step!

Step 1: Open the Alist home page and check the service status.

Step 2: Add management by logging into Alist. The default username and password are usually 'admin'.

Step 3: Click 'Add', select '115 Cloud Disk' as the drive, mount path: /115, sequence number: 0, leave remarks blank, cache expiration time: 30, do not check 'Web Proxy', set 'WebDAV Strategy' to 'Local Proxy', leave 'Download Proxy URL' blank, do not select 'Extract Folder', for 'Cookie': Open the web version of 115 Cloud Disk, press FN+F12, refresh the page, find the file starting with ?cid= on the left, click into it, find the 'cookie', copy this code, and paste it into the 'cookie' field in Alist. Leave 'QR Code Token', 'Qrcode Source', and 'Root Folder ID' blank. Set 'Page Size' to 56 and 'Rate Limit' to 2. For 'Root Folder ID', open the official 115 Cloud Disk website, enter the folder you want to set up, and click on the number following cid= in the URL. For example, in the URL https://115.com/?cid=249163533602609229&offset=0&tab=&mode=wangpan, the 'Root Folder ID' is 249163533602609229. Then click 'Save'.

Step 4: After successfully mounting the cloud disk with Alist, open VidHub, select 'Add File Source', and choose 'WebDAV'. The server address should be the one found in the WebDAV information at the bottom of the AListServer home page. If it's a local network, use an address starting with 192. Enter the port number: 5244, and the username and password from the account information, which are the Alist login credentials, usually 'admin'. For the path, enter /dav. Click 'Add' and select the files you want to mount, then click 'Complete'.

Common Questions About AListServer Software

  1. What is 'Auto Run'? It helps to automatically start the service when the app is reopened after being killed. Note that services will not automatically start when switching from the background to the foreground.
  2. Why can't I use it when switched to the background? Go to App-Settings-Background Running and turn on the switch.
  3. Why does the service become unavailable or close automatically even with background running enabled? This could be due to failure in keeping the service alive. In extreme cases, the system may still kill the service process. Simply re-enter the app and restart the service.
  4. Why does iOS consume more power? Power consumption varies depending on the device and usage scenario. It is recommended to manually close the service when not in use.
  5. Why doesn't AList update when files are added or deleted from the cloud disk? AList has caching. Refresh the page by clicking the refresh button in the bottom right corner of the browsing page (after accessing the management page from tvOS).
  6. Why can't some videos be played on the built-in browser page? The built-in player is weak. It is recommended to use third-party players.
  7. Why can't I access it from the tvOS after running for a while and switching to the background? This could be due to system background scheduling policies that restrict or kill the service. Usually, enabling minimalist mode and restarting after a power outage can restore access. If a power outage restart does not solve the issue, it may be necessary to abandon using the tvOS version and switch to the iOS version, which is more stable in the background.

Hottest Articles

Latest Articles

Mac System Data Exceeding 200GB? Here’s How to Actually Clear It — A Deep Dive with Heavy Keynote Usage and Time Machine as Examples I. Problem Overview After long-term use, some macOS users discover that “System Data” in Storage Settings grows abnormally large. Common symptoms include: System Data occupying 200GB or more https://cdn.okaapps.com/resource/图2.webp No corresponding files can be located in Finder Deleting caches or log files has little effect Third-party cleaning tools are ineffective Uninstalling and reinstalling apps (such as Keynote) does not help Even after reinstalling macOS, the issue reappears after some time This problem is especially common among heavy productivity users, such as those working extensively with Keynote, Final Cut Pro, or design tools. II. Commonly Tried but Ineffective Solutions Users typically attempt the following methods, most of which fail to solve the problem at its root: Manually deleting directories such as ~/Library/Caches and ~/Library/Logs Using third-party cleaning tools like CleanMyMac or similar utilities Uninstalling and reinstalling Keynote Reinstalling macOS via “Reinstall macOS” These approaches are limited because they do not address the real sources behind System Data inflation. III. What Exactly Is “System Data”? It is important to understand that: System Data is not a real folder, but rather a collection of data that macOS cannot accurately categorize. System Data may include, but is not limited to: macOS system temporary files Application and system caches Portions of the user Library (~/Library) Files Spotlight cannot classify Large resource files inside application packages Local caches from cloud services (such as iCloud or OneDrive) iPhone / iPad backup files Residual data from deleted user accounts Time Machine local snapshots As a result, System Data cannot be reliably inspected or reduced through simple cache deletion or Finder-based browsing. IV. Key Cause #1: Time Machine Local Snapshots Consuming Disk Space How Local Snapshots Work Even when no external drive or NAS is connected, macOS will: https://cdn.okaapps.com/resource/图3.webp Create a Time Machine local snapshot every hour Retain snapshots from the last 24 hours by default If the backup destination remains disconnected, keep local snapshots associated with the most recent full backup These snapshots: Are based on the APFS file system Do not appear as regular files Are entirely counted under System Data In some cases, local snapshots can consume tens or even hundreds of gigabytes. https://cdn.okaapps.com/resource/图4.webp Why They Sometimes Cannot Be Deleted When Time Machine uses a NAS or network storage device as its backup destination, the following situations may occur: The NAS was previously disconnected The network path or IP address changed The backup was not re-“claimed” by the system As a result, macOS may treat these snapshots as belonging to an unreachable backup destination, leading to: tmutil deletion failures Errors such as Stale NFS file handle Snapshots that cannot be reclaimed, causing persistent disk usage V. Key Cause #2: How Keynote and Similar Apps Amplify System Data Keynote itself is not malfunctioning, but its design inherently amplifies System Data usage: Keynote files are actually packages containing large numbers of resources These may include: High-resolution images Embedded videos Fonts Animation and transition assets Spotlight sometimes fails to correctly classify these resources, causing them to be grouped under System Data. For users who frequently create large, media-heavy presentations, steady growth in System Data over time is expected. VI. Effective Solutions (Prioritized) Solution 1: Verify and Restore Time Machine Backup Status (Recommended) Open Disk Utility From the menu bar, select Show APFS Snapshots Select the system Data volume Check whether a large number of Time Machine local snapshots exist If using a NAS as the backup destination: Reconnect the NAS Select the original backup in Time Machine settings Follow the prompts to claim the existing backup Once the backup relationship is properly restored, macOS can automatically manage and reclaim snapshot space. Solution 2: Use Disk Analysis Tools to Identify Real Space Usage It is recommended to use tools that analyze disk usage without automatically deleting files, such as: GrandPerspective EtreCheck The goal is to identify: Which files or directories consume the most space Whether disk usage is abnormally concentrated in specific areas Avoid relying on “one-click cleanup” tools. Solution 3: Check for Residual Data from Old User Accounts If the device previously: Had multiple user accounts Removed accounts without deleting their home folders Then old home directories may still exist and be counted as System Data. Solution 4: Rebuild the System Environment Completely (Last Resort) When System Data usage becomes severely unmanageable and no clear source can be identified, the only definitive solution is: Fully back up all current data Erase the disk and reinstall macOS During setup: Migrate only the user account Do not migrate system settings, applications, or Library data This approach completely removes legacy data structure issues. VII. Long-Term Prevention Tips (for Keynote and Content Creators) Archive older Keynote projects to an external drive or NAS Avoid storing large volumes of presentation files locally for long periods Keep the Time Machine backup destination consistently available Avoid third-party tools that perform automated “system-level cleaning” Periodically monitor disk usage with analysis tools VIII. Conclusion Abnormally large macOS System Data usage is rarely caused by a single cache or log issue. Instead, it is typically the result of Time Machine local snapshots, application package resources, and inherited historical data structures working together. Only by understanding what System Data actually contains—and addressing the root causes—can disk space issues be resolved effectively and long-term.