Issues

Issue #2593 resolved

Getting ssl required - when pushing to wiki (BB-1488)

hindlemail
created an issue

{{{ $ hg push pushing to https://geckofx@bitbucket.org/geckofx/geckofx/wiki searching for changes http authorization required realm: Bitbucket.org HTTP user: geckofx password: remote: ssl required }}}

Comments (19)

  1. Mark Bucciarelli
    • changed status to open

    Hi, I have the same issue.

    pushing to https://mbucc@bitbucket.org/mbucc/salesforce_activities_to_batchbook/wiki
    searching for changes
    http authorization required
    realm: Bitbucket.org HTTP
    user: mbucc
    password: 
    remote: ssl required
    $ 
    
  2. Ian Glover

    Am seeing the same issue

    pushing to https://iang@bitbucket.org/iang/wmfuzzy/wiki
    searching for changes
    http authorization required
    realm: Bitbucket.org HTTP
    user: iang
    password: 
    remote: ssl required
    
  3. Ashish Mondal

    I am getting the same error:

    pushing to https://nulldev@bitbucket.org/nulldev/windows-phone
    http authorization required
    realm: Bitbucket.org HTTP
    user: nulldev
    password: 
    searching for changes
    remote: ssl required
    
  4. Kirk Woll

    I have this problem as well. I just signed up for bitbucket. Is not being able to use your repository a regular feature of bitbucket? If so, I will be looking elsewhere.

  5. Marcus Bertrand staff

    Please open a support request directly to support@bitbucket.org instead of commenting here and we will take care of you immediately. Please include your affected repository names in the request.

  6. Rob Vesse

    I just encountered this bug myself, the interesting thing is that I only see it on some repositories. As requested I have sent a support request via email to resolve the problem repository but I am commenting here because I'm wondering if the difference in how those repositories were created is the cause of the problem.

    • If I fork an existing repo and clone it to my local machine I have no problem
    • If I create a new empty repository and then push into it from an existing clone of another repository on my local machine I have no problem
    • If I create a new repository by importing a remote repository (from SourceForge in my case) then I have a problem

    This leads me to suggest that maybe the import repository code does not configure a repository in quite the same way on your servers as just creating a new repository does

  7. Log in to comment