alist-org
Terabox folders and files can't be deleted or renamed.
Please make sure of the following things
-
[x] I have read the documentation. 我已经阅读了文档。
-
[x] I'm sure there are no duplicate issues or discussions. 我确定没有重复的issue或讨论。
-
[x] I'm sure it's due to
AListand not something else(such as Network ,DependenciesorOperational). 我确定是AList的问题，而不是其他原因（例如网络，依赖或操作）。 -
[x] I'm sure this issue is not fixed in the latest version. 我确定这个问题在最新版本中没有被修复。
AList Version / AList 版本
3.44.0 or latest beta
Driver used / 使用的存储驱动
Terabox
Describe the bug / 问题描述
Terabox may have updated something, but I can no longer delete or rename files or folders with Alist.
I notice that if I try to upload a file, it allows me to do some work, but after a moment, it returns to the same state; sometimes this workaround doesn't work.
I have already tried getting new cookies with the same results, so I have no idea what it may be. Maybe there have been some changes in the API, as they have been making some changes to the site interface lately.
Reproduction / 复现链接
Start Alist and try to rename or delete a folder or a file, it would refresh and do nothing.
Config / 配置
{ "force": false, "site_url": "", "cdn": "", "jwt_secret": "6oGo908CLl4IxCPu", "token_expires_in": 48, "database": { "type": "sqlite3", "host": "", "port": 0, "user": "", "password": "", "name": "", "db_file": "/data/data.db", "table_prefix": "x_", "ssl_mode": "", "dsn": "" }, "meilisearch": { "host": "http://localhost:7700", "api_key": "", "index_prefix": "" }, "scheme": { "address": "0.0.0.0", "http_port": 5244, "https_port": -1, "force_https": false, "cert_file": "", "key_file": "", "unix_file": "", "unix_file_perm": "", "enable_h2c": false }, "temp_dir": "/data/temp", "bleve_dir": "/data/bleve", "dist_dir": "", "log": { "enable": true, "name": "/data/log/log.log", "max_size": 50, "max_backups": 30, "max_age": 28, "compress": false }, "delayed_start": 0, "max_connections": 0, "max_concurrency": 64, "tls_insecure_skip_verify": true, "tasks": { "download": { "workers": 5, "max_retry": 1, "task_persistant": true }, "transfer": { "workers": 5, "max_retry": 2, "task_persistant": true }, "upload": { "workers": 5, "max_retry": 0, "task_persistant": false }, "copy": { "workers": 5, "max_retry": 2, "task_persistant": true }, "decompress": { "workers": 5, "max_retry": 2, "task_persistant": false }, "decompress_upload": { "workers": 5, "max_retry": 2, "task_persistant": false }, "allow_retry_canceled": false }, "cors": { "allow_origins": [ "" ], "allow_methods": [ "" ], "allow_headers": [ "*" ] }, "s3": { "enable": false, "port": 5246, "ssl": false }, "ftp": { "enable": false, "listen": ":5221", "find_pasv_port_attempts": 50, "active_transfer_port_non_20": false, "idle_timeout": 900, "connection_timeout": 30, "disable_active_mode": false, "default_transfer_binary": false, "enable_active_conn_ip_check": true, "enable_pasv_conn_ip_check": true }, "sftp": { "enable": false, "listen": ":5222" }, "last_launched_version": "dev" }
Logs / 日志
Nothing much just the commands with no errors whatsoever.
It seems like you're experiencing an issue with Alist where Terabox folders and files can't be deleted or renamed. This might be due to recent changes in Terabox's API or interface. Let's try to address this issue step by step:
-
Check for API Changes: Since you've mentioned that Terabox might have updated something, it's possible that their API has changed. This could affect how Alist interacts with Terabox. You might want to check Terabox's API documentation or any recent announcements for changes.
-
Update Alist: Ensure that you are using the latest version of Alist. Sometimes, updates include fixes for compatibility with third-party services like Terabox.
-
Review Alist Configuration: Double-check your Alist configuration to ensure everything is set up correctly. Pay special attention to any settings related to Terabox.
-
Logs and Debugging: Although you mentioned there are no errors in the logs, enabling more detailed logging might help identify the issue. Look for any warnings or unusual entries that might give a clue.
-
Community and Support: Consider reaching out to the Alist community or support channels. Other users might have encountered the same issue and could have solutions or workarounds.
-
Fallback Options: If the issue persists, you might need to consider alternative methods for managing your Terabox files until a fix is available.
If you need further assistance or have additional information, feel free to share it here. I'm here to help!
🪧 Tips
For further assistance, please describe your question in the comments and @petercat-assistant to start a conversation with me.![petercat-assistant[bot] avatar](https://avatars.githubusercontent.com/in/875736?v=4 "Published by a pub.dev verified publisher"){kind=small}
Renaming and deleting still work fine for me. Please make sure you have entered the correct cookie. (However, uploading large files seems to have problems in the latest version, which may be related to 3b71500f237c4cb3427ce11cb6675fa9ba7006b6, which doesn't seem to be relevant to your question.)
I have tried to change the cookies many times, and it doesn't work. Sometimes it lets me rename or delete, but most of the time it doesn't. I tried with other accounts, and it's the same. It's random. About the upload, it doesn't matter if it's a 1 MB or a 1 GB file; it will give you the error I posted in your previous PR about the JSToken not found.
I have been experiencing since they add the AI page on the website, so I suspect that somehow something must have changed.
I tried IPs and accounts in and outside of Japan, as well as new/old accounts, and none of them could reproduce your issue. Before anyone else runs into a similar problem and provides more information, I can't help you more.
I tried IPs and accounts in and outside of Japan, as well as new/old accounts, and none of them could reproduce your issue. Before anyone else runs into a similar problem and provides more information, I can't help you more.
You're using the last beta or the 3.44.0 stable version too?
I'm using Alist on my PC and a docker running on a Miami server, I live on the Caribbean Dominican Republic, and I had been facing the same problem on both, my PC and the docker.
I noticed that when the site uses reCAPTCHA, it will give me that jsToken error (not always, but most of the time) when trying to upload anything. A few days ago, I could upload again without problems, but until a few hours ago, I started getting this error:
Error [terabox] failed to create file, errno: 10
And on the console:
2025/05/20 23:47:51.245186 WARN RESTY Post "https://c-jp.terabox.com/rest/2.0/pcs/superfile2?app_id=250528&channel=dubox&clienttype=0&method=upload&partseq=509&path=%252FCloudless.zip&uploadid=P1-MTAuMjUyLjcwLjI2OjE3NDc3ODM4MjU6OTAxODg1NzM1NzQzMDYwODc3NQ%3D%3D&web=1": context deadline exceeded (Client.Timeout exceeded while awaiting headers), Attempt 1
It's a 4 GB zip file; nothing in the logs. I'm not that good at debugging, so I have no idea if it's just TeraBox doing weird stuff or something else. Back then, there was an issue like this when you tried to upload anything bigger than 8 GB that I reported last year, and it got fixed by @Jason-Fly #7498.
About the other problem with the files or folder that I can't move, rename, or delete: it gets somewhat fixed if I try to upload something successfully to TeraBox with Alist, either by WebDAV or by Alist itself. However, as you can see, it's something that has been failing since the changes made to the site (a couple of months now). I never had these problems before.
One more thing I have been dealing with is the slow upload speed I get when using Tera with Alist. It's somewhat stuck at 3-4 MB/s. Any idea why? Uploads by the TeraBox client or through the site are 100% faster. I get between 19-40 MB/s speed.
BTW, thanks for trying to help me out, and sorry for the trouble with this situation.
Hey, @URenko found this repo from someone that uses NodeJS tool for interacting with the TeraBox Api, and he did some some fixes to his Api repo to fix the chunks upload, the time out and the files/folders rename, delete and move recently: https://github.com/seiya-npm/terabox-api https://github.com/seiya-npm/terabox-api/commits/package/ https://github.com/seiya-npm/terabox-api/commit/b1902e4ffcb6c6d8057dd9db3d562b79f30ed27d https://github.com/seiya-npm/terabox-api/commit/df932382ea2973eec0218225e29493be45230b77
I'm not GO programmer, so there is not much I can do about.
It seems you're experiencing an issue with Terabox folders and files not being able to be deleted or renamed using Alist. This might be due to recent updates or changes in the Terabox API or site interface, as you've mentioned.
Here are a few steps you can take to troubleshoot and potentially resolve the issue:
-
Check for Updates: Ensure that you are using the latest version of Alist. Sometimes, issues are resolved in newer versions.
-
API Changes: If Terabox has updated their API, it might require changes in the Alist code to accommodate these updates. You might want to check if there are any recent updates or patches from the Alist community or developers addressing this issue.
-
Logs and Debugging: Since the logs don't show any errors, you might want to enable more detailed logging or debugging to capture any subtle issues that might not be immediately apparent.
-
Community and Support: Engage with the Alist community or support forums to see if others are experiencing similar issues and if there are any known workarounds or fixes.
-
Re-authentication: As you've tried getting new cookies, ensure that the authentication process is correctly implemented and that there are no changes required in the authentication flow.
If these steps do not resolve the issue, it might be beneficial to report this to the Alist developers if it hasn't been reported yet. They might need to investigate and update the integration with Terabox.
🪧 Tips
For further assistance, please describe your question in the comments and @petercat-assistant to start a conversation with me.
You're using the last beta or the 3.44.0 stable version too?
3.44.0 with some personal fixes
Error [terabox] failed to create file, errno: 10
As I said earlier, uploading large files seems to be problematic in the latest version (erroro 10). You can try the fix in my fork (binary available at https://github.com/URenko/alist/actions/runs/14942481665 ), it may be related to 3b71500 (not completely sure yet). But this is another problem, it has nothing to do with the jsToken problem you are facing.
2025/05/20 23:47:51.245186 WARN RESTY Post ...: context deadline exceeded (Client.Timeout exceeded while awaiting headers), Attempt 1
This is normal, it will retry the same request.
One more thing I have been dealing with is the slow upload speed I get when using Tera with Alist. It's somewhat stuck at 3-4 MB/s. Any idea why? Uploads by the TeraBox client or through the site are 100% faster. I get between 19-40 MB/s speed.
One difference is that Terabox can upload multiple chuncks at the same time, while alist currently only uploads one chunck at the same time. But at the same time, it depends on your network environment. I can reach over 20MB/s in the proper network environment and multi-file upload (with proper WebDAV client).
Seiya's fix doesn't seem to be related to the jsToken you encountered (move, rename, or delete), and some fixes are already included in #7498.
Based on your description, I recommend that you try Terabox web pages and seiya's clients on your Miami server's network environment (e.g. through a proxy) to locate the problem (e.g. whether reCAPTCHA is frequently encountered or additional operations are required).
You're using the last beta or the 3.44.0 stable version too?
3.44.0 with some personal fixes
Error [terabox] failed to create file, errno: 10As I said earlier, uploading large files seems to be problematic in the latest version (erroro 10). You can try the fix in my fork (binary available at https://github.com/URenko/alist/actions/runs/14942481665 ), it may be related to 3b71500 (not completely sure yet). But this is another problem, it has nothing to do with the jsToken problem you are facing.
2025/05/20 23:47:51.245186 WARN RESTY Post ...: context deadline exceeded (Client.Timeout exceeded while awaiting headers), Attempt 1This is normal, it will retry the same request.
One more thing I have been dealing with is the slow upload speed I get when using Tera with Alist. It's somewhat stuck at 3-4 MB/s. Any idea why? Uploads by the TeraBox client or through the site are 100% faster. I get between 19-40 MB/s speed.
One difference is that Terabox can upload multiple chuncks at the same time, while alist currently only uploads one chunck at the same time. But at the same time, it depends on your network environment. I can reach over 20MB/s in the proper network environment and multi-file upload (with proper WebDAV client).
Seiya's fix doesn't seem to be related to the jsToken you encountered (move, rename, or delete), and some fixes are already included in #7498.
Based on your description, I recommend that you try Terabox web pages and seiya's clients on your Miami server's network environment (e.g. through a proxy) to locate the problem (e.g. whether reCAPTCHA is frequently encountered or additional operations are required).
I had tested a couple of builds, especially before the 3.43.0 version with the traffic limiter implementation, to no avail; they still fail to upload files. So, TeraBox did, in fact, make some changes. With your fix, uploads are working again just fine. I use TeraBox and OneDrive a lot on a daily basis for backups.
I mostly upload any file bigger than 2 GB using the alist interface because of the limitation of WebDAV when running it on Linux; with Windows, it's like 4 GB. I didn't want to set up a Windows machine for it (too little gain). If you have a way to overcome the limit over WebDAV or a client that allows uploads bigger than 2 GB over WebDAV, it would be appreciated.
Regarding the upload speed, before I could maintain a speed of 8-12 MB/s upload transfer with alist, but lately, it barely reaches 2-4 MB/s max (with paid premium). So, as you can imagine, it can take hours to upload big files. I can somewhat mitigate the issue when I'm uploading multiple files.
The error about the upload with the JS token is something that I have been dealing with since the changes made to the website, and as I said, it's random. When it happens, I had've try with proxy/VPN, different Internet providers and places. I would get the same thing. I rotate the cookie from time to time, and it doesn't matter that I change it when it happens; sometimes it works, but most of the time it doesn't. To me, it's like they kind of raised the level of security, and Alist failed to handle the issue. I can download or see the files without issue, so it's strange.
Now, about the problem with the files/folders rename, move, and delete actions.
Try with a freshly started Alist run, then first try to rename a file/folder or try to delete an already uploaded file or upload something to the TeraBox website (not through Alist, because if you upload something with Alist, it will start to work again for rename and delete actions). Move, for some reason, is working again now, at least on all the tests I have run so far.
I have a running Docker instance with Render if you want to check it out yourself. It's running on a EU server, and it has a TeraBox account I just created to test with another new account:
https://nothing-4mup.onrender.com
U: admin
P: 123456
Pst: sorry for the late reply, it has been a stressful week.
You're using the last beta or the 3.44.0 stable version too?
3.44.0 with some personal fixes
Error [terabox] failed to create file, errno: 10As I said earlier, uploading large files seems to be problematic in the latest version (erroro 10). You can try the fix in my fork (binary available at https://github.com/URenko/alist/actions/runs/14942481665 ), it may be related to 3b71500 (not completely sure yet). But this is another problem, it has nothing to do with the jsToken problem you are facing.
2025/05/20 23:47:51.245186 WARN RESTY Post ...: context deadline exceeded (Client.Timeout exceeded while awaiting headers), Attempt 1This is normal, it will retry the same request.
One more thing I have been dealing with is the slow upload speed I get when using Tera with Alist. It's somewhat stuck at 3-4 MB/s. Any idea why? Uploads by the TeraBox client or through the site are 100% faster. I get between 19-40 MB/s speed.
One difference is that Terabox can upload multiple chuncks at the same time, while alist currently only uploads one chunck at the same time. But at the same time, it depends on your network environment. I can reach over 20MB/s in the proper network environment and multi-file upload (with proper WebDAV client). Seiya's fix doesn't seem to be related to the jsToken you encountered (move, rename, or delete), and some fixes are already included in #7498. Based on your description, I recommend that you try Terabox web pages and seiya's clients on your Miami server's network environment (e.g. through a proxy) to locate the problem (e.g. whether reCAPTCHA is frequently encountered or additional operations are required).
I had tested a couple of builds, especially before the 3.43.0 version with the traffic limiter implementation, to no avail; they still fail to upload files. So, TeraBox did, in fact, make some changes. With your fix, uploads are working again just fine. I use TeraBox and OneDrive a lot on a daily basis for backups.
I mostly upload any file bigger than 2 GB using the alist interface because of the limitation of WebDAV when running it on Linux; with Windows, it's like 4 GB. I didn't want to set up a Windows machine for it (too little gain). If you have a way to overcome the limit over WebDAV or a client that allows uploads bigger than 2 GB over WebDAV, it would be appreciated.
Regarding the upload speed, before I could maintain a speed of 8-12 MB/s upload transfer with alist, but lately, it barely reaches 2-4 MB/s max (with paid premium). So, as you can imagine, it can take hours to upload big files. I can somewhat mitigate the issue when I'm uploading multiple files.
The error about the upload with the JS token is something that I have been dealing with since the changes made to the website, and as I said, it's random. When it happens, I had've try with proxy/VPN, different Internet providers and places. I would get the same thing. I rotate the cookie from time to time, and it doesn't matter that I change it when it happens; sometimes it works, but most of the time it doesn't. To me, it's like they kind of raised the level of security, and Alist failed to handle the issue. I can download or see the files without issue, so it's strange.
Now, about the problem with the files/folders rename, move, and delete actions.
Try with a freshly started Alist run, then first try to rename a file/folder or try to delete an already uploaded file or upload something to the TeraBox website (not through Alist, because if you upload something with Alist, it will start to work again for rename and delete actions). Move, for some reason, is working again now, at least on all the tests I have run so far.
I have a running Docker instance with Render if you want to check it out yourself. It's running on a EU server, and it has a TeraBox account I just created to test with another new account:
https://nothing-4mup.onrender.com U: admin P: 123456
Pst: sorry for the late reply, it has been a stressful week.
Same thing here. I've been facing the same issues; as you mentioned, rename or delete isn't working at all. I needed to use the TeraBox website in order to do that. Trying to upload something with alist works. I have noticed that it doesn't matter if it gets uploaded or if the upload fails; it will work. After that, I can delete or rename without an issue.
Hey, @URenko, thanks for the fix. I have been using it for a couple of days now. I couldn't upload anything to TeraBox at all, but recently uploads tend to keep restarting because of a timeout. I get that jsToken error from time to time as well when trying to upload anything, as OP mentioned. I'm in Miami, and I run alist just locally on a dedicated workstation I have for storage and running containers.
Unfortunately, since alist has been acquired by a company with a bad reputation #8649 :( , I will not be continuing its development.
But luckily some people started working on implementing a Terabox backend for rclone ( https://github.com/rclone/rclone/pull/8508 ). While I doubt it will ever be merged into mainline, let's move to rclone. By the way, the discussion in that PR partly answers your questions.
Unfortunately, since alist has been acquired by a company with a bad reputation #8649 :( , I will not be continuing its development.
But luckily some people started working on implementing a Terabox backend for rclone ( rclone/rclone#8508 ). While I doubt it will ever be merged into mainline, let's move to rclone. By the way, the discussion in that PR partly answers your questions.
Lord, just wake up to THIS s*show. Saw your reply by mail. The choice done by the team is just stupid to me, @URenko.
Luckily the community looks like is making a fork with a lot of the previous supporters moving there, working in replacing the code relate to alist web/API: https://github.com/OpenListTeam/OpenList
Well, that's more like what I suspected and mentioned; they kind of force a jsToken check request for most of the tasks (so that must be implemented, I guess), and that's the reason why renaming and deleting (moving previously) weren't working when you don't perform any action that triggers the jsToken, like uploads with Alist (it doesn't matter if you don't finish the upload, but it should start to upload in order to make an action). If that doesn't happen, it will flag you when you do those basic things from time to time. That's why I mentioned the reCAPTCHA thing, and that at least could probably be fixed with the user agent change to what Seiya did on her API implementation, but I don't know anything about GO.