nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

[Solved] HTTPS for bitbucket but not show a lock

Nicolás Royo Ruiz

Hi,

I've installed a wildcard certificate, and import to cacert store, but my web direction not show a lock, but the address https://stash.overtus.com/ is correct.

In my jira instance address and lock are ok.

Thanks in advance.

Accepted answers

Nicolás Royo Ruiz

My mistake.

Add additional connector to ssl at bitbucket.propierties instead of conector simple:

server.secure=true
server.scheme=https
server.proxy-port=443
server.proxy-name=mycompany.com<br>

Thanks for all

All comments

Christian Glockner

Hi Nicolas,

I don't know which browser you are using, but I just tried with Chrome, and there's definitely a lock displayed.

Cheers,

Christian

Premier Support Engineer

Atlassian

Nicolás Royo Ruiz

Oh Thanks! In Safari don't show!

I've tried in Chrome, and I must to explain better. When I logged, lock don't show.

Show the message "Info or Not secure", https://support.google.com/chrome/answer/95617?visit_id=1-636543853872287763-3712397161&p=ui_security_indicator&rd=1.

But in the information of certificate show 'Valid'.

Christian Glockner

Hi Nicolas,

I'm seeing a lock in Safari as well, so the problem doesn't seem to be with your site it seems. In Chrome it says "Secure" for me.

Cheers,

Christian

Premier Support Engineer

Atlassian

Nicolás Royo Ruiz

Captura de pantalla 2018-02-16 a las 15.39.35.png

When I do the logging event, https stay but lock disappear.

I think that not showing error on Troubleshooting and support tools page:

Captura de pantalla 2018-02-16 a las 15.43.03.png

I will check again Nginx, and system log, just in case.

Thanks in advance.

Nicolás Royo Ruiz

My mistake.

Add additional connector to ssl at bitbucket.propierties instead of conector simple:

server.secure=true
server.scheme=https
server.proxy-port=443
server.proxy-name=mycompany.com<br>

Thanks for all

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bitbucket