tainted SSL

Hey again, many of the SSL complains have been addressed and fixed in the last 2.5 version.
And I'm assuming you're experiencing these issues with 2.1.1.
There's two ways I can suggest you work this out, first have a little patience until 2.5 is final and you'll be settled. Secondly, you could manually take the changes from 2.5 and apply them on your 2.1.1 installation.

I know it's not the best advice one could give you, but this is the situation as of right now.

Strangle it seems fixed since I enabled xmlrpc in my php.ini ....

Have you filled in the Alternate URL in the Settings page?

Could you create a temporary admin account so I could take a look at the site configuration? You can email it to me if you may, [email@chyrpdomain]

I did experiment already plenty with it, but so far no luck. I will send you an admin account+passwd when I am back here (like in 3h or so) Thanks again!

https://braindeadmonkey.com/chyrp for both should be fine, as currently the desired index.php resides within the chyrp directory, correct me if I am wrong

Great, I'd be glad to help out. Until later then.

UPDATE I'm posting this for others to see, drahnr managed to fix it, read below.

fixed it
mimetype.assign = (".html" => "text/html",
                   ".txt" => "text/plain",
                   ".jpg" => "image/jpeg",
                   ".png" => "image/png",
                   ".css" => "text/css")
the line with text/css was missing
this was the sole reason for the css vendetta
this is the fault of the default config shipping lighty
(usually this is not required, dunno why lighty got this wrong this time)

Back to the SSL problem, this seems to be not an issue causedby chyrp, rather sick caching by chromium. Firefox+opera do not show that cert tainted warning.

Update: This was a random cooincident. The actual problem was a badly written theme requiring some other website to work properly (currently in the process of ripping that out).