streamango.com & streamcherry.com official support

Status
Not open for further replies.
Remote upload isn't something that we can maintain 24/7, sometimes the other side, quite naturally, updates their services to prevent remote uploads and URL resolvers, while we offer an API for our CDN, others might not be that open.

We heavily rely on user feedback and no ticket is left unread, we might not always answer to reports like "FIX REMOTE UPLOAD!!!!!!!!11111" because you most likely weren't the first one reporting it. But this doesn't mean that you shouldn't submit such reports, it just means that we note them, just not always have the time to answer.

As I've explained, the SSL CDN went offline because of Cloudflare, while we did our best with amendments from our side, Cloudflare didn't seem to want to provide enterprise support to their enterprise customers.

Mango and Cherry are still online and will stay online, if you wish to switch your service provider, please do so. See you back in a couple of weeks.

Sending lot's of love to all of our users (nearly a month late valentine?) and thank you for your continued support. We appreciate you.

Edit://

Download Button - Never intended to come, and won't happen anytime soon. We removed it due to user feedback who didn't want a download button at all, a small minority is asking for it, and that is why we offer the API solution, you can just add your download button on your website providing a direct download.

Web upload bug? Adblock Problem? - Never heard any reports regarding this issue in any of the tickets.
The only Adblock Problem we ever noticed was that some ad-index added our static script domain to their lists and thus prevented the user account panel to work as intended.

No Support from the Admin, correct. He doesn't do much. :(
 
Last edited:
Remote upload isn't something that we can maintain 24/7, sometimes the other side, quite naturally, updates their services to prevent remote uploads and URL resolvers, while we offer an API for our CDN, others might not be that open.

Ok so what if "the other side" is Streamango itself? I'm using your remote upload exclusively to "clone" files (remote uploading streamango links to streamango). I understand that it's hard to support 3rd party services who may or may not provide proper API's. But file cloning shouldn't be affected by that. I've never understood why you and Openload hide the cloning functionality under the remote upload API. After all as we can see here if the actual remote upload future breaks it takes down cloning with it which shouldn't be affected (remote uploading streamango links only results in some db queries). So is this getting looked into?
 
Ok so what if "the other side" is Streamango itself? I'm using your remote upload exclusively to "clone" files (remote uploading streamango links to streamango). I understand that it's hard to support 3rd party services who may or may not provide proper API's. But file cloning shouldn't be affected by that. I've never understood why you and Openload hide the cloning functionality under the remote upload API. After all as we can see here if the actual remote upload future breaks it takes down cloning with it which shouldn't be affected (remote uploading streamango links only results in some db queries). So is this getting looked into?

Thanks for the actual great inquiry and issue observation.
Yes, we too have followed their steps by adding it to the remote upload as users tend to copy hundreds if not thousands of files at once. However, we also have the "Copy File(s)" option in the context menu within the file manager, once you right-click on a file or select multiple files. That option, in fact, works properly even if the remote upload service is running awol again.
 
Thank you for responding. I wasn't aware that the file manager "copy files" thingy worked with file ID's from other accounts. Still, that introduces the problem of needing the accounts login creds as opposed to the API login+key which is a bit of a security risk. It would be really great if this could just get added to the API. Since all the functionality for this is obviously already implemented in the backend it shouldn't take more than 30 minutes to expose it through the API.
 
If you cannot maintain remote upload then why offer it? Seriously this is gonna become an issue with you just saying that you cannot maintain it.. that is the start of it... smmfh


Edit: Understandable that you cannot maintain it 24/7.
 
Last edited:
Thank you for responding. I wasn't aware that the file manager "copy files" thingy worked with file ID's from other accounts.
It doesn't; cloning sounds like you are copying something you already have. To me.

Still, that introduces the problem of needing the accounts login creds as opposed to the API login+key which is a bit of a security risk. It would be really great if this could just get added to the API. Since all the functionality for this is obviously already implemented in the backend it shouldn't take more than 30 minutes to expose it through the API.
Revealing any of the above information is a risk for your files and the account.
The recent issue, however, shouldn't hinder you from using the remote upload to clone mango files, they do not count as items in the remote upload queue, which is currently the issue and we are dealing with it.

And for everyone else; all accounts which previously had unlimited remote uploads and filled up the remote upload queue with massive submissions (I warned you), are going to be removed from the programme entirely.
 
So are we suppose to add just 1 link at a time then? i am pretty sure you are speaking of me as well even though you didn't mention names since i usually add a massive amount.. guess i have something to look forward too then :)


Edit: There is also a limitation of files that you can add at a time so remote upload won't keep getting bogged down. most hosts have it,.
 
Last edited:
It doesn't; cloning sounds like you are copying something you already have. To me.

I've tested it - it actually does. By cloning I mean taking an existing streamango link (belonging to another person) and adding it to your account. Some sites call it "cloning" while others call it "attach to my account" or something along those lines.

The recent issue, however, shouldn't hinder you from using the remote upload to clone mango files, they do not count as items in the remote upload queue, which is currently the issue and we are dealing with it.

That's the thing. Cloning using the remote upload API currently returns a status code of 500 and a "server error" status message which I assume is the same issue people are having with actual remote uploads. Also, while you're right that cloning using remote upload doesn't use the queue, if it works the same way on streamango as it does on openload it does use the daily remote upload limits which suggests both cloning and actual remote uploading share some code path. But this is going a bit offtopic. Anyway, glad to hear the issue is being worked on. I still hope at some point the API gets a dedicated path for cloning though.
 
Remote upload has been down for some time now and this is not the first time it has been down so not sure why it is taking so long to fix the same issue that has been fixed many,many times before. maybe not a priority on the things to do list?
 
Hello,

Please test the remote upload again, we tracked down the issues and have updated the system. We hope that with the recent update, we are going to have fewer problems.
 
Remote upload better but still sometimes slow and not instant like it was ( link from openload )
Thanks for fixing it anyway
 
Remote upload is down "Again"


Thanks for the fix!!

Remote upload works but it is so slow that many files end up with an "error" and do not finish uploading.
 
Last edited:
Status
Not open for further replies.
Back
Top