I'm getting error as rpc error: code = 14 desc = grpc: RPC failed fast due to transport failure while i try to register the user through rest client... please provide me the possible solution as soon as possible...i followed the below link to configure cop server please let me know the configuration is right or not.
https://github.com/hyperledger-archives/fabric-cop
and the attachment conatins directories involved in configuration:
directories involved in configuration
We renamed "fabric-cop" to "fabric-ca" so you are using an outdated version of the code. I'd suggest taking a look at https://github.com/hyperledger/fabric-ca as that's the latest code
Related
I'am using [Let's encrypt community for rancher][1] but since ACMEv1 is deprecated, it doesn't work anymore, i have this classic message
30/01/2020 16:29:04time="2020-01-30T15:29:04Z" level=fatal msg="LetsEncrypt client: Failed to register account: acme: Error 403 - urn:acme:error:unauthorized - Account creation on ACMEv1 is disabled. Please upgrade your ACME client to a version that supports ACMEv2 / RFC 8555. See https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430 for details."
I saw there's is updated image to address this issues : https://github.com/janeczku/rancher-letsencrypt/issues/110 and in particular :
https://hub.docker.com/r/vxcontrol/rancher-letsencrypt/ or better https://github.com/TrueCarry/rancher-letsencrypt/tree/acme-v2
But since i am new at Rancher, i can figure how to use this image instead the old one ?
Can someone help me to understand how it works ?
I am using Rancher 1.6.29
Thanks a lot
I feel so dumb ... i just did an upgrade of the container, giving the uadevops/rancher-letsencrypt image, and worked flawless
I am getting below error-
Got TLS error trying to find package cupertino_icons at https://pub.dartlang.org.
pub upgrade failed (69) -- attempting retry 2 in 2 seconds...
My understanding is I am on office network(VPN) thats why I am getting this error. I have tried multiple options and I have seen multiple multiple post but no post shows the exact way of doing things. So I will post my all questions here, if anyone help it will be really helpful for all persons who are going to start work on flutter
1) How to set and create a self-signed certificate?
Do we need to create a self signed certificate for pub.dartlang.org domain?
have tried to create a certificate by using this (https://www.akadia.com/services/ssh_test_certificate.html) use domain as pub.dartlang.org, is this a correct way or how to do it?
2)I have put DART_VM_OPTIONS=--root-certs-file=C:\Users\dev\certs\chrome.cer as my certificate but still issue not resolved.
3)If I have to set https_proxy? What are the values for hostname and port in VPN? How can i find these values?
Flutter app behind corporate firewall throws TLS error during packages get
4) To solve this issue I have seen the reference of this comment
https://github.com/dart-lang/pub/issues/1882#issuecomment-415588527
How to implement this?
I have tried multiple things, if anyone can help how to bypass this error that will help many persons, I think.
I have same error on MACbook when running Flutter Create. When I opened the web-browser to access pub.dartlang.org, there is an error message that says: Your Clock is set incorrectly.
Somehow my date was set to a week ago. Fixing the date resolve the TLS issue.
It can be a network error or some kind of permission issue. I was facing same issue. In my case it was due to network permissions in our organisation. I tried with some another network which has full access and my issue was resolved.
It might be problem with restricted network.
You can set proxy
systemProp.http.proxyPort=PortNumber
systemProp.https.proxyPort=PortNumber
systemProp.http.proxyUser=User
systemProp.https.proxyUser=User
systemProp.http.proxyPassword=Password
systemProp.https.proxyPassword=Password
systemProp.https.proxyHost=YourHost
systemProp.http.proxyHost=YourHost
systemProp.http.nonProxyHosts=YourNonHost
systemProp.https.nonProxyHosts=YourNonHost
It might be a problem with the restricted environment variables sequence. You can set bash_profile：
export FLUTTER_STORAGE_BASE_URL=https://storage.flutter-io.cn
export PUB_HOSTED_URL=https://pub.flutter-io.cn
keynote：
"FLUTTER_STORAGE_BASE_URL" is in front of "PUB_HOSTED_URL"
I was also getting the same error, after upgrading my flutter. I was connected to the internet but my clock was not on correct time. After I have corrected the time on my pc, the error was solved.
I updated our signalr packages from 2.4.0 and added RunAzureSignalR instead of RunSignalR. Added this code in de Startup.cs
app.Map("/signalr", map =>
{
var hubConfiguration = new HubConfiguration
{
EnableDetailedErrors = true
};
map.RunAzureSignalR(typeof(Startup).FullName, hubConfiguration, options =>
{
options.ConnectionString = AppApiSettings.SignalRServiceConnectionString;
});
});
But when I try to send a message to the hub I get an exception The connection is not active, data cannot be sent to the service.. Can't find any reason this would happen or why the service would not run.
When I use RunSignalR (self hosted) everything runs great.
Any help would be greatly appreciated.
It turns out Azure Service only support TLS1.2 for security concerns.
Please add following code to your Startup:
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
The hint for this solution was found on a github ticket: https://github.com/Azure/azure-signalr/issues/279
"No server available" indicates that your app server has trouble connecting to Azure service. You can enable tracing from the app server side with the following to see if any error throws.
GlobalHost.TraceManager.Switch.Level = SourceLevels.Information;
A sample here: https://github.com/Azure/azure-signalr/blob/dev/samples/AspNet.ChatSample/AspNet.ChatSample.SelfHostServer/Startup.cs#L19
If you are local debugging the server side, you can also uncheck "Just My Code" and break when any CLR exception throws:
System.Security.Authentication.AuthenticationException: "A call to SSPI failed, see inner exception."
- (inner) "The function requested is not supported"
System.ObjectDisposedException: 'Safe handle has been closed'
System.Net.WebException: 'The request was aborted: Could not create SSL/TLS secure channel.'
System.Net.WebSockets.WebSocketException: 'Unable to connect to the remote server'
- (inner) WebException: The request was aborted: Could not create SSL/TLS secure channel.
I recently had the same issue and again the accepted answer didn't help me. My project was a .NET 4.8 MVC application (so TLS version shouldn't be an issue) and following an update of the projects Nuget packages the issue arose.
I knew it was the Nuget updates that had broken my application but I didn't want to go through each one to figure out where the issue was.
Thanks to #cognophile for pointing me in the right direction. For me though I only needed to downgrade the following three Nuget packages to version 5.0.17 to fix the issue. Anything 6.x with these packages caused the issue again.
Microsoft.AspNetCore.Connections.Abstractions
Microsoft.AspNetCore.Http.Connections.Client
Microsoft.AspNetCore.Http.Connections.Common
I've recently had the same issue whereby the negotiation worked with map.RunSignalR(...) but not map.RunAzureSignalR(...) and tried the accepted answer here without resolution. For anyone still experiencing this issue having tried the accepted answer like myself, I found the below to work for a .NET Framework 4.6.1 project.
Navigating to the negotiation link (e.g. .../signalr/negotiate?clientProtocol=2.1&connectionData=...&callback=jQuery...&_=...) in the browser would give a
HTTP 500: Azure SignalR Service is not connected yet, please try again later
Having enabled the exception debugging suggestions from #Youp Hulsebos and the SignalR GitHub (source), I was able to find the following exceptions being thrown from the SignalR registration call in Startup.Configure(...):
Microsoft.Azure.SignalR.Common.ServiceConnectionNotActiveException: 'The connection is not active, data cannot be sent to the service.'
LoaderException - Method 'get_Features' in type 'Microsoft.AspNetCore.Http.Connections.Client.HttpConnection' from assembly 'Microsoft.AspNetCore.Http.Connections.Client, Version=1.0.0.0, Culture=neutral' does not have an implementation.":"Microsoft.AspNetCore.Http.Connections.Client.HttpConnection"
Having found the second of these exceptions and applying some Google-fu, I found this GitHub issue discussing the LoaderException from Microsoft.Azure.SignalR.WebSocketConnectionContext discussing this as the result of upgrading Microsoft.AspNetCore.Http.Connections.Client from 5.0.12.0 to 6.0.0.0.
Having tried downgrading the package to 5.0.12.0, I still encountered the same issue. Having checked the linked issue ([dotnet/aspnetcore#38699]), I downgraded the following packages to 5.0.11.0 and this resolved the issue:
Microsoft.AspNetCore.Connections.Abstractions
Microsoft.AspNetCore.Http.Connections.Client
Microsoft.AspNetCore.Http.Connections.Common
Microsoft.AspNetCore.Http.Features
I am generating dynamic links from the application using Branch IO. It generates link properly but sometime theres error generating link like
The request timed out.
CFNetwork handshake failed
Is this issue from branch side?
Found error in my network. Due to firewall issue, some of the packets were dropped.
Tried from other network i was able to get rid of the above issue.
We have a situation where our builds have stopped executing in a stable manner.
At a rate of about one every three we receive either TF215096 or TF215097 errors & the Build fails.
If we then restart the Build controller, it works again - until next time.
The errors we get are:
TF215096: An error occurred while connecting to controller vstfs:///Build/Controller/1: There was no endpoint listening at ht*p://XXXX that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
TF215096: An error occurred while connecting to controller XXX - Controller: Could not connect to ht*p://XXX. TCP error code 10061: No connection could be made because the target machine actively refused it 192.168.XXX.XXX:XXX.
TF215097: An error occurred while initializing a build for build definition \XXX: Team Foundation services are not available from server ht*p://XXX. Technical information (for administrator): The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.
TF215097: An error occurred while initializing a build for build definition \YYY: An error occurred while receiving the HTTP response to ht*p://XXX. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.
Server logs provide with little info, at least we 've found nothing that helps us resolve the situation. Various searches in the Net were also not productive.
Does anybody had these/similar issues? Any ideas on how/where to look for a resolution?
Thank you very much in advance for any input!
Yeah it does sound like you have some connectivity issues. You can try enabling SOAP tracing on both the build machine and the server (if possible) to see if there is any error. If it still does not give you any new information, contact Microsoft by filing a Connect Bug to get help.
I am not sure if it will help you but I have ran into similar issues with build agents and ended up just deleting and re-creating the agent. You may try deleting your controller/agent and adding it back in. A brute-force solution but a good starting point. If that doesn't resolve the issue at least you can eliminate the controller/agent as the issue and take a look at network/server related issues.
Today is a happy day, since we managed to get to the bottom of the matter. Sorry #Duat that I'm taking away the 'answer' checkmark - but it turned out that the problem was quite different from what you (and anybody else) has predicted.
In my last update I was about to forward the matter to MS, when we realized that our Firewall was misbehaving in the name resolution. So we assumed this was the culprit & awaited for this to resolve. After this was resolved, we STILL had the same issues and we went again re-examining the situation.
We isolated the problem within our Build Process, more specific with a custom code activity included in our build solution.
I had implemented a code activity that would kick in at the final steps of every build. This activity was about gathering BuildDetails about the running build & add them as a new line in a 'BuildLog.xls'. Implementation made use of Microsoft.Office.Interop.Excel.This excel sheet resides in another server (NOT on the Servers where the controller/agents reside).
During development of this activity I was faced with issues like this, but after I was done no instances of EXCEL were left hanging. So I thought this was done & dealt with.
With try & error, we observed that when this activity wouldn't ran, no problems would occur.
With this activity running, the very first build after a build-controller reset would succeed, any next build had a certain chance to fail. Once any build failed, no other would succeed until another build-controller reset.
I have only a general understanding of what the problem was (Excel-call is DCOM, TFS services are WCF : How on earth would they interfere?! Why would this sometimes succeed and sometimes fail?! ).
The provided diagnostics were no help either, in fact they mislead us into a loop that continued for months.
If I ever find the time, I 'd like to cleanly reproduce the error & make a Server Fault question out of it...
After removal of this activity it works! I now searched in SO & found this, where J.Saunders comments: "In general, you should never use Office Interop from a server environment". It's ironic that once you get to the bottom of any difficult issue, the whole universe seems to have known about it except you...