In my Stash installation I configured tomcat's server.xml and web.xml according to this link so that HTTP is blocked and automatically redirected to HTTPS. Using a self-signed certifcate the stash backup client runs into trouble, output is:
2014-10-10 13:13:36,673 ERROR A backup could not be created. Reason: java.lang.RuntimeException: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No name matching <our real and existing servername> found org.apache.wink.client.ClientRuntimeException: java.lang.RuntimeException: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No name matching <our real and existing servername> found
What I tried:
What can I do to get this working?
Is there a way to allow HTTP connections to tomcat from localhost only?
Thanks in advance
You can also try it the other way around: Program a workaround, example: http://pastebin.com/g8KFQHms This class calls the backup client, but before excludes localhost from certificate checking. Compile it with something like: javac -cp .:stash-backup-client.jar SSLWorkAround.java And run it with: java -cp .:stash-backup-client.jar SSLWorkAround
So both logfile and the certicate show the same sever FQDN? I was assuming a mismatch between the certificate and the server configuration. If thats not the case i recommend opening a ticket with Atlassian Support. Maybe the backup tool cannot deal with the redirect from http to https when communicating with the server.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes it's like myhost.myprovider.com. In backup-config.properties I specified https://myhost.myprovider.com.net:8443. myhost.myprovider.com is a technical domain name like you get it when ordering a root server
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is the server name shown in FQDN format?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.