Why won't my deploy user use my ssh key? [closed] - ruby-on-rails

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I am trying to fix an ssh key error to work for a deploy user with my RoR Capistrano 3.3.5 project. I have an ubuntu 14.04 server which has my public ssh key authorized.
If I type ssh root#server-address.com my ssh key works, and I am immediately logged into my server.
If I type ssh deploy#server-address.com I am prompted for a password.
I need the deploy user to use the same key and authenticate without password. What is wrong? How do I go about making this happen?
I appreciate any help you can provide, thanks!

you need to add your public key to the deploy user's authorized_keys file which is located at /home/deploy/.ssh/authorized_keys on the server.

cat ~/.ssh/id_rsa.pub | ssh user#machine "mkdir ~/.ssh; cat >> ~/.ssh/authorized_keys"
this command would work for a new sever setup too.

Related

I can't access to Nifi Ui [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 11 months ago.
Improve this question
I have installed docker on Ubuntu-21.04 and I'm trying to run apache/nifi on it. I am using this command: docker run --name nifi -dp 8443:8443 apache/nifi. From the logs all seems fine:
Generated Username [24a06eea-579f-443a-ad81-b9fe95d46bd3]
Generated Password [9D3NKqhLElChcXHw0jzfO/wkT8yOV+uV]
2022-03-24 15:39:27,726 INFO [main] org.apache.nifi.web.server.JettyServer NiFi has started. The UI is available at the following URLs:
2022-03-24 15:39:27,726 INFO [main] org.apache.nifi.web.server.JettyServer https://a8917820086b:8443/nifi
The entire logs are here
But if i go at localhost:8443 I see this:
on firefox
and on chrome.
I don't know why I can't access to the UI of Nifi.
I have done all of this exactly on windows 10 and it works. Someone can help me? Thanks in advance.
You need to go to https://localhost:8443 not http://localhost:8443. By default NiFi is now secured with TLS, but 8443 is not the standard HTTPS port, thus it does not automatically redirect you to HTTPS if you only enter localhost

How to get metrics of kong cluster behind load balancer [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
Currently, I'm using Kong API CE on my project, and use Prometheus plugin to get metrics.
But on production environment and autoscale, behind the load balancer, how can I get metrics for all kong instance from Prometheus server?
Should I use consul in this case? Please help.
Using Prometheus plugin
Install Prometheus
Install Grafana
Enable Prometheus Plugin in Kong
Access Prometheus in your browser say at localhost:9090
Access Grafana in your browser say at localhost:3000
Set Up Port Forwards:
If Kong proxy port is now your localhost 8000 port, Eg: If you are using plain-text HTTP proxy for this purpose
Create Some Traffic for the services and routes registered
Now Access Grafana Dashboard, you should be able to see metrics related to the traffic flowing through our services.

Localhost 3000 not working [closed]

Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 2 years ago.
Improve this question
Hi I'm learning ruby on rails but all of a sudden localhost/3000 is not working, it was working fine moments ago. I'm using windows 8 and my ruby version is 2.2.4 and rails version is 4.2.6
Rails server is running but localhost/300 is not loading in browser. Help please.
rails server
browser
You're using /3000 instead of :3000. You need http://localhost:3000 which connects to localhost using port 3000.
It does actually indicate the correct URL in your console output.
You have to run the server on a port and it is 3000 so the address should be http://localhost:3000 instead of http://localhost/3000.
Ports are followed by : in the url

How do I get the docker client to trust a self signed cert on the token auth server [closed]

Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 3 years ago.
Improve this question
I'm attempting to get a docker registry v2 set up including token auth using self signed certificates.
I can get my docker client to trust the docker registry (by adding the ca.crt into /etc/docker/certs.d/registry.example.com/ in boot2docker)
I'm not sure how to tell the docker registry v2 to trust the auth server, though. I get the following error:
FATA[0003] Error pushing to registry: Get
https://docker-auth.example.com/auth?
scope=repository%3Atest%3Apull%2Cpush&service=registry.example.com:
x509: certificate signed by unknown authority
I'm using the docker auth server here: https://github.com/brandnetworks/docker_auth

RabbitMQ client can't connect to remote RabbitMQ server [closed]

Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 8 years ago.
Improve this question
I have a nodejs client that uses bramqp for connecting to RabbitMQ server. My client can connect to a Rabbit MQ server in localhost and works well. But it's unable to connect to a remote RabbitMQ server on other machine. I opened port 5672 in the remote server, so I think that the problem is in the configuration of rabbitMQ server. How can I solve this problem?
The problem seems the new rabbitmq access control policy
Please read this post:
Can't access RabbitMQ web management interface after fresh install
I think it can help you!

Resources