Permission denied in Apache logs when used as a reverse proxy
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
When using Apache as a reverse proxy, Apache responds with a message that the Bitbucket server is not available and the following can be seen in the Apache error logs:
[error] (13)Permission denied: proxy: HTTP: attempt to connect to 192.168.1.1:7990 (bitbucket.example.com) failedDiagnosis
Environment
- This error can occur on RedHat or CentOS.
Cause
By default, SELinux prevents Apache from initiating outbound connections, so it is unable to proxy requests to Bitbucket Server.
Resolution
Run the following command on the server to allow Apache to make outbound connections.
/usr/sbin/setsebool -P httpd_can_network_connect 1You can also review the SELinux configurations and add the Bitbucket ports, by following instructions from the Change Ports Numbers document.