Hello. I'm having this problem on both my Moodle and LimeSurvey jumpboxes so something weird is going on. When I manually set the public hostname to its FQDN and then turn on SSL, when attempting to access the application from the WAN, by using the FQDN, and only on the SSL port (non-SSL 80 works fine), you can't connect. What I found, when connecting on the LAN, is that it is redirecting to the server's private, non-routeable IP address. Where is it being held up? There must be a setting in Apache that makes the browser want to redirect to the IP but I sure can't find it. Any ideas? DNS is set up correctly, both internally and externally. HTTP works fine, but HTTPS won't connect.
Public hostname problems
I think this is a bug in our public address code. The situation is complicated in this case because both applications use their IP address/hostnames.
I have filed a ticket on this issue. I don't know that we will get to it right away, however.
Austin
Is there somewhere I can
Is there somewhere I can manually override this? At this point it seems like my only option is to not use HTTPS...
Public hostname problems
Well, yes, there is. I just don't know what that is until I try and reproduce it myself, which I have not had a chance to do yet.
Lets look at limesurvey first, what is the Public Name you have entered into the JumpBox Administration page and what does the following command return:
Austin
I'm going to purchase a
I'm going to purchase a support case for this. It's too important to keep to these forums.