I've got Apache Cordova (latest version as of today) installed on a Windows7 machine and am attempting to create a new project. I'm inside a firewall, so have set proxies (npm config set proxy ..., npm config set https-proxy ... ) to access internet.
using the following command:
cordova create testApp1
I get the following error output:
Creating a new cordova project with name "HelloCordova" and id "io.cordova.hellocordova" at location "C:\Users\sr7\Documents\Cordova\testApp1"
Downloading cordova library for www...
Error: tunneling socket could not be established, cause=Parse Error
at ClientRequest.onError (C:\Users\sr7\AppData\Roaming\npm\node_modules\cordova\node_modules\cordova-lib\node_modules\request\node_modules\tunnel-agent\index.js:168:17)
at ClientRequest.g (events.js:199:16)
at ClientRequest.emit (events.js:107:17)
at Socket.socketOnData (_http_client.js:315:9)
at Socket.emit (events.js:107:17)
at readableAddChunk (_stream_readable.js:163:16)
at Socket.Readable.push (_stream_readable.js:126:10)
at TCP.onread (net.js:529:20)
This would appear to be a proxy issue, however if I do this at home (i.e. no proxy), it still fails although the error is different, i.e.
Creating a new cordova project with name "HelloCordova" and id "io.cordova.hellocordova" at location "C:\Users\sr7\Documents\Cordova\testApp1"
Downloading cordova library for www...
Error: tunneling socket could not be established, cause=getaddrinfo ENOTFOUND wwwcache.sanger.ac.uk
at ClientRequest.onError (C:\Users\sr7\AppData\Roaming\npm\node_modules\cordova\node_modules\cordova-lib\node_modules\request\node_modules\tunnel-agent\index.js:168:17)
at ClientRequest.g (events.js:199:16)
at ClientRequest.emit (events.js:107:17)
at Socket.socketErrorListener (_http_client.js:272:9)
at Socket.emit (events.js:107:17)
at net.js:923:16
at process._tickCallback (node.js:355:11)
It appears to still be trying to find the proxy "wwwcache.sanger.ac.uk", although I've removed the proxy info from npm (they both show null if I do "npm config ls -l").
Can anyone suggest a way to fix this, ideally within a firewall. Thanks.
Being behind a proxy, I've encountered the same issue with latest version of nodejs.
To fix it, download latest version of tunnel-agent here
and put it in the npm folder of your installed cordova-lib :
.\npm\node_modules\cordova\node_modules\cordova-lib\node_modules\npm\node_modules\request\node_modules\tunnel-agent
Source of information : https://issues.apache.org/jira/browse/CB-8662
Related
I want to install a private package hosted on an internal Gitlab with Yarn.
So, I configured my .npmrc with this informations :
#mypackage:registry=https://gitlab.intra/api/v4/packages/npm/
//gitlab.intra/api/v4/projects/819/packages/npm/:_authToken=xxxxx
//gitlab.intra/api/v4/packages/npm/:_authToken=xxxxx
always-auth=true
When I attempt to install the package with yarn add #mypackage/lib-node-client, Yarn give me an error :
Trace:
Error: https://gitlab.intra/api/v4/projects/725/packages/npm/#mypackage/lib-node-common/-/#mypackage/lib-node-common-21.7.1.tgz: Request failed "404 Not Found"
at ResponseError.ExtendableBuiltin (/usr/lib/node_modules/yarn/lib/cli.js:696:66)
at new ResponseError (/usr/lib/node_modules/yarn/lib/cli.js:802:124)
at Request.<anonymous> (/usr/lib/node_modules/yarn/lib/cli.js:67062:16)
at Request.emit (node:events:369:20)
at Request.module.exports.Request.onRequestResponse (/usr/lib/node_modules/yarn/lib/cli.js:141640:10)
at ClientRequest.emit (node:events:369:20)
at HTTPParser.parserOnIncomingClient (node:_http_client:646:27)
at HTTPParser.parserOnHeadersComplete (node:_http_common:129:17)
at HTTPParser.execute (<anonymous>)
at TLSSocket.socketOnData (node:_http_client:512:22)
So, Yarn can't find the URL : https://gitlab.intra/api/v4/projects/725/packages/npm/#mypackage/lib-node-common/-/#mypackage/lib-node-common-21.7.1.tgz
If I try to get this on my browser, I can download the package...
If anyone can help me please, thank's for all :)
In your .npmrc file, you tell how to connect to GitLab for the project 819. The error is about the project 725. GitLab simply refuse the connexion.
Try with
#mypackage:registry=https://gitlab.intra/api/v4/packages/npm/
//gitlab.intra/api/v4/projects/725/packages/npm/:_authToken=xxxxx
//gitlab.intra/api/v4/projects/819/packages/npm/:_authToken=xxxxx
//gitlab.intra/api/v4/packages/npm/:_authToken=xxxxx
always-auth=true
We had a gitlab private package registry, and was constantly getting this error.
npm i #placeholder/package-name works fine, but yarn add #placeholder/package-name was giving 404 errors.
I tried all possible solutions listed on this thread. At last, there was a section in gitlab on troubleshooting yarn installation [1].
It said,
try adding this to your .npmrc file (and replace <your_token> with your personal access token or deploy token):
//gitlab.example.com/api/v4/projects/:_authToken=<your_token>
Our previous .npmrc looked like this
save-exact=true
unsafe-perm=true
#placeholder:registry=https://gitlab.com/api/v4/packages/npm/
//gitlab.com/api/v4/packages/npm/:_authToken=${PLACEHOLDER_TOKEN}
With the above new line addition, it looked like this,
save-exact=true
unsafe-perm=true
#placeholder:registry=https://gitlab.com/api/v4/packages/npm/
//gitlab.com/api/v4/packages/npm/:_authToken=${PLACEHOLDER_TOKEN}
//gitlab.com/api/v4/projects/:_authToken=${PLACEHOLDER_TOKEN}
With that addition, yarn add #placeholder/package-name worked fine.
[1] https://docs.gitlab.com/ee/user/packages/npm_registry/#error-running-yarn-with-the-package-registry-for-npm-registry
This should be the accepted answer. //gitlab.com/api/v4/projects/:_authToken=${PLACEHOLDER_TOKEN} Was the piece I was missing, which supercedes needing to list each project id as in Joel's answer.
While trying to install puppeteer with: npm i puppeteer getting this error. My Node version is v12.16.3. I'm on a windows machine.
<!-- language: lang-none -->
ERROR: Failed to set up Chromium r756035! Set "PUPPETEER_SKIP_DOWNLOAD" env variable to skip download.
Error: Client network socket disconnected before secure TLS connection was established
at connResetException (internal/errors.js:608:14)
at TLSSocket.onConnectEnd (_tls_wrap.js:1514:19)
at Object.onceWrapper (events.js:416:28)
at TLSSocket.emit (events.js:322:22)
at endReadableNT (_stream_readable.js:1187:12)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
-- ASYNC --
at BrowserFetcher.<anonymous> (C:\Users\Red Viper\AppData\Roaming\npm\node_modules\puppeteer\lib\helper.js:116:19)
at fetchBinary (C:\Users\Red Viper\AppData\Roaming\npm\node_modules\puppeteer\install.js:148:8)
at download (C:\Users\Red Viper\AppData\Roaming\npm\node_modules\puppeteer\install.js:54:9) {
code: 'ECONNRESET',
path: null,
host: 'storage.googleapis.com',
port: 443,
localAddress: undefined
}
use --unsafe-perm
It works for me!
npm i puppeteer -g --unsafe-perm
Run following command from terminal:
Mac:
export PUPPETEER_SKIP_DOWNLOAD='true'
Windows:
SET PUPPETEER_SKIP_DOWNLOAD='true'
Both will set environment variable and you should be fine with execution
For me, the reason was that this address was banned in my country. I had to use a proxy to avoid this error.
Probably you're behind a proxy, may be you can contact your network/security admin in your organization.
This was the case for me, and the issue didn't appear in my home network.
I am running Apache Ignite 2.4.0 and configured Ignite web console using following steps Ignite webconsole build and deploy
same has been configured for production mode in Apache server and after successfully starting Backend, when i access web console from front end I am getting below signup error on Backend Node application console. I have tried multiple configurations but none of them seems to work.
Error: Not Found: /signup
at app.use (/recon/Ignite/web-console/backend/app/apiServer.js:64:33)
at Layer.handle [as handle_request] (/recon/Ignite/web-console/backend/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/recon/Ignite/web-console/backend/node_modules/express/lib/router/index.js:317:13)
at /recon/Ignite/web-console/backend/node_modules/express/lib/router/index.js:284:7
at Function.process_params (/recon/Ignite/web-console/backend/node_modules/express/lib/router/index.js:335:12)
at next (/recon/Ignite/web-console/backend/node_modules/express/lib/router/index.js:275:10)
at SessionStrategy.strategy.pass (/recon/Ignite/web-console/backend/node_modules/passport/lib/middleware/authenticate.js:325:9)
at SessionStrategy.authenticate (/recon/Ignite/web-console/backend/node_modules/passport/lib/strategies/session.js:71:10)
at attempt (/recon/Ignite/web-console/backend/node_modules/passport/lib/middleware/authenticate.js:348:16)
at authenticate (/recon/Ignite/web-console/backend/node_modules/passport/lib/middleware/authenticate.js:349:7)
at Layer.handle [as handle_request] (/recon/Ignite/web-console/backend/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/recon/Ignite/web-console/backend/node_modules/express/lib/router/index.js:317:13)
at /recon/Ignite/web-console/backend/node_modules/express/lib/router/index.js:284:7
at Function.process_params (/recon/Ignite/web-console/backend/node_modules/express/lib/router/index.js:335:12)
at next (/recon/Ignite/web-console/backend/node_modules/express/lib/router/index.js:275:10)
at initialize (/recon/Ignite/web-console/backend/node_modules/passport/lib/middleware/initialize.js:53:5)
at Layer.handle [as handle_request] (/recon/Ignite/web-console/backend/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/recon/Ignite/web-console/backend/node_modules/express/lib/router/index.js:317:13)
at /recon/Ignite/web-console/backend/node_modules/express/lib/router/index.js:284:7
at Function.process_params (/recon/Ignite/web-console/backend/node_modules/express/lib/router/index.js:335:12)
at next (/recon/Ignite/web-console/backend/node_modules/express/lib/router/index.js:275:10)
Snady, ignite-2.5.0 is on vote now and may be released in several days. I think it make sense to use this version.
Requirements: NodeJS 8.x & MongoDB 3.4.x. // Make sure you have this.
So, I downloaded sources and do the following:
In first terminal:
cd {apache-ignite-2.5.0}/modules/web-console/backend
npm install --no-optional
npm start
In second terminal:
cd {apache-ignite-2.5.0}/modules/web-console/frontend
npm install --no-optional
npm start
In browser do: http://localhost:9000/
EDIT:
Will Ignite Web Console in Docker works for your case?
See: https://hub.docker.com/r/apacheignite/web-console-standalone/
When trying to follow the instructions (https://fabric-composer.github.io/tasks/genapp.html) to generate an Angular app based on a running business network I'm getting a No bower.json present error, using the defaultProfile. It seems to generate a node_modules directory but it's empty, however no angular-app directory is created. I was able to get the app generated by pointing at an existing BNA file as outlined in step 2 of the document but wasn't ideal. Any idea of what mind be going on?
jdockter#ubuntu:~$ yo fabric-composer:angular
WARNING: No configurations found in configuration directory:/home/jdockter/config
WARNING: To disable this warning set SUPPRESS_NO_CONFIG_WARNING in the environment.
Welcome to the Angular2 skeleton app generator
? Do you want to connect to a running Business Network? Yes
? What is the name of the application you wish to generate?: angular-app
? Description of the application: Skeleton Fabric Composer Angular2 project
? Author name: Jon Dockter
? Author email: jdockter#us.ibm.com
? What is the Business Network Identifier?: labor-network-model
? What is the Connection Profile to use? defaultProfile
? Enrollment id: WebAppAdmin
? Enrollment Secret: DJY27pEnl16d
Configuring: angular-app
About to connect to a running business network
I'm all done. Running npm install && bower install for you to install the required dependencies. If this fails, try running the command yourself.
npm WARN enoent ENOENT: no such file or directory, open '/home/jdockter/package.json'
npm WARN jdockter No description
npm WARN jdockter No repository field.
npm WARN jdockter No README data
npm WARN jdockter No license field.
bower ENOENT No bower.json present
Complete
I created this defect to track this:
https://github.com/fabric-composer/fabric-composer/issues/206
Will update here as soon as we know more.
Thanks for the report.
I am using Windows 7X64 machine and trying to build Andriod application using cordova/ionic CLI v1.5.5. I am getting this error that I couldn't solve.
"You may not have the required environment or OS to build this project"
with commands ionic build android and cordova build android. The command ionic platform add android was successful. I am working with Android sdk (API 22) using the Android SDK Manager. I also made sure that PATH variable is correctly set.
Full transcript of process is:
C:\Users\ddevkota\Desktop\freshIonic>ionic build android
Running command: "C:\Program Files\nodejs\node.exe" C:\Users\ddevkota\Desktop\fr
eshIonic\hooks\after_prepare\010_add_platform_class.js C:\Users\ddevkota\Desktop
\freshIonic
add to body class: platform-android
Running command: cmd "/s /c "C:\Users\ddevkota\Desktop\freshIonic\platforms\andr
oid\cordova\build.bat""
ANDROID_HOME=C:\Users\ddevkota\AppData\Local\Android\sdk
JAVA_HOME=C:\Progra~1\Java\jdk1.7.0_15
Running: C:\Users\ddevkota\Desktop\freshIonic\platforms\android\gradlew cdvBuild
Debug -b C:\Users\ddevkota\Desktop\freshIonic\platforms\android\build.gradle -Do
rg.gradle.daemon=true
Downloading http://services.gradle.org/distributions/gradle-2.2.1-all.zip
Exception in thread "main" java.lang.RuntimeException: java.io.IOException: Serv
er returned HTTP response code: 403 for URL: http://services.gradle.org/distribu
tions/gradle-2.2.1-all.zip
at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAcc
essManager.java:78)
at org.gradle.wrapper.Install.createDist(Install.java:47)
at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:129)
at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:48)
Caused by: java.io.IOException: Server returned HTTP response code: 403 for URL:
http://services.gradle.org/distributions/gradle-2.2.1-all.zip
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon
nection.java:1625)
at org.gradle.wrapper.Download.downloadInternal(Download.java:59)
at org.gradle.wrapper.Download.download(Download.java:45)
at org.gradle.wrapper.Install$1.call(Install.java:60)
at org.gradle.wrapper.Install$1.call(Install.java:47)
at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAcc
essManager.java:65)
... 3 more
C:\Users\ddevkota\Desktop\freshIonic\platforms\android\cordova\node_modules\q\q.
js:126
throw e;
^
Error code 1 for command: cmd with args: /s /c "C:\Users\ddevkota\Desktop\freshI
onic\platforms\android\gradlew cdvBuildDebug -b C:\Users\ddevkota\Desktop\freshI
onic\platforms\android\build.gradle -Dorg.gradle.daemon=true"
ERROR building one of the platforms: Error: cmd: Command failed with exit code 1
You may not have the required environment or OS to build this project
Error: cmd: Command failed with exit code 1
at ChildProcess.whenDone (C:\Users\ddevkota\AppData\Roaming\npm\node_modules
\cordova\node_modules\cordova-lib\src\cordova\superspawn.js:134:23)
at ChildProcess.emit (events.js:110:17)
at maybeClose (child_process.js:1015:16)
at Process.ChildProcess._handle.onexit (child_process.js:1087:5)
Thanks for help in advance.
NOTE: This turns out to be a permission issue in client (403). I connected my machine to different network and it started working. All build process. If you wanna do it manually here is how far I got.
Solution for not Valid JAVA_HOME
After spending days and uninstalling all versions of java, reinstalling only one version and setting up Environment VariableJAVA_HOME as C:\Program Files\Java\jdk1.7.0_15 I solved the problem.
However there was another issue of ionic build android error when downloading gradle.
This was solved as I added gradle to my project offline.
Solution for not Gradle 403 Http response
Do the following:
After downloading gradle from issued link (here is https://services.gradle.org/distributions/gradle-2.2.1-all.zip) paste it in somewhere likes myApp\platforms\android\gradle\gradle-2.2.1-all.zip and in build.js from myApp\platforms\android\cordova\lib\build.js find this:
var distributionUrl = 'distributionUrl=https://services.gradle.org/distributions/gradle-2.2.1-all.zip';
And replace it with your own file's location:
var distributionUrl = 'distributionUrl=../gradle-2.2.1-all.zip';
Still working on build and will keep on posting the solution. A thread about other issues is created in ionic forum and it is here.
Solution for not Gradle 403 Http response
find distributionUrl variable in:
myapp\platforms\android\cordova\lib\builders\GradleBuilder.js
change http value to https in this line:
var distributionUrl = process.env['CORDOVA_ANDROID_GRADLE_DISTRIBUTION_URL'] || 'https://services.gradle.org/distributions/gradle-2.2.1-all.zip';