Accessing private Git repository via new servers not possible

[patrickkaleta]

After changing the remote origin to our new private Git repository, I'm still unable to push/pull from the DEV server.

I've added a SSH key as described, but trying to push commits to the repo returns the following error now:

ssh: connect to host scm.atosresearch.eu port 22: Connection timed out
fatal: Could not read from remote repository.

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

Trying to check whether the SSH key was added successfully (as mentioned in the description) with ssh -T git@https://scm.atosresearch.eu/ also returns the "Connection timed out" error. @maesbri could you please check with your IT department, what might be the issue now?

[patrickkaleta]

I tested connecting to the repository with my own machine and our old CSIS-server (to rule out the DEV and PROD servers as the source of error), however the connection still fails due to a time out. @maesbri, @DanielRodera any news from you IT department on what could be the problem here?

[DanielRodera]

Hi @patrickkaleta,

I am afraid you cannot make the push by ssh,

Our company´s policy regarding the security doesn't allow external connections (using ssh)

Did you try making a push using https instead of ssh??

[patrickkaleta]

Did you try making a push using https instead of ssh??

Thank you @DanielRodera. ssh seems to be indeed forbidden. Push/pull is possible via https. I've changed the remote origins in both our servers, so that they now use https instead.