You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We set up a GeoNode Core 4.1.0 on a VM using docker. The system worked well when tested on localhost and also when deployed accessible from the institutes network only. When proxied through HAProxy GeoNode and its components (Django, GeoServer, Postgres-DB) can be reached from the outside successfully but we ran into the following issues:
uploading even small resources as datasets takes unreasonable long
updating metadata of these datasets results in 504 error
register remote services results in 504 error
creating an dataset results in 504 error
Uploading resources as documents worked just fine. Editing metadata also worked here. Same applies to maps, geostories and dashboards.
The presumable fix:
After a while we figured what might be the problem here and the following .env settings did the trick:
When keeping GEONODE_LB_HOST entries empty GeoServer Proxy Base URL is set to http://geonode:80 by the system itself. GeoNode then already works behind the HAProxy but the OGC-Services provided by GeoServer are not reachable from the outside. We fixed this by logging into GeoServer and setting the Proxy Base URL entry empty...
I understand that GeoNode is supposed to run on its own. SSL/TLS encryption is provied internally by Letsencrypt.
However, when deploying GeoNode behind a HAProxy encryption is already taken care of.
Is there an 'official' way / recommendation to set up the system using a proxy?
Hi GeoNode-Team,
We set up a GeoNode Core 4.1.0 on a VM using docker. The system worked well when tested on localhost and also when deployed accessible from the institutes network only. When proxied through HAProxy GeoNode and its components (Django, GeoServer, Postgres-DB) can be reached from the outside successfully but we ran into the following issues:
Uploading resources as documents worked just fine. Editing metadata also worked here. Same applies to maps, geostories and dashboards.
The presumable fix:
After a while we figured what might be the problem here and the following .env settings did the trick:
When keeping GEONODE_LB_HOST entries empty GeoServer Proxy Base URL is set to http://geonode:80 by the system itself. GeoNode then already works behind the HAProxy but the OGC-Services provided by GeoServer are not reachable from the outside. We fixed this by logging into GeoServer and setting the Proxy Base URL entry empty...
I understand that GeoNode is supposed to run on its own. SSL/TLS encryption is provied internally by Letsencrypt.
However, when deploying GeoNode behind a HAProxy encryption is already taken care of.
Is there an 'official' way / recommendation to set up the system using a proxy?
Thanks!
Specifications
timeout http-request 10s
timeout queue 1m
timeout connect 10s
timeout client 1m
timeout server 1m
timeout http-keep-alive 10s
timeout check 10s
The text was updated successfully, but these errors were encountered: