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

Bug 531478

Summary: cant push to git or connect with ssh maybe ip block
Product: Community Reporter: Christian Campo <christian.campo>
Component: GitAssignee: Eclipse Webmaster <webmaster>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: denis.roy, stefan.geiger
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard: stalebug

Description Christian Campo CLA 2018-02-21 11:05:12 EST
ip is 62.4.68.150

we get connection timeouts on git pull or push and also when I try to login to build.eclipse.org

I tried the same from one of our internet server to which I did ssh and it worked. So I assume our IP is blocked.

Can you please unblock it ? thanks
Comment 1 Eclipse Webmaster CLA 2018-02-21 11:25:50 EST
You should have been sent an email asking you to confirm this connection if it was a new IP.  I've replied to the message, so you should be unblocked.

-M.
Comment 2 Stefan Geiger CLA 2018-02-22 06:58:03 EST
It seems the IP is still blocked. I still cant push or pull. And i've got no email where I can confirm the connection.


Stefan
Comment 3 Christian Campo CLA 2018-02-22 09:55:44 EST
I did get an email when I tried the internet server and that worked. However working from my local environment with the IP 62.4.68.150 I did not get any email

So I assume no email is the spam folder since it worked with the other access. However we are still blocked. Can you please look into it.

thanks
Comment 4 Denis Roy CLA 2018-02-22 10:01:09 EST
I'm not seeing anything on our end that would prevent you from accessing SSH.
Comment 5 Stefan Geiger CLA 2018-02-22 10:09:53 EST
Hi, problem is fixed right now.

Thank you for your support!
Comment 6 Stefan Geiger CLA 2018-02-23 09:26:16 EST
Hi, IP seems blocked again. I dont know why it should be blocked again, but i cant pull or push (In Eclipse git: Connection timed out: connect)

On Jenkins:
Caused by: hudson.plugins.git.GitException:.... returned status code 128:
stdout: 
stderr: ssh: connect to host build.eclipse.org port 22: Bad file number
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Is there any way to find out what has caused the block? Furthermore is there a way to unblock our ip without making a ticket everytime?

Greetings 
Stefan
Comment 7 Eclipse Webmaster CLA 2018-02-23 11:53:18 EST
(In reply to Stefan Geiger from comment #6)
> Is there any way to find out what has caused the block?

In this case the issue is that Christian 'fat-fingered' his password(based on the log messages) enough times to get you blocked.

> Furthermore is there
> a way to unblock our ip without making a ticket everytime?

Not at this time no.  I've manually cleaned up the current record so you should be able to connect again.

-M.
Comment 8 Stefan Geiger CLA 2018-02-23 13:46:55 EST
Hi,

thank you for your response,patience and support. 
And I appologize for future incidents regarding the IP-Blocking hassle.

greetings Stefan
Comment 9 Christian Campo CLA 2018-02-26 09:56:38 EST
we are blocked again. we are still not sure what is going on and why we are getting blocked. I am pretty sure that it wasnt me this time.

Is it possible to whitelist our static IP address (see below) since it is static for our office.

thanks for unblocking
Comment 10 Eclipse Webmaster CLA 2018-02-26 14:42:54 EST
(In reply to Christian Campo from comment #9)

> I am pretty sure that it wasnt me this time.

Well all I can tell you is that someone at your IP, using your committer id failed to login enough times to get you blocked(again).
 
> Is it possible to whitelist our static IP address (see below) since it is
> static for our office.

Done.

-M.
Comment 11 Eclipse Genie CLA 2020-02-17 12:30:56 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 12 Eclipse Webmaster CLA 2020-02-25 13:40:28 EST
Closing after 2 years.

-M.