Disabling HTTP(S) access to Git repositories in Bitbucket Server
Administering Bitbucket Server
- Users and groups
- External user directories
- Global permissions
- Setting up your mail server
- Integrating Bitbucket Server with Atlassian applications
- Connecting Bitbucket Server to an external database
- Migrating Bitbucket Server to another server
- Getting started with Bitbucket Server and AWS
- Specifying the base URL for Bitbucket Server
- Configuring the application navigator
- Managing add-ons
- Audit logging in Bitbucket Server
- Updating your Bitbucket Server license details
- Bitbucket Server config properties
- Moving Bitbucket Server to a different context path
- Data recovery and backups
- Disabling HTTP(S) access to Git repositories in Bitbucket Server
- Smart Mirroring
- Data Center Migration
- Git Large File Storage
- Git Virtual File System (GVFS)
- Enabling SSH access to Git repositories in Bitbucket Server
- Using diff transcoding in Bitbucket Server
- Changing the port that Bitbucket Server listens on
- Lockout recovery process
- Proxying and securing Bitbucket Server
- High availability for Bitbucket Server
- Diagnostics for third-party apps
- Enabling JMX counters for performance monitoring
- Bitbucket Server debug logging
- Scaling Bitbucket Server
- Add shortcut links to a Bitbucket Server repository
- Administer code search
On this page
Related content
- Enabling SSH access to Git repositories in Bitbucket Server
- Can't access Bitbucket Server with Git - Issuer certificate is invalid
- Securing Bitbucket Server behind nginx using SSL
- Securing Bitbucket Server with Apache using SSL
- Bitbucket Server webhook is not providing git URL is response payload.
- Proxying and securing Bitbucket Server
- Bitbucket Server: Git operations fails with error fatal: unable to access.. Encountered end of file
- How to serve your Bitbucket Server repo without using Bitbucket Server
- Bitbucket does not support Git's legacy HTTP transport protocol when using Git LFS
- Bitbucket Server HTTPS request is redirecting back to HTTP URL during application links creation
A Bitbucket Server administrator can disable HTTP(S) access to Git repositories in Bitbucket Server. This removes the ability to push to or clone Git repositories in Bitbucket Server over HTTP(S).
Disabling HTTP(S) access
To disable HTTP(S) access:
- Go to the Bitbucket Server administration area and click Server settings (under 'Settings').
- Under 'HTTP(S) access', uncheck HTTP(S) enabled.
- Click Save.
Last modified on Nov 15, 2018
Related content
- Enabling SSH access to Git repositories in Bitbucket Server
- Can't access Bitbucket Server with Git - Issuer certificate is invalid
- Securing Bitbucket Server behind nginx using SSL
- Securing Bitbucket Server with Apache using SSL
- Bitbucket Server webhook is not providing git URL is response payload.
- Proxying and securing Bitbucket Server
- Bitbucket Server: Git operations fails with error fatal: unable to access.. Encountered end of file
- How to serve your Bitbucket Server repo without using Bitbucket Server
- Bitbucket does not support Git's legacy HTTP transport protocol when using Git LFS
- Bitbucket Server HTTPS request is redirecting back to HTTP URL during application links creation
Powered by Confluence and Scroll Viewport.