Open jkariscodes opened 2 years ago
Hi guys, I have same problem, if I change the images for Jenkins the error appers.
java.io.IOException: Failed to start a listener: winstone.HttpsConnectorFactory, the application just say: winstone.WinstoneException: Please set --httpsKeyStore
It is totally normal to have gsconf4my_geonode exiting with code 0, but it could case issues if you are using bind mounts instead of volumes: #264.
Look at geonode logs and at the browser console logs.
Jenkins can be disabled and is not required to upload layers.
I have the same issue. I followed the installation routine from the documentation and from the repository. Once I used the script create-envfile.py and once I configured the .env by myself. It always resulted in the error that I can't upload geodata to Geonode.
When I tried to create geodata within Geonode I get the error message, that the authentication credentials for Geoserver are not working:
Insepecting the scene in Geoserver I noticed, that the default password was still active. Changed it to what is used in .env. The effect: I still get the error on the left panel and a never ending process on the right one (see screenshot: ). But the data was transfered to Geoserver successfully this time. So half done in total.
P.S.: I was testing with Xubuntu 20.04 in a VM
So, now 4 days later. I did not change anything else than what I described above. Now, the geodata was loaded into Geonode. The same data I tried it with last time. Same with creating geodata inside Geonode.
I had this issue recently and after changing GeoServer passwod to 'geoserver' the layers started to upload to a certain point. When the layer is bigger than 150MB it keeps giving me this error.
Hi, I have installed GeoNode 4.0 geonode-project via docker and whenever I try uploading shapefiles from different sources like GADM or NaturalEarth I get an error stating that upload process failed and that I should check the validity of the file (as shown below). This is what I have in celery logs In addition to which one of the containers is not running as shown below
This has been tested in both Ubuntu in WSL and Ubuntu OS.