Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Connection refused when sshd doesn't listen on default port #569
our ssh server doesn't listen on the default port 22, which results in the following error:
It works when I change the config of the sshd so that it runs on port 22 .
The :gitolite_server_port variable is set to the port on which the sshd listens.
This doesn't change anything:
The documentation of the clone function form the "/lib/gitolite/gitolite_admin.rb:211" file:
So, there must be a port definition in the provided url.
I've had problems with changing settings via the webpage.
You can edit
Then manually update using the following CLI commands:
Then restart the server and it should be set, just don't use the gui to change any settings as it breaks the config.
Hi! Actually you could create this file :
@alchris can you ssh to the box when it's on the different port?
What Git server are you running? Have you change the port number within that config file?
Then changed the
I always reboot after every setting change, a) to test b) to make sure all files have been loaded with the new config.
Hello jblobb, here what I did:
--> restart apache
--> restart apache
I don't have
127.0.0.1 should be the IP address of the box / VM.
They should be the IP of the Redmine box as well, then I would restart the box, to confirm that the changes have been applied to everything. Then run the Rake commands.
referenced this issue
Feb 14, 2016
@alchris I restart the server. BUT you can just restart redmine, which will still work.
When you pasted the config
Have you tired
As far as I can see gogs, doesn't integrate to Redmine.
Can you post a copy of
@alchris Yes, I understand that they are on the same host.
It's not suppose to be 127.0.0.1. When you ssh to that box you don't use 127.0.0.1 it's the IP address.
I was having issues with this plugin on the standard port 22. I think that you have changed all the other values, you just need to change that IP.
I'm 95% sure it will work just by changing that IP, in the the cli, then updating the hooks.
I've had 2 other people follow this guide I've made and it works.
Yes, that's because you're on the localhost, which means your forcing it to bind it to the localhost. So you get an
I don't know what to tell you. I didn't write this plugin, I've just found the work around. I know setting 127.0.0.1 in the settings.yml won't allow you to connect, but using the IP address will.