Cloud
Data Center 4.12
Versions
- 9.5
- 9.4
- 9.3
- 9.2
- 9.1
- 9.0
- 8.19
- 8.18
- 8.17
- 8.16
- 8.15
- 8.14
- 8.13
- 8.12
- 8.11
- 8.10
- 8.9
- 8.8
- 8.7
- 8.6
- 8.5
- 8.4
- 8.3
- 8.2
- 8.1
- 8.0
- 7.21
- 7.20
- 7.18
- 7.19
- 7.17
- 7.16
- 7.15
- 7.14
- 7.13
- 7.12
- 7.11
- 7.10
- 7.9
- 7.8
- 7.7
- 7.6
- 7.5
- 7.4
- 7.3
- 7.2
- 7.1
- 7.0
- 6.10
- 6.9
- 6.8
- 6.7
- 6.6
- 6.5
- 6.4
- 6.3
- 6.2
- 6.1
- 6.0
- 5.16
- 5.15
- 5.14
- 5.13
- 5.12
- 5.11
- 5.10
- 5.9
- 5.8
- 5.7
- 5.6
- 5.5
- 5.4
- 5.3
- 5.2
- 5.1
- 5.0
- 4.14
- 4.13
- 4.12
- See all
Disabling HTTP(S) access to Git repositories in Bitbucket Server
Advanced actions
- Running the Bitbucket Server installer
- Automated setup for Bitbucket Server
- Starting and stopping Bitbucket Server
- Install Bitbucket Server from an archive file
- Install and configure a remote Elasticsearch instance
- Running Bitbucket Server as a Linux service
- Running Bitbucket Server as a Windows service
- Bitbucket Server config properties
- Proxying and securing Bitbucket Server
- Enabling SSH access to Git repositories in Bitbucket Server
- Using diff transcoding in Bitbucket Server
- Changing the port that Bitbucket Server listens on
- Moving Bitbucket Server to a different context path
- Running Bitbucket Server with a dedicated user
- Bitbucket Server debug logging
- Data recovery and backups
- Lockout recovery process
- Scaling Bitbucket Server
- High availability for Bitbucket Server
- Clustering with Bitbucket Data Center
- Enabling JMX counters for performance monitoring
- Getting started with Bitbucket Server and AWS
- Disabling HTTP(S) access to Git repositories in Bitbucket Server
- Smart Mirroring
- Git Large File Storage
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 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
- Securing Bitbucket Server behind nginx using SSL
- 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 Sep 16, 2015
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 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
- Securing Bitbucket Server behind nginx using SSL
- Bitbucket Server HTTPS request is redirecting back to HTTP URL during application links creation
Powered by Confluence and Scroll Viewport.