Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 400884

Summary:	Internal network has lost ability to SSH
Product:	Community	Reporter:	David Williams <david_williams>
Component:	Servers	Assignee:	Eclipse Webmaster <webmaster>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	blocker
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description David Williams

2013-02-15 02:40:59 EST

We first saw this in Orbit builds, where use my committer ID to check out from CVS via SSH. 

But, I tried several experiments, with several IDs, and always got the response 

$ ssh build.eclipse.org
ssh: connect to host build.eclipse.org port 22: Connection timed out

Comment 1 David Williams

2013-02-15 02:45:13 EST

(In reply to comment #0)
> We first saw this in Orbit builds, where use my committer ID to check out
> from CVS via SSH. 
> 
> But, I tried several experiments, with several IDs, and always got the
> response 
> 
> $ ssh build.eclipse.org
> ssh: connect to host build.eclipse.org port 22: Connection timed out

I meant to emphasize, it works fine from outside "eclipse.org" ... just not from internal network.

Comment 2 David Williams

2013-02-15 16:58:06 EST

This now works for us in Orbit. (And, my "manual" SSH session tests). 

I'll leave open in case you are still working on it, just wanted to let you know.

Comment 3 David Williams

2013-02-16 08:39:53 EST

And ... now it doesn't. Started "breaking" again, this morning.

Comment 4 Eclipse Webmaster

2013-02-21 15:53:37 EST

I suspect this is an artefact of 400612.  We've temporarily white-listed while the Orion team works on a solution.

-M.