[GeoNode-users] problem to install geonode on a remote vm
ingenieroariel at gmail.com
Wed Sep 23 10:07:37 PDT 2015
You best bet is to set a domain name that resolves both locally and
externally to the right IP address.
GeoNode stores the full URL internally in a few places, the main reason is
historical because geonetwork and geoserver need fully qualified urls
instead of relative ones. It would be interested to have someone
investigate how to remove that restriction from GeoNode.
On Wed, Sep 23, 2015 at 10:12 AM, Charles Cossé <ccosse at gmail.com> wrote:
> Hi, we have an issue running the latest GeoNode on a virtual server. From
> our LAN we access via a 192.168 ip address. Externally we access via
> another, real ip address. But when we access externally the image
> thumbnails and layers fail to show because they are referencing the 192.168
> address. Looking through the database ("maps_mapsnapshot" table) I found
> that GeoNode had ingested the 192.168 address and was generating links from
> there. I concluded that having 2 ips (one internal, one external) must
> not be possible given what was happening. I don't see any way around it
> and we're re-configuring our systems to use a single IP as a result.
> Charles Cossé
> Guyana Forestry Commission
> Georgetown, Guyana
> On Wed, Sep 23, 2015 at 10:02 AM, Giuseppe Ricci <peppepegasus at gmail.com>
>> Hi guys,
>> I'm trying to install geonode on a virtual machine installed on Micrsoft
>> Azure server.
>> I followed this tutorial:
>> but when i give this command:
>> sudo geonode-updateip localhost:4567
>> I receive this errors:
>> $ sudo geonode-updateip localhost:4567
>> Replacing SITEURL value with 'localhost:4567' in
>> /etc/geonode/local_settings.py ... done.
>> Adding entry for 'localhost:4567' in
>> /usr/share/geoserver/data/printing/config.yaml ... 'localhost:4567' already
>> found to the printing whitelist.
>> Adding localhost:4567 to ALLOWED_HOSTS in /etc/geonode/local_settings.py
>> ... 'localhost:4567' already found in ALLOWED_HOSTS list.
>> * Restarting web server
>> AH00558: apache2: Could not reliably determine the server's fully qualified
>> domain name, using 100.73.20.46. Set the 'ServerName' directive globally to
>> suppress this message
>> [ OK ]
>> Finished processing 0 layers in 0.0 seconds.
>> 0 Created layers
>> 0 Updated layers
>> 0 Failed layers
>> 0.000000 seconds per layer
>> At the adress localhost:4567 I receive the message:
>> web page doesn't exist. ERR_CONNECTION_REFUSED.
>> Can some one to help me?
>> Dott. Giuseppe Ricci
>> Via B. Spaventa 6, Terlizzi
>> Cel. 340 3059772
>> geonode-users mailing list
>> geonode-users at lists.osgeo.org
> geonode-users mailing list
> geonode-users at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the geonode-users