Details
-
Bug
-
Resolution: Invalid
-
Medium
Description
We have Bitbucket installed on an internal server, and I was preparing to populate a repo we set up on that server.
From another server inside the network (where the files we want to track are), I run the commands listed on on the empty repo page. I run into issues when running "git push origin master"...output is: "fatal: unable to access 'http://myusername@bitbucketservername/pathtorepository.git': Failed to connect to bitbucketservername port 80: Timed out"
I am able to ping bitbucketservername, so I'm unsure where the hang up is.
I ran a test last week on a different repo with files on my local computer, and it worked perfectly, including a post-receive hook to automatically deploy files to the server that contains the files for the operation I tried to run today. This says to me it's some kind of network issue, but am wondering if this sort of thing has been seen before, and if there's something with the remote Bitbucket asks me to use that might be causing trouble.
Thanks!