Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Remote button over HTTP in Sourcetree



I have a repository which is shared over HTTP protocol.

After updating to Sourcetree v3.4.13 when I click on "Remote" button to open online repository the link generated in the browser in missing a ":" after "http", therefore generating a link over HTTPS to a non-existing page.

For example, when I click on "Remote" button I get linked to:


It should be instead:


I am using sourcetree for windows and I have not encountered this issue on previous release, as on 3.4.12 it was working fine.

Am I the only facing this issue? Is it gonna be fixed?

Thanks in advance,




2 answers

1 accepted

0 votes
Answer accepted
Mukesh Kumar
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 02, 2023

Hi @Claudio Preti

@Jerome Pönisch 

Thanks for reporting this issue.

We have found that this issue is occurring for some specific URLs only.

We will provide a fix in upcoming release soon.

Awesome! Thanks for the fast reactions!

I want to extend on this - this seems to be broken in general.


I have repos on HTTPS but if my repository path is configured like e.g.


The "Remote" button in a browser instead tries to go to


worked before but since update to 3.4.13 it's broken

(works again after rolling back to 3.4.12 )

I was so free to create a Bug for this

Update: The ticket is already in progress :)

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events