Truffle init failing - ethereum

I'm trying to run truffle in a linux virtual machine with a windows 10 host. When I run truffle init this is the error that I get...
DownloadingError: write EPROTO 140718189083520:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:s23_clnt.c:827:
at _errnoException (util.js:1022:11)
at WriteWrap.afterWrite (net.js:880:14)
I'm not really sure what's causing the error or how to solve it. Any advice would be appreciated. Thanks in advance!

This seems to be an issue with proxies.
I suggest you update your node environment to at least v10.16.0.
If that doesn't work try the answers to this other post.
npm gets stuck on fetchMetadata -> network

Related

Can you help me to fix the connection with my DBeaver?

I don't speak English, sorry.
I have this message to my DBeaver
Can you help me to fix the problem ?
Network error
Motif:
Network unavailable:
javax.net.ssl.SSLHandshakeException:PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
There are to ways to solve your problem.
1 - Check this link: ( https://dbeaver.com/docs/wiki/Importing-CA-Certificates-into-DBeaver/ ) and follow the steps.
2 - In DBeaver installation path, open the dbeaver.ini file and remove this line: -Djavax.net.ssl.trustStoreType=WINDOWS-ROOT
I did the same step, and did not work, but then I changed the SSL Factory to org.postgresql.ssl.LibPQFactory and it works.
I have similar error the first time that i open a DB:
Network error
Reason: Network unavailable due to certificate issue. Try changing the
setting Use Windows trust store in Preferences->Connections and
restart DBeaver. It might help if you haven't overridden trust store.
javax.net.ssl.SSLHandshakeException:PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to
find valid certification path to requested target
I try 'bAsK' solution but not work for me.
The solution for me is remove check in the setting Use Windows trust store in Preferences->Connections and restart DBeaver
I also installed JRE 8 (Java)
for mac OS , just edit the file
/Applications/DBeaver.app/Contents/Eclipse/dbeaver.ini
and add the below line to the file
-Djavax.net.ssl.trustStoreType=KeychainStore
Restart the DBeaver application to resolve this problem.

Failed to lift app: Error: Encountered error attempting to instantiate a session store using the installed version of `connect-mongo`

Trying to run my app through a localhost server but a few days ago this error message showed up out of nowhere. I'm using Sails.js with version ^1.3.2 for connect-mongo along with version ^1.2.0 for sails-mongo. My sessions.js file looks like the following -
secret: process.env.Mongodb_secret,
adapter: 'connect-mongo',
url: "mongodb://admin-user:fakepassword!#cluster0-shard-00-00.4c6tq.mongodb.net:27017,cluster0-shard-00-01.4c6tq.mongodb.net:27017,cluster0-shard-00-02.4c6tq.mongodb.net:27017/MyDB?ssl=true&replicaSet=atlas-11ei1d-shard-0&authSource=admin&retryWrites=true&w=majority",
Am I using an outdated version of connect-mongo? Has anyone run into a similar problem or know a discussion thread that has discussed something similar? Please let me know if additional information is needed. Thanks to anyone who helps out in advance.

How To Get EIP-198 in Solidity Working With Ganache-cli

I'm trying to use EIP 198 (https://github.com/ethereum/EIPs/blob/master/EIPS/eip-198.md) locally on ganache-cli, has anyone done that?
I keep getting an unknown opcode error.... I've ran ganache-cli with the ganache-cli -k byzantium argument already :\
The contract I'm specifically trying to deploy is: https://ropsten.etherscan.io/address/0x0feedd6091b9448b376ebb7f4d756b6f823439db#contracts
Turns out all I has to do was run it with ganache-cli -k=petersburg as I was running solidity>=0.5.0

Can not generate service, versioning conflict. What could I broke?

I use feathers for some months now and I already created and used several services. The app is generated with feather/cli command: 'feathers generate app'.
Today I tried to generate a new service with the usual command:
feathers generate service
only to get the error:
× This version of the generator will only work with Feathers Buzzard (v3) and up. Please runfeathers upgradefirst.
Fine. Run the upgrade. Got new error:
throw new Error('It looks like#feathersjs/feathersis already a dependency. I can not run the upgrade again.');
^
checked the version: is 3.9.0
Uninstalled/re-installed feathers/cli
Nothing works. Not sure what I broke as I did not (remember to) upgrade anything since a couple of days ago when I created the last service. Feathers was not updated in the last 4 months.
I tried googling my error but it seems like nobody else has this problem so it has to be something I've done.
Any suggestions?
LE: I have in package.json dependencies:
"#feathersjs/errors": "^3.3.6",
"#feathersjs/express": "^1.3.1",
"#feathersjs/feathers": "^3.3.1",
"#feathersjs/socketio": "^3.2.9",
"feathers-knex": "^5.0.7",
"feathers-memory": "^3.0.2",
"feathers-rest": "^1.8.1",
"feathers": "^2.2.4",```
This error will be shown if you still have the feathers module in your dependencies in your package.json. If #feathersjs/feathers is already included as well you can just remove the feathers dependency (after making sure it is not used anywhere else in your application which it shouldn't).

Is it possible to use virt-manager both for Openvz and KVM?

My code throws the error:
Could not connect to libvirt.
The end of the file was reached when reading the data: sh: nc: command not found: I / O error
Make sure that the remote The node is running libvirtd.
You should be able to do this with OpenVZ 7, I do not believe it is possible with any other version of OpenVZ.
If you continue having issues, providing additional information such as your OpenVZ kernel version and how you arrived at the error you previously posted, would be helpful.