Setup script is confusing
Current and Crowdin (3.5.2). Test on YouTube and VK (audio, video):
Trying to download from YouTube resulted in a warning:
After trying to update: "npm install npm@latest -g". There is no result, no matter what the order. Problem with code or with npm 8.19.2/node 18.9.0, maybe this version does not work correctly with this code.
Your service on co.wukko.me is now work. And yes turn that shit off: https://github.com/wukko/cobalt/blob/current/src/modules/sub/currentCommit.js
in order to get youtube module to work, you have to do this (for now). i forgot to add it to readme. hopefully node-ytdl-core maintainers will stop being so stubborn and will accept the actual fix for the signature decoding issue.
vk should work without any modifications, are you sure it works on co.wukko.me, but not when hosted locally?
and finally, what's wrong with commit info module? all data passed through to it is local and is never accessed or modified by the service user.
if it's easier for you to use russian to explain the issue, feel free to do it.
after looking at your screenshots again, you haven't followed all the requirements and setup steps. do that, then come back.
there's no port in .env file, therefore the web app can't locate the api server.
both vk and youtube may not work because of missing stream hash in .env file that's genereated by the setup script and is required for streamable stuff to work.
this is exactly why readme file is called that way and why you should read it before opening issues.
I have fixed inaccuracies in the setup script, according to which the setup becomes more understandable. The problem has been solved. Except that the user must still connect to the host, which was specified during the initial setup. So if the user defined the initial address as 127.0.0.1 and connected from a browser to localhost:9000, or from another machine in the internal/local network, the initiator will bump to the defined address 127.0.0.1, not counting the port. And originally the default connection type was specified even for localhost only by https, which caused connection problems and because of this. However, created a pull request.
i am currently working on an update that fixes this issue