Upgrading Rancher's Let's encrypt for ACMEv2 support - docker

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

Related

Klaviyo is unable to connect to Magento Server for OAuth Handshake

Quoting this answer: https://community.klaviyo.com/integrations-39/magento-2-4-1-integration-issue-2147?postid=7443#post7443
I have a question to "how to solve that?"
Because I am also facing a similar issue while integrating.
==ERROR MESSAGE==
We ran into an error
There was an error while integrating your Klaviyo account with Magento 2. Below are the details about your error
Klaviyo is unable to connect to Magento Server for OAuth Handshake.
Url tried was: None
Please ensure that both /oauth/token/request and /oauth/token/access
are accessible
So if you can help me, it will be very much useful.
Getting same above issue on Magento 2.4.2 with Klaviyo Integration.
Solution:
/vendor/magento/module-integration/Controller/Adminhtml/Integration/TokensExchange.php
use Magento\Framework\App\Action\HttpGetActionInterface;
class TokensExchange extends Integration implements
HttpPostActionInterface,HttpGetActionInterface
Added additional interface HttpGetActionInterface
Please override this file to local
https://github.com/magento/magento2/commit/68d20230ca9d6198fa3093eb174e24aff47b1646#comments
Actually there was no issues in the code or the module.
The problem was, I was using magento in localhost, so klaviyo was not able to connect it.
I moved to a public IP and removed the sub folder format in url, i.e., localhost/magento2 was my url. Changed it to work with localhost/
So now klaviyo is working.

Got TLS error trying to find package cupertino_icons at https://pub.dartlang.org

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.

Azure SignalR Service Connection is not active

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

Error creating Queues in RabbitMQ

I have an environment in our company which hosts RabbitMQ 3.6.1 and Erlang 19.3. When i tried to create a queue by using RabbitMQ Management UI, I am getting the below error. I can create Exchanges and VHosts ok. It is only when I am trying to create Queues that I am getting the error. I tried to write a utility to create queues using the HTTP api but even that fails.
Upon some more researching I stumbled upon this article https://groups.google.com/d/msg/rabbitmq-users/pa1UtLbbvOE/3OlgKgMBAgAJ which says Erlang 19 is not compatible with RabbitMQ 3.6.3 and lower. Can someone confirm my findings please?
The error I am getting is
Got response code 500 with body {"error":"Internal Server Error","reason":"{error,\n {exit,\n {{function_clause,\n [{rabbit_queue_location_validator,module,\n [\"random\"],\n [{file,\"src/rabbit_queue_location_validator.erl\"},\n {line,50}]},\n {rabbit_queue_location_validator,validate_strategy,1,\n [{file,\"src/rabbit_queue_location_validator.erl\"},\n {line,38}]},\n {rabbit_queue_master_location_misc,get_location_mod_by_config,\n 1,\n [{file,\"src/rabbit_queue_master_location_misc.erl\"},\n {line,88}]},\n {rabbit_queue_master_location_misc,get_location,1,\n [{file,\"src/rabbit_queue_master_location_misc.erl\"},\n {line,51}]},\n {rabbit_amqqueue,declare,6,\n [{file,\"src/rabbit_amqqueue.erl\"},{line,300}]},\n {rabbit_channel,handle_method,3,\n [{file,\"src/rabbit_channel.erl\"},{line,1331}]},\n {rabbit_channel,handle_cast,2,\n [{file,\"src/rabbit_channel.erl\"},{line,455}]},\n {gen_server2,handle_msg,2,\n [{file,\"src/gen_server2.erl\"},{line,1049}]}]},\n {gen_server,call,\n [<0.27627.105>,\n {call,\n {'queue.declare',0,<<\"Test\">>,false,true,false,false,false,\n []},\n none,<0.15368.105>},\n infinity]}},\n [{gen_server,call,3,[{file,\"gen_server.erl\"},{line,212}]},\n {rabbit_mgmt_util,'-amqp_request/5-fun-0-',4,\n [{file,\"src/rabbit_mgmt_util.erl\"},{line,579}]},\n {rabbit_mgmt_util,with_channel,5,\n [{file,\"src/rabbit_mgmt_util.erl\"},{line,598}]},\n {rabbit_mgmt_util,http_to_amqp,5,\n [{file,\"src/rabbit_mgmt_util.erl\"},{line,526}]},\n {webmachine_resource,resource_call,3,\n [{file,\"src/webmachine_resource.erl\"},{line,186}]},\n {webmachine_resource,do,3,\n [{file,\"src/webmachine_resource.erl\"},{line,142}]},\n {webmachine_decision_core,resource_call,1,\n [{file,\"src/webmachine_decision_core.erl\"},{line,48}]},\n {webmachine_decision_core,accept_helper,1,\n [{file,\"src/webmachine_decision_core.erl\"},{line,612}]}]}}\n"}
The RabbitMQ team monitors this mailing list and only sometimes answers questions on stackoverflow.
In your case, the error is happening here. Did you create a queue-master-locator policy with the value of random? If so, I recommend clearing the policy to see if that resolves the issue.
I also recommend upgrading to the latest version (3.6.12). The version you are using is very old.
Thanks to #Luke Bakken for pointing me to the RabbitMQ Mailing list.
I managed to fix the problem by changing the configuration of queue master location strategy to <<"random">>
Please see this link for more info
https://groups.google.com/d/msg/rabbitmq-users/XUbtu4UxbHQ/3y-PvO0oBAAJ

facing issues while enrolling the user certificate in fabric cop server

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

Resources