Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,459,444
Community Members
 
Community Events
176
Community Groups

[ISSUE]remote: Could not create socket to ping Stash: Connection refused

Not able to Push in to the Bitbucket

 

GD00519242@INBASDPC08424 MINGW64 ~/git/atlassian-project-repo (master)
$ git push
\Counting objects: 39, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (19/19), done.
Writing objects: 100% (39/39), 4.07 KiB | 0 bytes/s, done.
Total 39 (delta 3), reused 0 (delta 0)
remote: Could not create socket to ping Stash: Connection refused
To http://10.20.126.38:7990/scm/ap/atlassian-project-repo.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'http://GD00519242@10.20.126.38:7990/scm/ap/atlassian-project-repo.git'

 

pre-receive hook declined --> We dont have any hooks enabled in bitbucket.

 

Any pointers about this issues.

 

1 comment

I have been having the same issue and opened a ticket for it.  I did not get resolution from the ticket but in my case found at least a temporary solution.  I am running iptables on my server and have rules opening up the ports specified for the services listed.  When I stopped iptables, my pushes ran successfully.  When I ran netstat on the server I discovered it was listening on an additional port.  I added that port, 45453, to my allowed list in iptables and my pushes worked with iptables running.  I have not restarted bitbucket server yet to see if the additional port I added remains the same or if it will change with each restart.

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events