How to solve “sign_and_send_pubkey: signing failed: agent refused operation”?
Run ssh-add on the client machine, that will add the SSH key to the agent. Confirm with ssh-add -l (again on the client) that it was indeed added.
digital-ocean
Unable to access my website using the IP address of my Digital Ocean droplet
You are missing the Nginx. Port 80 is open but you are trying 5000, so won’t work. You can open port 5000 in the firewall and also check ufw firewall. ufw status and open the port using command sudo ufw allow 5000
Tomcat7 starts too late on Ubuntu 14.04 x64 [Digitalocean]
Replacing securerandom.source=file:/dev/urandom with securerandom.source=file:/dev/./urandom in $JAVA_PATH/jre/lib/security/java.security has solved my problem. Even when file:/dev/urandom is specified, JRE will still use /dev/random for SHA1PRNG (see bug JDK-4705093): In SHA1PRNG, there is a SeedGenerator which does various things depending on the configuration. If java.security.egd or securerandom.source point to “file:/dev/random” or “file:/dev/urandom”, we will use NativeSeedGenerator, which calls super() … Read more
How do I test a ClusterIssuer solver?
apiVersion: cert-manager.io/v1alpha2 kind: Certificate metadata: name: certificate-name spec: secretName: tls-cert duration: 24h renewBefore: 12h commonName: hostname dnsNames: – hostname issuerRef: name: letsencrypt kind: ClusterIssuer apiVersion: certmanager.k8s.io/v1alpha2 kind: ClusterIssuer metadata: name: letsencrypt spec: acme: email: [email protected] privateKeySecretRef: name: letsencrypt-private-key server: https://acme-v02.api.letsencrypt.org/directory solvers: – http01: ingress: class: nginx selector: {} apiVersion: extensions/v1beta1 kind: Ingress metadata: annotations: certmanager.k8s.io/acme-challenge-type: … Read more