When trying to run any transaction using Web3j on Ganache it fails with the exception: TxHashMismatchException.
It seems that something has changed on Ganache that is breaking the interoperability.
The issue here is that Ganache has changed the way the transactions hashes are created since version 6.2.0. This problem doesn't exist on version v6.1.8 and earlier, using v6.1.8 should fix your issue.
If you are running Ganache using Docker make sure that you specify the version and not latest.
Related
Since update to version 69.0.3497.81, kerberos authentication on our application doesn't work anymore. I don't master the authentification process but it seems that chrome use NTLM instead of Kerberos for authentication.
Access url to our application use an alias. Example:
https://myApplication/test
The application is deployed on a server: serverA.domain.com
I think the keytab referenced serverA.domain.com.
I noticed that if I use full server name with domain, it works! -> https://serverA.domain.com/test
We confirm that with previous chrome version, it works.
Have you guys met problems like that with last chrome update ? Any suggestion ?
It was a bug on google chrome. Since version 69.0.3497.23, chrome didn't resolve Cnames anymore. So if you use an alias in your DNS, it's not resolved and use directly for negocation kerberos.
chrome than got an error "ERR_ACCESS_DENIED".
With an incorrect SPN, the ticket acquisition will fail. Windows defaults to NTLM in those cases.
More Explanation from bug chat:
"Async host resolver currently doesn't resolve CNAMEs. Thus use of the
async resolver is not currently compatible with the needs of
HttpAuthHandlerNegotiate where correct CNAME lookup is required."
Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=872665
Hope this help others!
Yes, we have problems like that, it seems to be a bug in the latest version of Chrome, please see https://bugs.chromium.org/p/chromium/issues/detail?id=872665
When I run the file "ganache-1.0.1-x86_64.AppImage" that I downloaded from GitHub, Ganache just hangs showing the following screen with no more actions.
Is something missed?
I tried Ganache version 1.0.0 and and version 1.0.1.
My system contains:
Ubuntu 17.10 64bit
node v6.11.4
npm 3.5.2
Truffle v4.0.1 (core: 4.0.1)
Solidity v0.4.18 (solc-js)
Thanks,
After investigation, I found that there was an application that uses the same default port of Ganache 7545.
Ganache should show error message clarifying that there is another application that uses the default running port. And better to suggest another port to start running with OR open Ganache settings page and notify to change the running port
I opened an issue at GitHub regarding this:
https://github.com/trufflesuite/ganache/issues/126
However, the solution is to close or change the port of the other application that uses the port 7545. Then you can run Ganache. After that, from Ganache settings, you can change the port that Ganache uses for any other free port you want.
Note: if Ganache crash for any reason and you hit the close button, it could be that it is still running in the background and still listening on (use) the port that it was running on. Therefore, you may need to kill (end) its process that is still running in the background.
I have a problem setting up the environment in my Spring tool Suite. It's as simple as not being able to start the server successfully. Because whenever I start it, it returns this error:
Error: Could not find or load main class
Workspace.sts-bundle.pivotal-tc-server-developer-3.1.1.RELEASE.base-instance.conf.logging.properties
I am using the 3.7.0 release of STS. What could be the possible reason for this? Any suggestions?
This is the same as here: Pivotal tc Server v.3.1 won't start
Make sure there are no spaces in your path to STS and let us know if that resolves your issue.
Thanks.
I have a strange behaviour in my Windows phone 8 application based on Worklight.
it works locally but when I deploy it in the production environment sometimes it works and sometimes not. Obviously, the behaviour I have is that the app init success in the first launch, it doesn't work in the seconde launch, it works in the third launch, doesn't work in the forth launch ... one by one.
the difference between the development environment and the production environment is that the first one is running over HTTP and the seconde one is running ever HTTPS.
Notice that it works in the other environments (Android, iOS, BlackBerry)
Any help?
I figured out how to fix the problem.
So to explain, here, what I did:
Before calling WL.client.init, I added a procedure call first (It's like a fake call) and then I initialized the WL Client.
Obviously, It fixed my problem. I think calling a procedure does initialize the connection between the client and the server.
So when the client call WL.Client.init or WL.Client.connect, succeeds to reach the server cause the connection is already initialized.
I have C++ Win32 app that uses HttpSendRequest to request some URL (via https). It worked OK earlier; but then errors ERROR_INTERNET_INCORRECT_HANDLE_STATE began happen. Why these ones? Any ideas?
I stumbled across something very similar recently. It suggests that your HttpOpenRequest has either failed or not yet completed, or during the HttpSendRequest() call the connection died for some reason (SSL handshake problems, Certificate problems, or just simple TCP connection problems).
I specifically saw the problem when developing an app using the asynchronous WinINET process, and my calls to HttpQueryInfo and InternetReadFile were failing with that return code.
In my case, I wasn't correctly waiting for the async notifications from HttpSendRequest to be received before calling the other methods, and also in cases where I wasn't correctly dealing with failures during the connection.
I know its a year late, but hopefully that helps.
It seems trivial but,
did you have flag INTERNET_FLAG_SECURE in making HttpOpenRequest?
as described in:
http://support.microsoft.com/kb/168151
For I myself was stuck here for hours until I found above knowledge base entry.
I got the same error on Windows XP for HTTPS connection (all flags correct) for the HTTP2 server endpoint, I wonder if it can't properly handle HTTP2 connection or the certificate.