[GeoNode-users] upload, WMS and permission errors

Simone Dalmasso simone.dalmasso at gmail.com
Mon Mar 16 08:30:12 PDT 2015

Hi, you need to add the target domain to the PROXY_ALLOWED _HOSTS directive
in the settings.
It should be like ("domain.com",)

Il martedì 10 marzo 2015, santos luis quispe choque <santoslqc at gmail.com>
ha scritto:

> Dear
> Again with my questions, I tell them we are implementing a node, for that
> we are installing the GeoNode 2.0.1, everything is OK except that when
> Harvesting (WMS) with other nodes i get error. I can not connect what does
> not happen with the 2.0.
> I ask you can help me.
> Beforehand thank you very much for your help
> Best Regards
> The error is as follows:
> [image: Imágenes integradas 1]
> DEBUG is set to False but the host of the path provided to the proxy
> service is not in the PROXY_ALLOWED_HOSTS setting.
> 2015-03-10 12:11 GMT-04:00 Ariel Nunez <ingenieroariel at gmail.com
> <javascript:_e(%7B%7D,'cvml','ingenieroariel at gmail.com');>>:
>> Gavin,
>> I'll try to come up with possible explanations for the errors you are
>> seeing:
>> 1) This happens from time to time, especially with big files over slow
>> networks. A timeout occurs and then the web page stops listening for the
>> json return, even though it all went fine. The best way to deal with this
>> in the future is to switch to asyncronous upload/configuration and do some
>> sort of polling.
>> 2) You got no error from the upload widget? Was there anything in the
>> logs? We improved this for 2.4 adding a place in the django admin where you
>> can go to look for failed uploads and keeps the geoserver log and the
>> django log. But it is not available in 2.0
>> 3) Not sure what could be going on.
>> 4) Also no idea
>> 5) To me, the problem could be in the geoserver-geonode-ext plugin. That
>> is the plugin for geoserver that handles the authentication, and it could
>> be misbehaving. potentially due to lack of resources (too little ram). What
>> is your configuration?
>> Something sounds bad there, but my recommendation is to run 2.4 instead,
>> we are getting close to a release and I would advice against having to
>> migrate in a few months. The pros of using 2.4 over 2.0 outweigh the cons
>> (IMHO).
>> -a
>> On Tue, Mar 10, 2015 at 10:59 AM, Gavin Fleming <gavin at kartoza.com
>> <javascript:_e(%7B%7D,'cvml','gavin at kartoza.com');>> wrote:
>>> :buildings_osm_maumere
>> That part should probably have been workspace:layer_name (or
>> geonode:buildings_osm_maumere)
>> The fact that there is no workspace indicates there could have been a
>> problem.
>> _______________________________________________
>> geonode-users mailing list
>> geonode-users at lists.osgeo.org
>> <javascript:_e(%7B%7D,'cvml','geonode-users at lists.osgeo.org');>
>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-users/attachments/20150316/70efcb6d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 1587946 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/geonode-users/attachments/20150316/70efcb6d/attachment-0001.png>

More information about the geonode-users mailing list