[GeoNode-users] Problems after Upgrade

[Le Ny Conseil]

Add these line at the end of your local_settings.py and add your ip address.

ALLOWED_HOSTS= [ '127.0.0.1', 'localhost', 'IP' ]
PROXY_ALLOWED_HOSTS=('ip_proxy')



2015-03-17 10:36 GMT+01:00 Christian Willmes <
christian.willmes at googlemail.com>:

>  ah great. Thanks!
>
> I was blind looking for that line in local_settings.py, did not see it...
>
> Pro tip: do not let the upgrade procedure overwrite your settings file,
> when it asks you to apply changes from the updated package. :^)
>
> Cheers,
> Christian
>
> Am 17.03.2015 um 10:31 schrieb Le Ny Conseil:
>
> You have got the ALLOWED_HOSTS section at the end of the same file
> (local_settings.py).
>
>
> 2015-03-17 10:28 GMT+01:00 Christian Willmes <
> christian.willmes at googlemail.com>:
>
>>  thanks! That solved the PostGIS problem.
>>
>> I now need to add my server to ALLOWED_HOSTS:
>>
>> [Tue Mar 17 04:24:02.116194 2015] [:error] [pid 1224:tid 140153217300224]
>> Invalid HTTP_HOST header: 'localhost'.You may need to add u'localhost' to
>> ALLOWED_HOSTS.
>>
>> I did set the SITEURL in local_settings.py as before the update.
>>
>> Where is that to configure?
>>
>> Thanks,
>> Christian
>>
>> Am 17.03.2015 um 10:09 schrieb Le Ny Conseil:
>>
>> Hello Christian,
>>
>>  Add this line in your geonode local_settings
>>
>>  POSTGIS_VERSION = (2,1,0)
>>
>> 2015-03-17 10:03 GMT+01:00 Christian Willmes <
>> christian.willmes at googlemail.com>:
>>
>>> Hi,
>>>
>>> im running a geonode 2.4beta from the testing Ubuntu ppa.
>>>
>>> After a apt-get update/upgrade this morning, I can't get geonode to
>>> restart.
>>>
>>> I have this (scary) message in my logs:
>>>
>>> [Tue Mar 17 03:59:59.676955 2015] [:error] [pid 1671:tid
>>> 139799543056128] [remote 127.0.0.1:60324] ImproperlyConfigured: Cannot
>>> determine PostGIS version for database "geonode_data". GeoDjango requires
>>> at least PostGIS version 1.3. Was the database created from a spatial
>>> database template?
>>>
>>>
>>> Any hints, how to solve this?
>>>
>>> Interesting though, that on commandline 'geonode updatelayers' seems to
>>> execute without errors. But it dit not solve the above problem.
>>>
>>> Thanks,
>>> Christian
>>> _______________________________________________
>>> geonode-users mailing list
>>> geonode-users at lists.osgeo.org
>>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users
>>>
>>
>>
>>
>>  --
>>  Pierre-André Le Ny
>> *Le Ny Conseil*
>> http://www.lenyconseil.fr
>>
>>
>>
>> _______________________________________________
>> geonode-users mailing listgeonode-users at lists.osgeo.orghttp://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users
>>
>>
>>
>> _______________________________________________
>> geonode-users mailing list
>> geonode-users at lists.osgeo.org
>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users
>>
>>
>
>
>  --
>  Pierre-André Le Ny
> *Le Ny Conseil*
> http://www.lenyconseil.fr
>
>
>
> _______________________________________________
> geonode-users mailing listgeonode-users at lists.osgeo.orghttp://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users
>
>
>
> _______________________________________________
> geonode-users mailing list
> geonode-users at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users
>
>


-- 
Pierre-André Le Ny
*Le Ny Conseil*
http://www.lenyconseil.fr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-users/attachments/20150324/82043b2d/attachment.html>