[ckan-dev] CKAN installation issue after enabling SSL

[Carl Lange]

Hi Shashi,

Did you set your ckan.site_url to be https in your production.ini file?

Cheers,
Carl

On 16 May 2016 at 08:53, Mike Sinclair <mm.sinclair08 at gmail.com> wrote:

> If you click "manage resource" > "update" does it flip over to https?
>
> I had this happen before because the resource hadn't updated to reflect
> the change. You could alternatively make nginx less strict.
>
>  add_header 'Access-Control-Allow-Origin...;
>  add_header 'Access-Control-Allow-Methods....;
>
> You've restarted the webserver and have the correct site_url in the config?
>
> Mike
> ᐧ
>
> On Sun, May 15, 2016 at 10:42 PM, Shashi Deshetti <shashi at factly.in>
> wrote:
>
>> Hi Team
>>
>> I am currently working on installing the data portal:
>> https://data.factly.in and running into the following issue after I
>> installed the SSL certificate.
>>
>> Mixed Content: The page at 'https://data.factly.in/' was loaded over
>> HTTPS, but requested an insecure XMLHttpRequest endpoint '
>> http://data.factly.in/api/i18n/en'. This request has been blocked; the
>> content must be served over HTTPS.
>>
>> Similar issue was discussed here in this post
>> <https://lists.okfn.org/pipermail/ckan-dev/2016-March/009850.html>, but
>> a resolution was not mentioned. I followed the steps mentioned here to
>> setup SSL: https://github.com/ckan/ckan/wiki/SSL
>>
>> Any help is greatly appreciated.
>>
>> Thanks,
>> Shashi
>>
>> _______________________________________________
>> ckan-dev mailing list
>> ckan-dev at lists.okfn.org
>> https://lists.okfn.org/mailman/listinfo/ckan-dev
>> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
>>
>>
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20160516/371e2e5d/attachment-0003.html>