I have an instance of Atlassian FishEye+Crucible running in a server in a standard HTTP connection. But we need this instance to be also accessed from outside, over a HTTPS connection. Proposed solution? Revese Proxy, what already works fine for other Atlassian products, such as JIRA and Confluence.
But FishEye+Crucible is being a torturer problem since it does not work from outside: the logon screen loads with no style (in a CSS way) and it doesn't login, redirecting for a mistaken URL.
I have already tried the Atlassian proposed solution, but it did not work. I also tried something proposed in a Server Fault entry, and nothing happened again.
So, I ask: do anyone have a clue to make it work?
I'm using FishEye + Crucible version 2.7.15 and Apache httpd version 2.2.
My httpd.conf looks like this:
<IfModule ssl_module> Include conf/extra/httpd-ssl.conf SSLRandomSeed startup builtin SSLRandomSeed connect builtin </IfModule> <IfModule proxy_module> SSLProxyEngine On ProxyRequests Off ProxyPreserveHost Off <Location /crucible> ProxyPass http://INTERNAL_ADDRESS:LOCAL_PORT ProxyPassReverse http://INTERNAL_ADDRESS:LOCAL_PORT </Location> </IfModule>
And my config.xml (FishEye+Crucible configuration file):
<web-server> <http bind=":LOCAL_PORT"/> </web-server>
Finally, my architecture looks like this:
Outside World/Browser <-- HTTPS --> Apache httpd <-- HTTP --> FishEye + Crucible
Thanks in advance for all help!
Please set the context on the FishEye/Crucible Server settings to match the context being proxied. In your case this will be "crucible".
BTW, FishEye/Crucible configures its internal Jetty instance programmatically. You cannot configure it with a jetty-web.xml file
Thank you very much! It has worked perfectly! :D
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi MacNeill,
I'm very new to Crucible. I have similar problem. Can you please provide code snippet like how to set Context on FishEye/Crucible.
Thanks in Advance.
Regards
Venkat
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Guiraldelli
Everything seems to be fine from Apache side. However, you'll have to review some settings from Jetty, which is the app. server for Fisheye.
Will be something like this:
<Configure id=
"Server"
class
=
"org.mortbay.jetty.Server"
>
...
<Call name=
"addConnector"
>
<Arg>
<New
class
=
"org.mortbay.jetty.nio.SelectChannelConnector"
>
<Set name=
"port"
>
8080
</Set>
<Set name=
"forwarded"
>
true
</Set>
<Set name=
"hostHeader"
>example.com:
81
</Set>
</New>
</Arg>
</Call>
...
</Configure>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Paulo,
I have a little problem when I tryed your approach (that seems valid): could you help again, please?
As support, I'm providing you my FishEye output log and my jetty-web.xml.
Thank you for all your attention.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.