Monado7 | 5 points
I've found help request threads here even though I know this sub is mainly for links to content. So, sorry about that but I'm desperate at this point.
I've known about the work around for Mega's "exceeded bandwidth quota" for a little while now and know how to do it but for some reason I get this huge error when starting Mega Downloader (that I can screenshot if necessary) that starts with "System.Configuration...". After closing that I get "Error starting web server: The requested service provider could not be loaded or initalized". This happens when the "use streaming server' option is checked or re-checked.
This method I just tried today but I get this error now; "Warning: skipping invalid mega download link". I've tried putting ".co" in the link, using single quotes, adding http:// or a single / to the end of the url when pasting to megadl.
I just can't get past the damn quota limit. Is there another way or am I totally SoL?
MegaTools requires "double quotes" when you put the link. As far as MegaDownloader, you may want to try uninstalling and reinstalling. From what I can tell, you have an error when it's loading up from files, but if that doesn't work, try reverting to a previous build of MegaDownloader.
[-] un_amigo | 3 points | Feb 17 2017 23:07:05
I think to run megadl, the link should be sth like this (with 'https' instead of 'http')
As for megadownloader, why don't you just turn off streaming option?
permalink
[-] Monado7 | 2 points | Feb 17 2017 23:57:15
When I add https:// I get an error "API call 'g' failed: http post failed: curl error: couldnt resolve host name.
Every tutorial for megadownloader method uses IDM and says to use the streaming option. I've tried without streaming and IDM with no luck.
I don't understand why this is happening, my setup is normal. I have WIN10 and Panda Antivirus. My internet according to speedtest.net is 30mbps. There shouldn't be anything stopping me from using these methods. It's very frustrating since Mega is used to host everything and I'm one of the few who can't use it. If I could afford a membership I would at this point.
permalink
[-] un_amigo | 2 points | Feb 18 2017 00:37:17
Can you post some screenshots? Might be easier to troubleshoot.
Was it running smoothly before?
I do not understand why the tutorial would use IDM to download files on Mega. MegaDownloader does that just fine. This is my configurations. I don't use Streaming Server.
permalink
[-] Monado7 | 1 points | Feb 18 2017 01:06:53
This is the guide I'm referring to. All the other google searches returned that guide or a similar one.
To clarify, I've never gotten any of these methods to work. Ever since the quota was implemented, I've had to hope I can get what I want from Google Drive.
I am going to try with your settings and will post some screenshots very soon.
permalink
[-] Monado7 | 1 points | Feb 18 2017 01:51:13
Mega dl/cmd error I get
Mega Downloader 1.7 with your settings and streaming option off
permalink
[-] un_amigo | 2 points | Feb 18 2017 02:58:09
My try with megadl. I'm guessing this could be a DNS issue. Try open the whole link on a browser & change your DNS to Google or OpenDNS. If that doesn't work, then check your firewall (could be Panda, idk). Btw, you can add a path to the megatools folder in the Environment System Variables so that you can call the command anywhere.
As for MegaDownloader. I think there is no .NET 4.0 on your machine as mentioned in the FAQ. Other than that, i've no clue.
Edit: Here is what I found on megatools github
permalink
[-] Monado7 | 1 points | Feb 18 2017 03:17:22
Alright I'll give those a try. Thanks for your help so far, I really appreciate it!
permalink
[-] un_amigo | 2 points | Feb 18 2017 03:24:43
No big deal. Let me know how it goes.
permalink
[-] Monado7 | 1 points | Feb 18 2017 04:12:43
Unfortunately, I'm still getting all the same errors. I changed to google's DNS (8.8.8.8), disabled Panda, updated to .net 4.6.1.
Oh well, I tried.
permalink
[-] denvit | 1 points | Feb 18 2017 11:55:44
The "g" error make me think you need to escape the "!": at least this is what's needed in *nix systems: replace the "!" With "\!" and try again
permalink