I have VisualSVN installed on remote machine and I have implement the post commit hook so that I can get the every email on check-in by any developer in team. My hook is:
"%VISUALSVN_SERVER%\bin\VisualSVNServerHooks.exe" ^
commit-notification "%1" -r %2 ^
--from svn.admin --to <recepient mail> ^
--smtp-server <smtp server address>
Now after implementing it on remote machine(client domain), I am getting the below error on committing:
VisualSVNServerHooks: E020014: The server rejected one or more
recipient addresses. The server response was: 550 5.7.1 ... Relaying
denied. IP name lookup failed
Related
Essentially I cannot connect to an SSH server anymore. Whenever I try to connect I get the following error:
ssh: connect to host HOSTNAME port 22: Connection refused
Note that I am able to connect from a different machine. Hence, the issue seems to be client side. Furthermore, I also cannot pull/push to git repositories that are cloned via ssh. Again, when pulling I get the following error:
ssh: connect to host github.com port 22: Connection refused
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists
It seems like I somehow nuked my SSH installations/config files. I have reinstalled SSH but this did not fix the problem. Any ideas?
Note that you never "connect" to github.com directly (no interactive shell)
As mentioned here, "Connection refused" means
invalid IP address for github.com (manual entry in /etc/hosts or your resolver)
firewall along the way to github.com which blocks the ssh traffic (eg. local firewall or corporate firewall)
So is the other machine (where you do succeed) on the same network?
Check if the other machine SSH config file was not using ssh.gthub.com port 443 (instead of the default github.com:22, typically blocked in a corporate environment).
When Using git clone, I come into an error.
Here is the command and the error information.
[user#linux]$ git clone git#github.com:username/repertory.git
FATAL: failed to begin relaying via HTTP.
ssh_exchange_identification: Connection closed by remote host
fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.
Except for git#github, git clone https://...... and git clone git://...... works well. So i guess there is something wrong with ssh protocal, then i checked ssh.
[user#linux]$ ssh -T git#github.com
Hi username! You've successfully authenticated, but GitHub does not provide shell access.
It seems that I can connect to github through ssh protocol properly. But what's wrong with git clone through ssh?
This error message comes from connect.c from SSH
It is a SSH Proxy Command -- connect.c, the simple relaying command to make network connection via SOCKS and https proxy: You can make SSH session beyond the firewall with this command.
So check if such a connection is needed: it could very well be needed if you are in an enterprise, behind firewall, but in that case do contact your IT support team to check the validity/approval of such a solution.
And that error message indicates that even this SSH mode (relay through https proxy) might be blocked.
If you are not in an enterprise setting, and don't need proxy, do remove them (HTTPS(S)/PROXY) from your environment variables and your git config file.
If you're using a Proxy, many corporate firewalls block access to the CONNECT method on ports other than 443. GitHub operates an SSH server listening on port 443, using the host "ssh.github.com".
First, configure your SSH ~/.ssh/config with the following:
Host github.com, ssh.github.com
User git
Hostname ssh.github.com
Port 443
ProxyCommand socat - PROXY:localhost:%h:%p,proxyport=3128
in the example above I'm assuming you're running a web proxy on host localhost and port 3128 (e.g. cntlm).
You may also substitute socat with nc or connect-proxy with slightly different syntax.
Test with:
ssh -T git#ssh.github.com
Hi username! You've successfully authenticated, but GitHub does not provide shell access.
then with:
git clone git#ssh.github.com:username/repository.git
I have cloned the project https://github.com/kanaka/noVNC on my server(google compute engine). Now according to the readme file, i ran the script
bash launch.sh --vnc localhost:5900
this returned the
Navigate to this URL:
http://instance_name:6080/vnc.html?host=instance_name&port=6080
Now on my local system, I hit the URL
server_ip:6080/vnc.html
I entered the IP(googled my IP) of another system and port 5900. But it is showing server disconnected(code:1006). I didn't provided any password as I didn't gave any password to vnc server.
In console it is showing error
WebSocket connection to 'ws://192.168.1.236:5900/websockify' failed: Error during WebSocket handshake: Invalid status line
Am I missing something?
When i run p4 info in my perforce workspace then it shows me some perforce client information of my workspace. But i want to see, from where exactly it is picking up that information. I tried to google it but everywhere they are only telling about the command and it's output, i need to know the source of info for this command.
The following items are read from the client environment (see "p4 help environment" for more information, and run "p4 set" to see where exactly each one is coming from):
User name: sam_stafford
Client name: samwise-silver
Client host: FORGE
Current directory: c:\
The client root is stored in the server database ("p4 client -o"):
Client root: C:\public
The server address is determined by your P4PORT setting ("p4 set P4PORT"), normalized via reverse DNS lookup. The client address and client port refer to your machine and the port being used to make the connection to the server:
Server address: wayfarer-p4d:1666
Peer address: 10.23.2.15:54416
Client address: 10.23.2.15
License info comes from the server's license file:
Server license: Perforce Software, Inc. 5000 users (expires 2018/03/18)
Server license-ip: 10.199.2.50
Server root, case sensitivity, and server ID are configured globally for that server instance ("p4 configure show" will show you more about these):
Server root: /p4/1/root
ServerID: guru
Case Handling: sensitive
Server date and uptime come from the server's system clock:
Server date: 2015/04/23 00:03:21 -0700 PDT
Server uptime: 118:03:19
Server version comes from the P4D executable (same as "p4d -V" on the server):
Server version: P4D/LINUX26X86_64/2015.1/1028542 (2015/03/20)
I have set up an http server with the hgweb.cgi cgi script in a Linux server.
I put up a mercurial repository in the server. I can clone the repository from a windows machine without any problems. I can view the server in any browser. I can clone the repository from my localhost: (the server)
hg clone http:// localhost /hg/proj
works perfectly.
But when I tried to access the server on another Linux machine I got this error message:
hg clone http://myhgserver/hg/proj
abort: HTTP Error 404: Condition Intercepted
I could not find any error message in the error_log file on the apache2 web server.
First I suspected that I am using an older version of hg on my client side (1.4).
My server side is hg 2.6.3.
Then I tied to install the latest mercurial in my home directory (I have no permission the system directories)
I used the "make local" command to install the mercurial package locally.
./hg --version
Mercurial Distributed SCM (version 3.0+4-75aaae8ad660+20140613)
The clonning command gave the same error:
abort: HTTP Error 404: Condition Intercepted
I have spend almost the whole day, and now it is mid night, still could not find any answer.
Anyone else has seen such a problem?
Kemin
After a night of sleep, I got my problem resolved.
Basically, the hg program is missing the ability to resolve hostname into IP addresses.
Since my server and client computers are on the same LAN, there is no connection or firewall problems.
I can PING from my client to my server without any problems. I can run the host command:
host myhgserver it will give you the whole IP address and the fully qualified domain names. If I used the IP address instead of the host short name, then hg works fine.
What I think is needed is to add a few lines of code to hg client program so that it can find the server from an alias.