Disable HTTP(S) access to Git repositories
Administer Bitbucket Data Center and Server
- Users and groups
- Advanced repository management
- External user directories
- Global permissions
- Setting up your mail server
- Integrate with Atlassian applications
- Connect Bitbucket to an external database
- Migrating Bitbucket Server to another server
- Run Bitbucket in AWS
- Specify the Bitbucket base URL
- Configuring the application navigator
- Managing apps
- View and configure the audit log
- Update your license key
- Configuration properties
- Change Bitbucket's context path
- Data recovery and backups
- Disable HTTP(S) access to Git repositories
- Smart Mirroring
- Export and import projects and repositories
- Git Large File Storage
- Git Virtual File System (GVFS)
- Enable SSH access to Git repositories
- Use diff transcoding
- Change the port Bitbucket listens on
- Lockout recovery process
- Proxy and secure Bitbucket
- High availability for Bitbucket
- Diagnostics for third-party apps
- Enabling JMX counters for performance monitoring
- Enable debug logging
- Scaling Bitbucket Server
- Add a shortcut link to a repository
- Administer code search
- Adding additional storage for your repository data
- Add a system-wide announcement banner
- Configuring Project links across Applications
- Improving instance stability with rate limiting
- Use a CDN with Atlassian Data Center applications
- Managing personal access tokens
- Connecting to a 3rd party application using Application Links
- Setting a system-wide default branch name
- Automatically decline inactive pull requests
- Encrypt database password
- Data pipeline
On this page
Related content
- Bitbucket Server webhook is not providing git URL is response payload.
- Can't access Bitbucket Server with Git - Issuer certificate is invalid
- Git command returns "not found" or error code 404
- Bitbucket Server: Git operations fails with error fatal: unable to access.. Encountered end of file
- Permanently authenticating with Git repositories
- Unable to push changes to the repository in Bitbucket Server with insufficient permission error over HTTPS URL
- Can't clone or pull due to a git outbound proxy
- Unable to push changes to the repository in Bitbucket with insufficient permission error over HTTPS URL
- How to serve your Bitbucket Server repo without using Bitbucket Server
- Specify the Bitbucket base URL
Administrators can disable HTTP(S) access to Git repositories in Bitbucket Data Center and Server. This removes the ability to push to or clone Git repositories over HTTP(S).
To disable HTTP(S) access:
- Go to
> Server settings. - Uncheck HTTP(S) enabled.
- Select Save.
Last modified on Jun 21, 2021
Related content
- Bitbucket Server webhook is not providing git URL is response payload.
- Can't access Bitbucket Server with Git - Issuer certificate is invalid
- Git command returns "not found" or error code 404
- Bitbucket Server: Git operations fails with error fatal: unable to access.. Encountered end of file
- Permanently authenticating with Git repositories
- Unable to push changes to the repository in Bitbucket Server with insufficient permission error over HTTPS URL
- Can't clone or pull due to a git outbound proxy
- Unable to push changes to the repository in Bitbucket with insufficient permission error over HTTPS URL
- How to serve your Bitbucket Server repo without using Bitbucket Server
- Specify the Bitbucket base URL
Powered by Confluence and Scroll Viewport.