MainSilent / Discord-Screenshare

First ever discord video screenshare SELFBOT
298 stars 80 forks source link

WebDriverError: unknown error: DevToolsActivePort file doesn't exist #50

Closed just-rich closed 2 years ago

just-rich commented 2 years ago

Well I was able to get it running on my raspberry pi 4, but it was terrible- sluggish and bad quality. I'm sure there's some way to improve it but I don't have the knowledge for that.

So I'm using an AWS EC2 instance to see if I can get this running, ran into a lot off issues which I've managed to fix until this one- not some easy workaround or fix (or at least none I found on google/stackoverflow)

Anyone run into this issue?

` let err = new ctor(data.message) ^

WebDriverError: unknown error: DevToolsActivePort file doesn't exist at Object.throwDecodedError (/home/ubuntu/videostream/node_modules/selenium-webdriver/lib/error.js:522:15) at parseHttpResponse (/home/ubuntu/videostream/node_modules/selenium-webdriver/lib/http.js:549:13) at Executor.execute (/home/ubuntu/videostream/node_modules/selenium-webdriver/lib/http.js:475:28) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {`

MainSilent commented 2 years ago

It appears to be a dependency issue, I recommend using the Dockerfile.

just-rich commented 2 years ago

It appears to be a dependency issue, I recommend using the Dockerfile.

So i'm trying out this Docker thing, but run into this when I build COPY failed: file not found in build context or excluded by .dockerignore: stat .env: file does not exist

MainSilent commented 2 years ago

Make sure to have the .env file in the same directory as Dockerfile.

just-rich commented 2 years ago

Make sure to have the .env file in the same directory as Dockerfile.

Oh ok. I thought docker clones the repo already, so I just need .env in before running build and it will clone repo as well?

got this error now error Couldn't find a package.json file in "/Discord-Screenshare"

after docker build is finished how do i run this?

MainSilent commented 2 years ago

It will run after the build, The .env is copied for configuration.

just-rich commented 2 years ago

It will run after the build, The .env is copied for configuration.

I can't get it to run no matter what I do...

I do the build and it ends with this error error Couldn't find a package.json file in "/videostream"

then i try to run it docker run dockerfile or sudo docker run dockerfile i get these;


docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create": dial unix /var/run/docker.sock: connect: permission denied.
See 'docker run --help'.
ubuntu@ip-172-31-23-133:~/videostream$ sudo docker run dockerfile
Unable to find image 'dockerfile:latest' locally
docker: Error response from daemon: pull access denied for dockerfile, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.```
MainSilent commented 2 years ago

This is docker related issue, It's not able to make a connection with docker.

just-rich commented 2 years ago

This is docker related issue, It's not able to make a connection with docker.

Ok iI got it running but got that error for stage channels. Where is the node_modules folder stored at so I can go in and edit it? After docker build, where it does save all the files?

MainSilent commented 2 years ago

The new version is using discord.js-selfbot-v13, Stage channels shouldn't be an issue.

just-rich commented 2 years ago

The new version is using discord.js-selfbot-v13, Stage channels shouldn't be an issue.

Ok so I just did a brand new clone, edited the .env, build from dockerfile in it. but got this error after build.


    const invalidToken = new Error(WSCodes[4004]);
                         ^

Error [TOKEN_INVALID]: An invalid token was provided.
    at WebSocketManager.connect (/Discord-Screenshare/node_modules/discord.js-selfbot-v13/src/client/websocket/WebSocketManager.js:129:26)
    at Client.login (/Discord-Screenshare/node_modules/discord.js-selfbot-v13/src/client/Client.js:335:21)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  [Symbol(code)]: 'TOKEN_INVALID'
}```
just-rich commented 2 years ago

wait discord asks to change password for this alt, idk why suddenly. was working just fine few hours ago

EDIT: GOT BOT WORKING! GONNA TRY IT OUT RN

hey after docker build, I can't seen to just use the docker run command I always have to build to start/restart it. what am i missing?

ExclusiveRishi commented 2 years ago

The new version is using discord.js-selfbot-v13, Stage channels shouldn't be an issue.

Ok so I just did a brand new clone, edited the .env, build from dockerfile in it. but got this error after build.

    const invalidToken = new Error(WSCodes[4004]);
                         ^

Error [TOKEN_INVALID]: An invalid token was provided.
    at WebSocketManager.connect (/Discord-Screenshare/node_modules/discord.js-selfbot-v13/src/client/websocket/WebSocketManager.js:129:26)
    at Client.login (/Discord-Screenshare/node_modules/discord.js-selfbot-v13/src/client/Client.js:335:21)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  [Symbol(code)]: 'TOKEN_INVALID'
}```

Hey @rich1488 I'm facing same issue, Can you tell me how did you fixed it?

MainSilent commented 2 years ago

The new version is using discord.js-selfbot-v13, Stage channels shouldn't be an issue.

Ok so I just did a brand new clone, edited the .env, build from dockerfile in it. but got this error after build.

    const invalidToken = new Error(WSCodes[4004]);
                         ^

Error [TOKEN_INVALID]: An invalid token was provided.
    at WebSocketManager.connect (/Discord-Screenshare/node_modules/discord.js-selfbot-v13/src/client/websocket/WebSocketManager.js:129:26)
    at Client.login (/Discord-Screenshare/node_modules/discord.js-selfbot-v13/src/client/Client.js:335:21)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  [Symbol(code)]: 'TOKEN_INVALID'
}```

Hey @rich1488 I'm facing same issue, Can you tell me how did you fixed it?

Have you set the token in .env?

ExclusiveRishi commented 2 years ago

Yup I have, tried both with and without quotes