Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    geotube
    @indeOWS
    Hi all. I have installed geonode-project.It seems that geonode is not seeing the .override_dev_env file, because ALLOWED_HOSTS takes effect only when I add it to the settings.py. ALLOWED_HOSTS=[ '172.21.14.45', 'localhost', 'django', 'geonode']. Any comment on that will be very appreciated
    @dpadron, what is the response for python -V? Also try python3 -m pip install --upgrade pip and pip3 install -r requirements.txt --upgrade --no-cache --no-cache-dir
    johngaldo12
    @johngaldo12
    Hello can anyone help me debug geonode
    Florian Hoedt
    @gannebamm
    Hi @johngaldo12 . You can use eg. PyCharm CE to debug geonode. Just clone the files, do a debug install and instead of using paver start configure a debug run config in PyCharm.
    You should use paver start_geoserver to get that one running though
    Florian Hoedt
    @gannebamm

    Hi, I am still new to django/geonode-project. If there are new updates to the geonode core codebase, how would someone update their own codebase?

    Is this the proper way for a docker setup assuming the installation setup mentioned in the docs:

    geonode@ubuntu:/opt/geonode_custom/geonode-project$ git pull
    geonode@ubuntu:/opt/geonode_custom/my_geonode$ docker-compose -f docker-compose.yml build --no-cache
    So first get the geonode-project codebase updated and than rebuilt the containers for my_geonode?
    Florian Hoedt
    @gannebamm
    thanks @afabiani

    I can not reach jenkins to test the backup & restore options:

    nginx4tisdex     | 2020/10/30 08:32:24 [error] 23#23: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 134.110.12.52, server: 134.110.12.52,
    request: "GET /jenkins HTTP/1.1", upstream: "http://172.22.0.4:9080/jenkins", host: "134.110.12.52"

    I have changed localhost to the ip. Letsencrypt is disabled (since I do not have a domain name for that dev VM)

    Florian Hoedt
    @gannebamm

    Furthermore I've spotted this in the pavement and am puzzled if this is intended:

    invoke.log
    Public PORT is None
    
    tasks.py:
    
    def _geonode_public_port():
        gn_pub_port = os.getenv('GEONODE_LB_PORT', '')
        if not gn_pub_port:
            gn_pub_port = _container_exposed_port(
                'nginx',
                os.getenv('GEONODE_INSTANCE_NAME', 'geonode')
            )
        elif gn_pub_port in ('80', '443'):
            gn_pub_port = None
        return gn_pub_port

    Is this intended? None is not a proper port, why is this not just '80'/'443' or ''?

    Florian Hoedt
    @gannebamm
    Being able to just use
    docker exec django4my_geonode /bin/sh manage.sh sync_geonode_layers updatethumbnails --help
    to fire up management commands is nice. Thanks GeoSolutions for the good implementation
    Villa
    @villa101101
    Hey everyone, not sure if this is the best place for this query but I will get right t it. So I have been trying to install an instance of Geonode that uses the PostgreSQL database and not the MYSQL db. However, the instance works relatively fine with using the MYSQL db but I keep run into difficulties when I follow the instructions on how to use the postgreSQL db instead.
    johngaldo12
    @johngaldo12
    image.png
    Can Anyone Help me with this error :(
    Database is Locked . Geonode on Windows . Error appears when uploading layers or documents.
    Florian Hoedt
    @gannebamm
    The database locked issue is a known issue with SQLite. Try to switch to a PostgreSQL backend instead.

    Hey everyone, not sure if this is the best place for this query but I will get right t it. So I have been trying to install an instance of Geonode that uses the PostgreSQL database and not the MYSQL db. However, the instance works relatively fine with using the MYSQL db but I keep run into difficulties when I follow the instructions on how to use the postgreSQL db instead.

    You need to change several variables. For a developer setup take a look at this workshop which I held on the GeoNode summit 2020: https://github.com/gannebamm/geonode-workshop
    Part 01 does cover a PostgreSQL setup.

    Villa
    @villa101101
    hey @gannebamm thanks for that useful set of instructions. Currently, it seems like the connections hasn't been configured properly because i am getting "'DatabaseOperations' object has no attribute 'select'" when i try to upload a document, or layer in geonode. I am able to create a user and sign in okay along with updating a users details.
    Villa
    @villa101101
    Screenshot 2021-02-11 at 3.31.37 PM.png
    Florian Hoedt
    @gannebamm
    Strange error. Do you have enabled PostGIS? What are your connection strings? Do you use postgis in the connection string? Shooting in the dark here
    Villa
    @villa101101
    i have fixed the issue. It was pulling the environmental variables from the wrong file which had some of the requirements for the postgresql setup but not all.
    Florian Hoedt
    @gannebamm
    Nice! Good to hear
    Abdelghafour BENKHELIFA
    @Abdelghafour1
    I installed geonode 3.1 on windows, I followed all the steps mentioned in the tutorial, when I managed to launch geonode by paver start, I found that geoserver works normally but django does not launch it, and i get no error, is the problem in the pavement.py file or in my installation? after the launch of the command paver start the operation stops here : 2021-02-16 09:33:39.244:INFO:oejs.Server:main: Started @20831ms
    When i run django with paver start_django, it runs fine. the same case for geoserver
    Villa
    @villa101101

    ConnectionError at /proxy/
    HTTPConnectionPool(host='geoserver', port=8080): Max retries exceeded with url: /geoserver/pdf/create.json?access_token=c39bLGzgZ4D5a5y8lxjmIjID7UbFAM (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f3a5a32abb0>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))

    Got that error when I try to print a map or layer in Geonode. Using version 3.1

    johngaldo12
    @johngaldo12

    I installed geonode 3.1 on windows, I followed all the steps mentioned in the tutorial, when I managed to launch geonode by paver start, I found that geoserver works normally but django does not launch it, and i get no error, is the problem in the pavement.py file or in my installation? after the launch of the command paver start the operation stops here : 2021-02-16 09:33:39.244:INFO:oejs.Server:main: Started @20831ms

    Have you tried uploading layers and there was no error?

    Darko Nedic
    @Darkonyks

    Hi everyone,

    I have docker installation of GeoNode with all defaults: my_geonode, my_geonode_data etc. Now I'm truing to change default password for user my_geonode in PostgreSQL and I did. Also, I have change in .env file to new password

    GEONODE_DATABASE=my_geonode
    GEONODE_DATABASE_PASSWORD="my new password"
    I'm not sure if this is an issue but after changing password geonode is not able to start:

    psql: FATAL: password authentication failed for user "my_geonode"
    my_geonode is unavailable - sleeping
    I'm not sure if this is an issue or not but I do not know where else this new password should also be placed.

    Villa
    @villa101101

    Hi everyone,

    I have docker installation of GeoNode with all defaults: my_geonode, my_geonode_data etc. Now I'm truing to change default password for user my_geonode in PostgreSQL and I did. Also, I have change in .env file to new password

    GEONODE_DATABASE=my_geonode
    GEONODE_DATABASE_PASSWORD="my new password"
    I'm not sure if this is an issue but after changing password geonode is not able to start:

    psql: FATAL: password authentication failed for user "my_geonode"
    my_geonode is unavailable - sleeping
    I'm not sure if this is an issue or not but I do not know where else this new password should also be placed.

    did you change it in the settings file?

    Darko Nedic
    @Darkonyks

    did you change it in the settings file?

    I do not find any line in settings.py where it should be changed. And why it should be changed in settings and where? I have used instructions for Basic installation and all crucial information's are placed in .env file ? At least that's what writes in instructions: https://docs.geonode.org/en/master/install/basic/index.html#second-step-deploy-geonode-on-a-production-server-e-g-https-my-geonode-geonode-org

    Pablo Zader
    @polzader
    Hello, I have got a quick question, I am running geonode/geoserver projecct using docker . How to I enable cors in geoserver? I possible?
    Alessio Fabiani
    @afabiani
    @polzader sure, you will need to tweak NGINX configuration and JAVA OPTS
    Pablo Zader
    @polzader
    @afabiani I configure nginx and tomcat but it still doesn't work. Could you help me? I am using https://hub.docker.com/r/geonode/geoserver
    Darko Nedic
    @Darkonyks

    did you change it in the settings file?
    Hi Villa,

    I have "hard coded" password on any place I find in my geonode project:

    grep -r GEONODE_GEODATABASE_PASSWORD .
    ./tasks.py:        "geonode_geodb_passwd": os.environ.get('GEONODE_GEODATABASE_PASSWORD', '1234'),
    ./tasks.py:    ctx.run("echo export GEONODE_GEODATABASE_PASSWORD=\
    ./tasks.py:    geopwd = os.getenv('GEONODE_GEODATABASE_PASSWORD', '1234')
    ./scripts/spcgeonode/.env:GEONODE_GEODATABASE_PASSWORD=1234
    ./scripts/spcgeonode/docker-compose.yml:    - GEONODE_GEODATABASE_PASSWORD=${GEONODE_GEODATABASE_PASSWORD}
    ./scripts/spcgeonode/docker-compose.yml:    - GEODATABASE_URL=postgis://${GEONODE_GEODATABASE_USER}:${GEONODE_GEODATABASE_PASSWORD}@postgres:5432/${GEONODE_GEODATABASE}
    ./scripts/spcgeonode/docker-compose.yml:      - GEODATABASE_URL=postgis://${GEONODE_GEODATABASE_USER}:${GEONODE_GEODATABASE_PASSWORD}@postgres:5432/${GEONODE_GEODATABASE}
    ./scripts/spcgeonode/docker-compose.yml:      - DATABASE_URL=postgres://${GEONODE_GEODATABASE_USER}:${GEONODE_GEODATABASE_PASSWORD}@postgres:5432/${GEONODE_GEODATABASE}
    ./scripts/spcgeonode/docker-compose.yml:      - GEONODE_GEODATABASE_PASSWORD=${GEONODE_GEODATABASE_PASSWORD}
    ./scripts/spcgeonode/docker-compose.yml:      - GEODATABASE_URL=postgis://${GEONODE_GEODATABASE_USER}:${GEONODE_GEODATABASE_PASSWORD}@postgres:5432/${GEONODE_GEODATABASE}
    ./scripts/spcgeonode/postgis/initdb-geonode.sh:        ALTER USER $geodb with encrypted password '$GEONODE_GEODATABASE_PASSWORD';
    ./scripts/docker/env/production/db.env:GEONODE_GEODATABASE_PASSWORD=1234
    ./scripts/docker/env/production/django.env:GEONODE_GEODATABASE_PASSWORD=1234
    ./scripts/docker/env/development/db.env:GEONODE_GEODATABASE_PASSWORD=1234
    ./scripts/docker/env/development/django.env:GEONODE_GEODATABASE_PASSWORD=1234
    ./.env_dev:GEONODE_GEODATABASE_PASSWORD=geonode_data

    also in Docker images

    ./tasks.py:        "geonode_geodb_passwd": os.environ.get('GEONODE_GEODATABASE_PASSWORD', '1234'),
    ./tasks.py:    ctx.run("echo export GEONODE_GEODATABASE_PASSWORD=\
    ./tasks.py:    geopwd = os.getenv('GEONODE_GEODATABASE_PASSWORD', '1234')
    ./scripts/spcgeonode/.env:GEONODE_GEODATABASE_PASSWORD=1234
    ./scripts/spcgeonode/docker-compose.yml:    - GEONODE_GEODATABASE_PASSWORD=${GEONODE_GEODATABASE_PASSWORD}
    ./scripts/spcgeonode/docker-compose.yml:    - GEODATABASE_URL=postgis://${GEONODE_GEODATABASE_USER}:${GEONODE_GEODATABASE_PASSWORD}@postgres:5432/${GEONODE_GEODATABASE}
    ./scripts/spcgeonode/docker-compose.yml:      - GEODATABASE_URL=postgis://${GEONODE_GEODATABASE_USER}:${GEONODE_GEODATABASE_PASSWORD}@postgres:5432/${GEONODE_GEODATABASE}
    ./scripts/spcgeonode/docker-compose.yml:      - DATABASE_URL=postgres://${GEONODE_GEODATABASE_USER}:${GEONODE_GEODATABASE_PASSWORD}@postgres:5432/${GEONODE_GEODATABASE}
    ./scripts/spcgeonode/docker-compose.yml:      - GEONODE_GEODATABASE_PASSWORD=${GEONODE_GEODATABASE_PASSWORD}
    ./scripts/spcgeonode/docker-compose.yml:      - GEODATABASE_URL=postgis://${GEONODE_GEODATABASE_USER}:${GEONODE_GEODATABASE_PASSWORD}@postgres:5432/${GEONODE_GEODATABASE}
    ./scripts/spcgeonode/postgis/initdb-geonode.sh:        ALTER USER $geodb with encrypted password '$GEONODE_GEODATABASE_PASSWORD';
    ./scripts/docker/env/production/db.env:GEONODE_GEODATABASE_PASSWORD=1234
    ./scripts/docker/env/production/django.env:GEONODE_GEODATABASE_PASSWORD=1234
    ./scripts/docker/env/development/db.env:GEONODE_GEODATABASE_PASSWORD=1234
    ./scripts/docker/env/development/django.env:GEONODE_GEODATABASE_PASSWORD=1234
    ./.env_dev:GEONODE_GEODATABASE_PASSWORD=geonode_data

    and it continue to restarting containers:

    CONTAINER ID   IMAGE                      COMMAND                  CREATED             STATUS                          PORTS                                                 NAMES
    c37c9c05f356   geonode/geonode:3.1        "/bin/sh -c 'serviceā€¦"   About an hour ago   Restarting (1) 12 seconds ago                                                         django4geonode
    940b02dcda68   geonode/geonode:3.1        "/bin/sh -c 'serviceā€¦"   About an hour ago   Restarting (1) 6 seconds ago
    A. Israel Lopez
    @isralopez
    Hi, I've a 3.1.x branch SPC Geonode installation via docker... but I can't upload any layer in shapefile... In the last step sends "Unexpected error!"... the logs:
    image.png
    image.png
    what I'm missing??
    A. Israel Lopez
    @isralopez
    Btw the connection geonode/geoserver is not working...
    Alessio Fabiani
    @afabiani
    which installation method you have followed?
    A. Israel Lopez
    @isralopez
    this one... https://docs.geonode.org/en/stable/install/spc/index.html using only the main services...
    on ly local machine with Ubuntu 18.04, I vahe the same problem on a VM with Ubuntu server 18.04...
    Alessio Fabiani
    @afabiani
    which GeoNode branch you used?
    3.1 or 3.x?
    A. Israel Lopez
    @isralopez
    Mmhh 3.x... yesterday I tried with 3.1 and the same...
    Darko Nedic
    @Darkonyks
    Hi, I'm having problem adding Remote Services from local Geoserver. I have Geonode 3.2.x docker installation. More about the issue GeoNode/geonode-project#171
    A. Israel Lopez
    @isralopez
    Any help with my SPC issue?? good afternoon
    Darko Nedic
    @Darkonyks
    @afabiani @villa101101 @gannebamm People I really need your help with problem with WMS services please take a look on issue GeoNode/geonode-project#171 . I have lost a days truing to make it work but I failed! Any help is most welcome !
    4 replies
    Alessio Fabiani
    @afabiani
    @Darkonyks I'm afraid you are not allowed currently to load an endpoint with an invalid certificate. HTTPS won't work with IP addresses unfortunately. But I'll try to give it a shot.
    Darko Nedic
    @Darkonyks
    @afabiani Hi Alessio, I was thinking that this is a problem, but on open issue I have shown example with IP address. I have GeoNode running on production with hostname all set up DNS etc... But also I do not have valid SSL either. Because my GN instance runs on subdomain. Domain has a valid SSL subdomain wildcard. So my next move is to import valid SSL from domain. Thanks a lot!!