As per following document https://confluence.atlassian.com/fisheye/fisheye-ssl-configuration-298976938.html we configured fisheye SSL but unfortunately I am not able to access through secure port (I am able to access non secure port: http://<host name>:8060/crucible)
Below are my environment details:
Java Version : 1.8.0_162
Java Vendor : Oracle Corporation
I am able to see the below in log:
Site Url : https://<host name>:9443/crucible
Web Context :crucible
Http Bind ::8060
Https Bind ::9443
Https Context :crucible
What happens when you try to access Fisheye through HTTPS in the browser? Can you let us know what error is displayed in the browser?
Screenshots are welcome.
In addition, you can also check for errors in Fisheye logs after starting Fisheye to have a better idea of the error being thrown in the logs. The log files are located in <FISHEYE_INST>/var/log/atlassian-fisheye-yyyy-mm-dd.
thanks for your response and below are the details,
I have enabled DEBUG mode but I don't see any thing in logs when I tried HTTPS through web browser.
Below is the exception I am getting in Chrome.
server.com uses an unsupported protocol.
ERR_SSL_VERSION_OR_CIPHER_MISMATCHHIDE DETAILSUnsupported protocolThe client and server don't support a common SSL protocol version or cipher suite.
I tried to few Ciphers but didn't succeed. Please suggest.
I believe the error, from searching online, is as it states, there is a mismatch in the cipher suite being provided and what is supported by the protocol provided and your JVM. You can use the two resources below to investigate:
Despite that, I just want to clarify that the example provided on the page is just to show how you can specify adding and excluding protocols and cipher suites. The values you actually provide will be based on what your certificate, java version, and or your security team require. It is not necessarily needed to complete SSL setup. Once you’ve followed the steps on our FishEye SSL Configuration page you should be able to access your site via HTTPS at the port you’ve defined.
Create the JKS file from the PKCS#12 file generated above – use the same password for the both
keytool -importkeystore -deststorepass <MY_DESTINATIONSTORE_PASSWORD> -destkeypass <MY_DESTINATIONKEY_PASSWORD> -destkeystore <keystore file name> -srckeystore <p12 output file> -srcstoretype PKCS12 -srcstorepass <MY_PKC12_KEYSTORE_PASSWORD>
Using JKS format directly fixed the issue, I didn't convert the format to PKC12 like above.
Hi All! We’re excited to share the launch of an announcement banner that lets Jira site administrators communicate directly to their users across their Jira Cloud instance. ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events