[GeoNode-devel] 502 Bad Gateway when saving map

Dimitris Karakostis karakostis.dimitris at gmail.com
Thu May 25 02:56:59 PDT 2017

This resolved issue from Francesco Bartoli fixes the bug:
Now its possible to save the remote layer in a map without any problem.
But I have noticed another bug. When I try to add on my map second layer,
which also belongs to a remote service, the layer is not added and the
geoserver logs throws out:  layer does not exist
Anyone had similar issue?

On Wed, May 24, 2017 at 1:49 PM, Dimitris Karakostis <
karakostis.dimitris at gmail.com> wrote:

> Hello everyone,
> I am getting a 502 Bad Gateway error when I try to save a map, which has
> remote layers.
> The layers come from a remote geoserver and they are created as indexed
> (not as cascaded).
> They are displayed correctly in the layer_detail/map_detail pages and I
> can also print them (I have configured the yml file of mapfish). Moreover,
> I have modified the settings.py file and added the host name in the
> When I create a map, the layers are displayed correctly but I can not save
> the map. I get:
> "The server returned an error: 502 Bad Gateway"
> If I try to load the layers from the remote server manually using the "add
> layer" tool in geoexplorer, then everything works correctly and the map is
> saved.
> As I understand this must be a network issue. Anyone has experienced
> something similar?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-devel/attachments/20170525/151f009c/attachment.html>

More information about the geonode-devel mailing list