I sent an email with our issue, but i thought maybe someone could benefit from whatever we learn here. That and I think Commit support is tired of my emails.
We FINALLY got our SSL files in the correct format.
If we go to http://127.0.0.1:4961 or https://127.0.0.1:4962 locally we can login both ways and the https site says it is secure with the little padlock and all.
Only problem is it only works locally. When we change the UseSSLEncryption=N to UseSSLEncryption=Y. we cant login from the web anymore.
we have the external ip set to commit.mywebsite.com and an A records from the dns web server pointing to the server's external IP. Works fine until we turn the SSL N to Y.
What else do we need to change to make it work?
Second question: is there a way to force SSL only once this is working? I don't want anyone using the unsecured version anymore. (Other than blocking the port on the firewall)
I would rather it redirect everyone so customers and employees have a smooth transition.
We FINALLY got our SSL files in the correct format.
If we go to http://127.0.0.1:4961 or https://127.0.0.1:4962 locally we can login both ways and the https site says it is secure with the little padlock and all.
Only problem is it only works locally. When we change the UseSSLEncryption=N to UseSSLEncryption=Y. we cant login from the web anymore.
we have the external ip set to commit.mywebsite.com and an A records from the dns web server pointing to the server's external IP. Works fine until we turn the SSL N to Y.
What else do we need to change to make it work?
Second question: is there a way to force SSL only once this is working? I don't want anyone using the unsecured version anymore. (Other than blocking the port on the firewall)
I would rather it redirect everyone so customers and employees have a smooth transition.
Comment