After first download with youtube-dl my access to youtube was blocked - youtube

I used youtube-dl to download a video and use VPN to access youtube.
After connect to the VPN my ip was changed and I can see youtube.com.
But after try to download first video I can not download any thing and the log is:
ERROR: Unable to download webpage: <urlopen error [Errno 101] Network is
unreachable> (caused by URLError(OSError(101, 'Network is unreachable'),))
So I looking for solution for this error and just find somthing like this link:
https://github.com/ytdl-org/youtube-dl/issues/9438
And after I read it, I can not find any solution for my case.
I try to curl address also but this try is faild and it shown me this error:
* Could not resolve host: www.youtube.com
* Closing connection 0
curl: (6) Could not resolve host: www.youtube.com
youtube-dl --version
2018.03.14
curl --version
curl 7.58.0 (x86_64-pc-linux-gnu) libcurl/7.58.0 OpenSSL/1.1.1a zlib/1.2.11
And wonderful thing is I can see youtube.com in my firefox browser but I can not access to it with curl or youtube-dl.
It seems somthing crashed after about 5 minutes and I can not access to youtube website.

After searching a lot, I realized that the problem was from CURL and VPN so I deleted the 'curl'.
And 'youtube-dl' completely removed and reinstalled.
And then it works for me.

Related

How do I resolve this OSError: [Erno 48] Address already in use error while working with the byob botnet on GitHub?

(I have seen other solutions to "Errno 48" issues on StackOverflow, but none have been successful yet.)
I am trying to develop a botnet using byob on github here: https://github.com/malwaredllc/byob
I am encountering a address in use error every time I run the command sudo ./startup.sh. It returns OSError: [Errno 48] Address already in use.
However when I attempt to use the ps -fA | grep python and kill the associated 502 18126 16973 0 9:16PM ttys000 0:00.00 grep python by using kill -9 181216, I get this error: kill: kill 18126 failed: no such process.
Does anyone have any idea what to do?
I am using a "MacOS M1Pro Chip OS V12.0.1 Monterey". Also the program byob is trying to run on port 5000 of IPv4 127.0.0.1 (this is a generic IP not specifically mine). http://127.0.0.1/5000.
In case you try to duplicate the problem you need to install docker.io or the docker desktop app depending on os then navigate to cd <outer-dir>/byob-master/web-gui then execute sudo ./startup.sh. The code will not work without access to docker, and the program needs to be ran with admin perms using the prefix sudo. The actual downloads take a while and it will prompt you to restart once. Then when you run it again, I encounter this problem...
Please let me know if someone was able to fix this. Thanks!

Docker EE installation: gpg: no valid OpenPGP data found

I tried to follow the instruction from Docker EE instruction.
https://docs.docker.com/ee/docker-ee/ubuntu/#set-up-the-repository
I met the problem with step five: Add Docker’s official GPG key using your customer Docker Engine - Enterprise repository URL.
curl -fsSL "${DOCKER_EE_URL}/ubuntu/gpg" | sudo apt-key add -
When I type this command, terminal returned
curl: (22) The requested URL returned error: 403
gpg: no valid OpenPGP data found.
I tried to use the browser open the url of "${DOCKER_EE_URL}/ubuntu/gpg", it also returns 403.
Then, I thought maybe my local environment is not clean, so I rent server from DigitalOcean, but it still returned the same message.
Could someone, please point me into the right direction? Thank you!
Update: I tried to use centos, it can't work, either.
I had the same issues this morning. For me the issue is now resolved.
Looks like it takes a couple of hours before the key is available (after requesting a trial license).

Firebase crash batch upload fail for unknown reason

I'm trying to upload DSYM s to firebase, which worked perfectly till a few days before. When I start the script, and it s start loggin, a few lines after it stuck for a few minutes and then fails.
/Users/..../dSYMs/DF...C47.dSYM/Contents/Resources/DWARF/leveldb: warning: function at offset 0x51662 has no name
./Pods/FirebaseCrash/upload-sym-util.bash:365: error: upload: Unable to upload symbol file (reason unknown).
The interesting thing is, in firebase console it tells me the upload was successful:
Future stack traces for UUID B4...AAF will
be symbolicated using the uploaded symbol file.
But it never, because I ve "uploaded" a few like this, and since that, I had a few more crashes, but still not symbolicated...
What's going on?
FYI: I'm using firebase crashreporting since February, and it worked nicely. I updated my mac to High Sierra a few days ago.
Thy
TL;DR
Look for the following line in upload-sym-util.bash:
HTTP_STATUS=$(curl ${CURLOPT} -sfL -H 'Content-Type: text/plain' -H "Authorization: Bearer ${BEARER_TOKEN}" -w '%{http_code}' -T "${FILE}" "${UPLOAD_URL}")
And append --http1.1 at the end so that it becomes:
HTTP_STATUS=$(curl ${CURLOPT} -sfL -H 'Content-Type: text/plain' -H "Authorization: Bearer ${BEARER_TOKEN}" -w '%{http_code}' -T "${FILE}" "${UPLOAD_URL}" --http1.1)
Explanation
We have been having this issue when uploading the DSYM files on Firebase via XCode. What was driving us crazy was that the process seemed to randomly succeed and fail. When the upload failed, it did after a few minutes.
We managed to run the offending curl command manually and discovered that it was returning an HTTP status code of 000 which seems to happen when the connection is closed before the server actually returns anything (eg: timeout). By using the --verbose argument we discovered that curl was aborting the call with an INTERNAL_ERROR (err 2) which seemed to be linked with the use of HTTP/2. We managed to confirm this when we found out that the only machine that was able to upload the DSYM files correctly had the same version of curl as everyone else but with no HTTP/2 support, which was apparently added in High Sierra. We forced curl to use HTTP1.1 and it did the trick.

register service worker with http

I am trying to register service worker in my project
but is is giving error as
"Failed to register a ServiceWorker: An SSL certificate error occurred when fetching the script."
and i opened chrome with insecure using below command
/opt/google/chrome/chrome --user-data-dir=/tmp/foo --unsafely-treat-insecure-origin-as-secure=https:://localexample.com
after opening url in chrome insecure window it is still giving error as same in console like "Failed to register a ServiceWorker: An SSL certificate error occurred when fetching the script" and in terminal it is giving error as "ERROR:cert_verify_proc_nss.cc(918)] CERT_PKIXVerifyCert for localexample.com failed err=-8172".
Any solution ???
open chrome in insecurity mode then you can install and implement service worker without using https:
Type below command in terminal (Ubuntu) :
$ /opt/google/chrome/chrome --user-data-dir=/tmp/foo --unsafely-treat-insecure-origin-as-secure=http://example.com
Right click on google chrome icon and open properties and change the target field in shortcut section to "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --user-data-dir=C:\dir --ignore-certificate-errors --unsafely-treat-insecure-origin-as-secure=<your site url>".
Now when you launch chrome again the service worker will work.
So I repeat mostly the answer from Nr.
If that specific DomException was happened locally, when accessing web resource at local machine with certificate, one of these latest version of browser launches may had helped:
open -a Opera.app --args --user-data-dir=/tmp/foo --ignore-certificate-errors --unsafely-treat-insecure-origin-as-secure=https://localhost:8111
open -a Brave\ Browser.app --args --user-data-dir=/tmp/foo --ignore-certificate-errors --unsafely-treat-insecure-origin-as-secure=https://localhost:8111
open -a Google\ Chrome.app --args --user-data-dir=/tmp/foo --ignore-certificate-errors --unsafely-treat-insecure-origin-as-secure=https://localhost:8111
Chromium browser did not start with these settings to allow to overcome this specific DomException for using SSL with service worker locally.
This person provided some insights as a story as well for this matter: https://deanhume.com/testing-service-workers-locally-with-self-signed-certificates/

Deployd dpd "app" - listening on port then goes right to "bye"

I had deployd running just fine on my MAC OS, then I let it sit for a couple weeks.
Went back to it, launching the Deployd server with "dpd app_name"
I get the following:
listening on port 2403
type help for a list of commands
dpd > bye
I've tried to install/reinstall multiple times, it's doing it also on all deployd website examples.
I've tried changing the port, no luck
I've looked for an error log file. Couldn't find any.
I tried to go on Chrome and Safari, same thing: "Connection Refused".
Any idea, anyone?
Thanks in advance!
That happened to me, just type sudo before dpd.
$ sudo dpd
If you run:
$ DEBUG=* dpd
inside the app folder you will probably see the problem is with mongod, and run with sudo solves it.

Resources