This question is in reference to Atlassian Documentation: Securing Bitbucket Server behind nginx using SSL
We have JIRA & confluence behind nginx, and we access them like https://jira.domain.dom & https://confluence.domain.com
Your instruction gives way how to access like this: <span class="nolink"><a href="https://mycompany.com:7990/bitbucket" rel="nofollow noopener noreferrer">https://mycompany.com:7990/Bitbucket</a></span>
<span class="nolink"><a href="https://mycompany.com:7990/bitbucket" rel="nofollow noopener noreferrer">https://mycompany.com:7990/Bitbucket</a></span>
Is it a big job to modify tomcat etc. so that the URL would "equal" https://bitbucket.domain.com
If there's already instructions for that, the links would be nice
That is actually how I deploy these applications. Here is the nginx config:
server { listen 443; ssl on; ssl_certificate ssl/yourcertificate.crt; ssl_certificate_key ssl/yourcertiticatekey.key; server_name bitbucket.domain.com; add_header X-Frame-Options ALLOW; location / { proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_pass http://127.0.0.1:7990/; proxy_redirect off; proxy_connect_timeout 300; } } server { listen 80; server_name bitbucket.domain.com; rewrite ^ https://bitbucket.domain.com$request_uri? permanent; }
In the server.xml file, update the connector for port 7990 with these options:
address="127.0.0.1" secure="true" scheme="https" proxyName="bitbucket.domain.com" proxyPort="443"
So the entire connector stanza looks like this:
<Connector port="7990" protocol="HTTP/1.1" connectionTimeout="20000" useBodyEncodingForURI="true" redirectPort="8443" compression="on" compressableMimeType="text/html,text/xml,text/plain,text/css,application/json,application/javascript,application/x-ja vascript" address="127.0.0.1" secure="true" scheme="https" proxyName="bitbucket.domain.com" proxyPort="443"/>
Thank you!
I tried this config and can't seem to get it to stop appending the 7990 at the end. Do you have this issue ?
I do not have that issue. Check the Base URL in the Server Settings page of the admin. If you previously had a port there (:7990), you'll need to remove it from the Base URL field and click "Save" at the bottom of the page.
It looks like you're new here. Sign in or register to get started.