kijart / youtube-proxy Goto Github PK
View Code? Open in Web Editor NEWYouTube proxy API that search and stream videos/audios
youtube-proxy's Introduction
youtube-proxy's People
Contributors
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
Stargazers
Watchers
youtube-proxy's Issues
Frozen app
Sometimes the application freezes and crashes the entire server.
> [email protected] start /app
> npm run start:pro
> [email protected] start:pro /app
> NODE_ENV=production node src/index.js
Listening on port 3000 in production mode over HTTP
Error: type reelShelfRenderer is not known
at parseItem (/app/node_modules/ytsr/lib/parseItem.js:70:13)
at catchAndLogFunc (/app/node_modules/ytsr/lib/parseItem.js:77:12)
at module.exports (/app/node_modules/ytsr/lib/parseItem.js:100:46)
at /app/node_modules/ytsr/lib/main.js:53:34
at Array.map (<anonymous>)
at module.exports (/app/node_modules/ytsr/lib/main.js:53:25)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async module.exports (/app/src/api/search.js:37:27)
/********************************************************************************************************************************************************************************************************
failed at func parseItem: type reelShelfRenderer is not known
pls post the the files in /app/node_modules/ytsr/dumps to https://github.com/TimeForANinja/node-ytsr/issues
os: linux-arm64, node.js: v12.22.12, ytpl: 3.5.0
********************************************************************************************************************************************************************************************************\
events.js:291
throw er; // Unhandled 'error' event
^
Error: connect ETIMEDOUT 104.237.169.22:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
Emitted 'error' event on PassThrough instance at:
at errorOrDestroy (internal/streams/destroy.js:108:12)
at PassThrough.onerror (_stream_readable.js:754:7)
at PassThrough.emit (events.js:314:20)
at PassThrough.emit (events.js:314:20)
at ClientRequest.onError (/app/node_modules/ytdl-core/node_modules/miniget/dist/index.js:148:24)
at ClientRequest.emit (events.js:314:20)
at TLSSocket.socketErrorListener (_http_client.js:427:9)
at TLSSocket.emit (events.js:314:20)
at emitErrorNT (internal/streams/destroy.js:92:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:60:3) {
errno: 'ETIMEDOUT',
code: 'ETIMEDOUT',
syscall: 'connect',
address: '104.237.169.22',
port: 443
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start:pro: `NODE_ENV=production node src/index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start:pro script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-04-14T15_50_13_680Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `npm run start:pro`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-04-14T15_50_13_707Z-debug.log
> [email protected] start /app
> npm run start:pro
> [email protected] start:pro /app
> NODE_ENV=production node src/index.js
Listening on port 3000 in production mode over HTTP
events.js:291
throw er; // Unhandled 'error' event
^
Error: connect ETIMEDOUT 104.237.171.25:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
Emitted 'error' event on PassThrough instance at:
at errorOrDestroy (internal/streams/destroy.js:108:12)
at PassThrough.onerror (_stream_readable.js:754:7)
at PassThrough.emit (events.js:314:20)
at PassThrough.emit (events.js:314:20)
at ClientRequest.onError (/app/node_modules/ytdl-core/node_modules/miniget/dist/index.js:148:24)
at ClientRequest.emit (events.js:314:20)
at TLSSocket.socketErrorListener (_http_client.js:427:9)
at TLSSocket.emit (events.js:314:20)
at emitErrorNT (internal/streams/destroy.js:92:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:60:3) {
errno: 'ETIMEDOUT',
code: 'ETIMEDOUT',
syscall: 'connect',
address: '104.237.171.25',
port: 443
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start:pro: `NODE_ENV=production node src/index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start:pro script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-04-14T16_44_15_487Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `npm run start:pro`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-04-14T16_44_15_505Z-debug.log
> [email protected] start /app
> npm run start:pro
> [email protected] start:pro /app
> NODE_ENV=production node src/index.js
Listening on port 3000 in production mode over HTTP
(node:29) UnhandledPromiseRejectionWarning: Error: socket hang up
at connResetException (internal/errors.js:609:14)
at TLSSocket.socketOnEnd (_http_client.js:458:23)
at TLSSocket.emit (events.js:326:22)
at endReadableNT (_stream_readable.js:1241:12)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
(node:29) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:29) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
> [email protected] start /app
> npm run start:pro
> [email protected] start:pro /app
> NODE_ENV=production node src/index.js
Listening on port 3000 in production mode over HTTP
> [email protected] start /app
> npm run start:pro
> [email protected] start:pro /app
> NODE_ENV=production node src/index.js
Listening on port 3000 in production mode over HTTP
(node:39) UnhandledPromiseRejectionWarning: Error: socket hang up
at connResetException (internal/errors.js:609:14)
at TLSSocket.socketOnEnd (_http_client.js:458:23)
at TLSSocket.emit (events.js:326:22)
at endReadableNT (_stream_readable.js:1241:12)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
(node:39) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:39) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:39) UnhandledPromiseRejectionWarning: Error: socket hang up
at connResetException (internal/errors.js:609:14)
at TLSSocket.socketOnEnd (_http_client.js:458:23)
at TLSSocket.emit (events.js:326:22)
at endReadableNT (_stream_readable.js:1241:12)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
(node:39) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.