Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Alessio Fabiani
    @afabiani
    I remember this has been specified in the docs
    geotube
    @indeOWS
    @afabiani . I got it. it was my bad. The browser was caching https.
    Francisco Palm
    @map0logo

    Hi, I don't know if this is the right place for this question, if not I apologize.

    I want to develop an "as simple as possible" Geonode extension to load directly a File Geodatabase into Geonode, where could I start?

    The people making the request do not want to do the gdb to shp conversion using ogr2ogr, they want to load the gdb directly from the interface.

    I was checking the osgeo importer and it seems to be significantly out of date, as it is not migrated to Python 3.

    peng22
    @peng22
    Hello
    wish you a good day
    is there like a tutorial to deploy geonode on https instead of http?
    Villa
    @villa101101
    Good day, How do I show only layers in the search catalogue when creating a map ?
    Rebecca Dittmann
    @Saxas13_twitter

    Screenshot 2021-04-16 at 4.42.56 PM.png

    I encounter the same issue, is there a way to fix it in geonode 3.1?

    Villa
    @villa101101

    Screenshot 2021-04-16 at 4.42.56 PM.png

    I encounter the same issue, is there a way to fix it in geonode 3.1?

    You need to confirm that the print map request is going to the right address. You can confirm that the right geoserver address is been used in the geoserver/data/printing/config.yaml file

    Villa
    @villa101101
    Screenshot 2021-05-21 at 7.16.34 PM.png

    Screenshot 2021-05-21 at 7.16.34 PM.png

    Get this error when I try to print a map with a legend, on A4 portrait. I get this error only with these settings.

    Villa
    @villa101101

    @gannebamm @afabiani Do you have any suggestions on how to show only layers in the catalog section when creating a map ?

    Also, Getting an error on printing a map when i choose A4 paper size, with a legend on the same page in portrait mode.

    any assistance would be appreciated.

    Alessio Fabiani
    @afabiani
    @villa101101 about the catalog you need to update the code to 3.2.0 or 3.2.x
    the printing error might depends on a wrong geoserver printing layout
    I suggest to use the default one provided with the geoserver-geonode-ext war
    Villa
    @villa101101
    Screenshot 2021-05-28 at 11.17.26 AM.png
    @afabiani I have tried the conifg.yaml file you suggested and I am getting the same error.
    Villa
    @villa101101
    I am also using version 3.2.0 of Geonode
    I installed it on May 5th
    Villa
    @villa101101

    @afabiani I have tried the conifg.yaml file you suggested and I am getting the same error.

    If i understand the file structure properly, I believe it is a case where the configurations for those specific criteria I mentioned where not configured, unless its referred to as standard layout @afabiani

    Darko Nedic
    @Darkonyks
    Hi everyone. Does anyone knows how to change document permission on batch update? I will have more than 6000 documents, and I need to assign privileges to all documents to Registered members only. Is there a command to run in container or maybe a SQL update directly on table in PostGIS? Thank you in advance.
    Darko Nedic
    @Darkonyks
    image.png

    Hi everyone. Does anyone knows how to change document permission on batch update? I will have more than 6000 documents, and I need to assign privileges to all documents to Registered members only. Is there a command to run in container or maybe a SQL update directly on table in PostGIS? Thank you in advance.

    I find it in Django admin... Documents > Metadata Batch edit

    geotube
    @indeOWS

    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

    I am trying to do the same thing. We had a fix for issue 7306 GeoNode/geonode#7306. I ran the commands according to https://docs.geonode.org/en/master/install/basic/index.html#update-geonode-core-to-the-latest-commit, and still having the issues with OGC Metadata Reference. Git status tells that Your branch is up to date with 'origin/master'. But the OGC reference metadata still there even after running makemigrations, migrate, collectstatic and restarting all containers.

    Could someone point me any direction please?
    Edgar Vitus Mlowe
    @Mloweedgar
    Hey guys can anyone help me with REST Geonode API. I want to access non-public layers using geonode rest API. but whenever I try to use basic auth I get cors. may be I should first Ask, does Geonode(3.2.0) rest API support basic authentication? Iam relatively new to Geonode, I will appriciated your support folks!!
    MatKDA
    @MatKDA

    Hi, after updating geonode to 3.2.1 (from git/pre-3.2.0), I'm getting a lot of these errors when uploading a layer:

    [geoserver.notification] - channel is already closed due to channel error; protocol method: #method<channel.close>(reply-code=406, reply-text=PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'geonode' in vhost '/': received 'false' but current is 'true', class-id=40, method-id=10)
    com.rabbitmq.client.AlreadyClosedException: channel is already closed due to channel error; protocol method: #method<channel.close>(reply-code=406, reply-text=PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'geonode' in vhost '/': received 'false' but current is 'true', class-id=40, method-id=10)

    1 reply
    cavernousguess
    @cavernousguess
    I've been experiencing failing backups with Geonode-Project 3.2x with an "Unable to serialize database error". Any insight would be appreciated, here's my description of the problem:
    GeoNode/geonode#7928
    Pratyush Das
    @Pratyush1991
    @cavernousguess Hello, I also had the same problem. It was fixed after I added these imports to backup.py script. At the top add django_jsonfield_backport.features import extend_features
    from django.db import connection
    Then add extend_features(connection) to function handle:
    def handle(self, **options):
    extend_features(connection))
    Pratyush Das
    @Pratyush1991
    image.png
    image.png
    cavernousguess
    @cavernousguess
    @Pratyush1991 Wonderful, this worked! Thank you so much! Do you mind if I update my Github issue with your screen shots and tag you for credit? For anyone else having this issue working in Geonode-Project, I cloned Geonode Core 3.2.1 into my custom Geonode-Project directory, edited the backup.py file as per @Pratyush1991's direction, edited my Geonode-Project requirements.txt to install Geonode Core from the aforementioned directory (added -e ./geonode/ and commented out GeoNode==3.2.1), then removed the dependency_link pointing to the Geonode Core repository from setup.py. After rebuilding the Docker containers, uploading data, and testing the backup, it worked!
    Pratyush Das
    @Pratyush1991
    @cavernousguess Yeah sure you can use my screenshots. Actually this problem is related to Django rather than Geonode. Geonde 3.2.x branch uses Django 2.2.20 which causes this problem where as I have tested with Geonode master branch which uses Django 3.2.4 where this problem doesn't occur.
    Pedro Guimarães
    @tigreped
    Hi, everyone. I'm getting a 2021-08-17 13:36:05,658 WARN [geoserver.geofence] - No source IP address found 2021-08-17 13:36:06,108 WARN [geoserver.geofence] - Error retrieving source address with Spring Request: No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message, your code is probably running outside of DispatcherServlet: In this case, use RequestContextListener or RequestContextFilter to expose the current request. 2021-08-17 13:36:06,108 WARN [geoserver.geofence] - No source IP address found message in my /geoserver_data/data/logs/geoserver.log
    Anyone seen this?
    Pedro Guimarães
    @tigreped
    Dockerized production instance
    Pedro Guimarães
    @tigreped
    Hum, it seems my instance Allows insecure protocol: TLSv1.1. And my network admin allows only 1.2 and beyond. Is this an easy fix for dockerized version? :X
    Florian Hoedt
    @gannebamm
    You can tinker around with the nginx container and set those in there: https://github.com/GeoNode/geonode-project/blob/master/docker/nginx/nginx.https.available.conf.envsubst#L16
    Pedro Guimarães
    @tigreped
    Yes @gannebamm but even after restarting the containers (down/up) the TSL protocol didn't update. :/
    Pedro Guimarães
    @tigreped
    it seems like the ssl_ciphers for version 1.2 and 1.3 are very different. It appears one must use a conditional or work only with one of the options.
    Pedro Guimarães
    @tigreped
    left only the 1.2 , rebuilt and it is now back up , tks @gannebamm
    Florian Hoedt
    @gannebamm
    ok, good to know. Thanks for testing the approach and coming back with resutls @tigreped
    Pedro Guimarães
    @tigreped
    Well, I'm kind of battling the network folks. Checking things on the server with openssl s_client -connect 127.0.0.1:443 gives me
    issuer=C = US, O = Let's Encrypt, CN = R3
    
    ---
    No client certificate CA names sent
    Peer signing digest: SHA256
    Peer signature type: RSA-PSS
    Server Temp Key: X25519, 253 bits
    ---
    SSL handshake has read 4687 bytes and written 404 bytes
    Verification: OK
    ---
    New, TLSv1.2, Cipher is ECDHE-RSA-AES256-GCM-SHA384
    Server public key is 2048 bit
    Secure Renegotiation IS supported
    Compression: NONE
    Expansion: NONE
    No ALPN negotiated
    SSL-Session:
        Protocol  : TLSv1.2
        Cipher    : ECDHE-RSA-AES256-GCM-SHA384
    So I'm getting I'm managed to change it. But on a "https://ssltools.digicert.com/checker/views/checkInstallation.jsp" check I'm still getting
    Protocols enabled    
    
    TLS1.2,TLS1.1,TLS1.0
    Protocols not enabled    
    
    SSLv3,SSLv2
    Pedro Guimarães
    @tigreped
    And I need to REMOVE 1.0 and 1.1 support. Any ideaS?
    Pedro Guimarães
    @tigreped
    Maybe regenerating new certificate/keys?
    Pedro Guimarães
    @tigreped

    Well. Using

    server {
        listen              $HTTPS_PORT ssl default_server;
               ssl_protocols       TLSv1.3; 
               ssl_ciphers         HIGH:!aNULL:!MD5;
       ...
    }

    Then I rebuilt and restarted the docker. Seems to have done the job. Checked with openssl s_client -connect

    Florian Hoedt
    @gannebamm
    sometimes a rebuild is required. Even after years with docker I am not sure when :sweat_smile:
    Nice to see you worked that one out