Can you point me to the https docs for thin? Normally links are generated with the protocol and host of the current request, if some links are http, it probably means that ChiliProject doesn't know the current request is over ssl.

I'm not sure what you mean. We didn't have to setup anything for Thin, simply included the gem in ChiliProject bundle and run it:

bundle exec thin start --ssl --ssl-key-file certificate.key --ssl-cert-file certificate.crt --ssl-verify -e production

Thin SSL support started with release 1.2.8:

http://groups.google.com/group/thin-ruby/browse_thread/thread/ebb73ddd0fb35ad9#

How savvy are you with html and rails? Could you check the generated page contains https only links in the places you've mentioned, for example in the project list? Next step would probably be to check if thin correctly sets the ENV['HTTPS'] correctly on requests.

Newbie.

HTML has relative paths and browser shows https URL with mouse over link, for e.g.

<select onchange="if (this.value != '') { window.location = this.value; }"><option value=''>Jump to a project...</option><option value="" disabled="disabled">---</option><option value="/projects/test-project?jump=overview">Test Project</option></select>

Regarding the ENV['HTTPS'] setting I don't know how to check it but if it wasn't set wouldn't all links refer to http instead of most refering to https and some redirecting to http?

Have you made sure to select HTTPS in Administration -> Settings -> General -> Protocol?

ChiliProject typically generates links without an explicit host and protocol. Sometimes, it requires to use the complete host and protocol. It then uses the information specified there.

Yes, Protocol is set to HTTPS.

But as far as I've read on Redmine/ChiliProject forums this setting is only used for links in the email notifications, not for the app links.

Manuel Pais wrote:

Yes, Protocol is set to HTTPS.

But as far as I've read on Redmine/ChiliProject forums this setting is only used for links in the email notifications, not for the app links.

It is only used for the mails, yes.

I'm still not sure this isn't some bizarre problem with thin, would you be open to logging the request object ChiliProject sees and decides wether to present http or https links on?

Sure, just let me know what I have to do.

thanks

Sorry it took me a few days to get back to you, my HDD died beginning of the week and I had to make up the lost time.

Try the following diff:

 1diff --git a/app/controllers/application_controller.rb b/app/controllers/application_controller.rb
 2index 57d77f5..2e1cb36 100644
 3--- a/app/controllers/application_controller.rb
 4+++ b/app/controllers/application_controller.rb
 5@@ -56,6 +56,7 @@ class ApplicationController < ActionController::Base
 6   end
 7
 8   def user_setup
 9+    logger.info "Request: https: #{request.env['https'].inspect} ; x_forwarded_proto: #{request.env['HTTP_X_FORWARDED_PROTO'].inspect}" if logger
10     # Check the settings cache for each request
11     Setting.check_cache
12     # Find the current user

This should show a line like Request: https: nil ; x_forwarded_proto: nil for each request in your ChiliProject logs, if it says anything else than on for the first or https for the second paramater, then the request won't be recognized as an ssl one. If that doesn't show discrepancies, we'll have to inspect the other parts of the request…

No worries Felix, hope you could recover all your data!

This brings us to another problem I just found out: the logs stopped working since a couple of weeks ago.

The only reason I can think of is that before the logs stopped working I installed the Redcase plugin (from Redmine) which didn't function properly and then I removed it and restarted ChiliProject.

Any ideas? It's hard to debug without logs :)

Manuel Pais wrote:

The only reason I can think of is that before the logs stopped working I installed the Redcase plugin (from Redmine) which didn't function properly and then I removed it and restarted ChiliProject.

Wrong permissions? Can't tell really, never heard of something like that unless the disk was full.

OK, I found out the (no) log issue happens when running thin as a task in Windows.

Anyway I can now log the Request info and it always shows like this:

Request: https: nil ; x_forwarded_proto: nil

Regardless if it's an https request or an http request.

Manuel Pais wrote:

OK, I found out the (no) log issue happens when running thin as a task in Windows.

Anyway I can now log the Request info and it always shows like this:

Request: https: nil ; x_forwarded_proto: nil

Regardless if it's an https request or an http request.

I'd say something on the way to your ChiliProject instance gobbles up the information whether it's https or not. I've never used thin though, so I can't tell you where the problem is, but maybe you have to tell it to pass the X_FORWARDED_PROTO header through or something.

thin is very simple, it has no configuration files or anything so I don't know how to change the header.

the ChiliProject installation instructions refer to using thin as webserver so I thought you'd be able to help me with this problem.

but i guess you've never tried it with SSL?

I've personally never used thin at all :-)

It seems thin doesn't set the env stuff rails expects to detect if it's ssl. You could try logging the whole request ("Request: #{request.inspect}") and see if you find any mention of ssl, but that could get a lot quickly.