-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Known issue: 404 Not found. #774
Comments
Thank you! |
But how, exactly? |
Can anyone please guide me how to do this..... I have literally no idea what to do to fix it..... |
If you add the code below to ytdl-cord, it works normally. |
That method won't return video length :/ |
That works great for me.. the only downside is that i cant change it on repl.it since modules are protected :/ |
You can use shell and enter these command to edit it: |
url.searchParams.set('c', 'TVHTML5');
url.searchParams.set('cver', '7.20190319'); |
Line 86 in 3134356
Line 117 in 3134356
If you modify the above two lines as follows, you can see that it returns normally.
|
Oof, thanks you! |
I don't see that folder. |
What are you using? |
I have used Railway.app to deploy the bot |
I am getting the same |
Do you have bash/console access? |
No but I can view deploy logs. |
Sorry but I can't help you then. |
If you're facing this issue this must be probably in repl. Whatever you try you won't be able to resolve it in repl it's because it has a error in the node_module folder which will not be available in your repl project. The only way you can resolve this is by using anyother IDE (ie: Visual Studio Code)
Also check whether you have updated ytdl if not it will show you this error here type it out in terminal/console
@wolf-yuan-6115 @eritislami pin this if possib;e |
Can i edit the file and then reupload it to repl? |
i changed it and it still does not work |
Did you change the ytdl-cord too? |
Same for me.. The only way i could get this to work was by modifying the module. But like i mentioned before, that is not an option since repl.it doesnt allow me to do that. |
I got it to work on my repl 🥳 I figured out i cant edit a file using shell, but i can move and rename. I edited the info.js file using vscode, uploaded to my repl, renamed the original info.js to info.example and then moved the new one to the folder. |
For who can't modify node_modules; Remove
Update: You may need to change ytdl-core to wolf-ytdl in commands, I recommended to modify node_modules if you can do it. |
can i just wait a couple of days for it to update its self or do have to change stuff |
wold-ytdl works but no sound comes out |
Hmm, i will re-check some code |
It works for me...
…On Thu, Jun 24, 2021 at 1:48 AM Marshxan ***@***.***> wrote:
For who can't modify node_modules;
Remove ytdl-core and install wolf-ytdl instead, you can also run these
script:
npm uninstall ytdl-core
npm i wolf-ytdl
*Update:*
You may need to change ytdl-core to wolf-ytdl in commands, I recommended
to modify node_modules if you can do it.
wold-ytdl works but no sound comes out
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#774 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AN4MEDC6NJGIQEUNMRXBUWDTUIM5BANCNFSM47DO2CDQ>
.
|
can you add me on discord Marshxan0001 and help me |
do you think I can just wait a week or two and it will fix by its self |
No, probably they google changed their API, so... yeah... |
Seems fent need to code a API change alert lol |
You can use this thing to solve it temporarily |
so how would i get the bot working again im not the best at coding and i want it to work ;) |
i have tyr ervrything on replit |
how to fix it |
get newest commit & |
Wow, it just worked. Thank you! |
If you seen
Error: 404 Not found
in your console, this is not an error!This is a problem with ytdl-core or YouTube API. This error will occur in these case:
There is no solutions at this moment, please don't open issue like this.
Update:
ytdl-core
already fixed this bug, just install ytdl-core master branch, this patch is not pushed to npm yet.Another update:
There is a method to fix this issue, please see #774 (comment)
Feel free to commit on this issue if you have any solution.
The text was updated successfully, but these errors were encountered: