Hi all,
To fix this issue, you have to add HOME environmental variable to a
directory in which the directory .qgis2 is writable for the user used by
QGIS Server, with Apache2, it's www-data.
For exemple, do these commands:
```
mkdir /srv/qgis/.qgis2
chown www-data:www-data /srv/qgis/.qgis2
chmod 774 /srv/qgis/.qgis2
```
And add this in your apache virtual host:
```
FcgidInitialEnv HOME "/srv/qgis"
```
The documentation probably needs to be updated.
Regards,
René-Luc
Le 14/05/2018 à 17:49, Alessandro Pasotti a écrit :
And this:
https://issues.qgis.org/issues/17951
and this too:
https://issues.qgis.org/issues/16462
On Mon, May 14, 2018 at 4:58 PM, Régis Haubourg
<regis.haubo...@gmail.com <mailto:regis.haubo...@gmail.com>> wrote:
Hi Anne,
did you test QGIS 3.0 also?
Could you create an issue in issue.qgis.org
<http://issue.qgis.org> tracker?
I found that one, that seemed related
https://issues.qgis.org/issues/18634
<https://issues.qgis.org/issues/18634>
Regards,
Régis
2018-05-14 16:25 GMT+02:00 Anne Blankert <anne.blank...@geodan.nl
<mailto:anne.blank...@geodan.nl>>:
Hello List,
This question was already asked in Jan 2017, but no solution
was posted.
http://osgeo-org.1560.x6.nabble.com/QGIS-Server-SSL-handshake-failed-for-cascading-WMS-td5305094.html
<http://osgeo-org.1560.x6.nabble.com/QGIS-Server-SSL-handshake-failed-for-cascading-WMS-td5305094.html>
The problem: if QGIS uses an HTTPS (SSL) WMS service, the WMS
works nicely in QGIS desktop. However, if you use the same
.qgs project file on QGIS Server, all requests to the HTTPS
(SSL) WMS server result in an SSL handshake error.
This (still) happens on:
Ubuntu 16.04
QGIS server 2.18
An example WMS https server showing the problem is:
https://geodata.nationaalgeoregister.nl/bag/ows
<https://geodata.nationaalgeoregister.nl/bag/ows>
A workaround could be to use the HTTP version of the WMS
instead of the HTTPS version. However, the capabilities of
many HTTP services advertise the HTTPS version for the GETMAP,
GETFEATUREINFO and GETLEGENDGRAPHIC endpoints.
The SSL problem also arises when trying to use WFS services
over HTTPS from QGIS Server.
Is this a known problem? Is there a workaround? Should I file
a bug report?
Thanks,
Anne
_______________________________________________
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
<mailto:QGIS-Developer@lists.osgeo.org>
List info:
https://lists.osgeo.org/mailman/listinfo/qgis-developer
<https://lists.osgeo.org/mailman/listinfo/qgis-developer>
Unsubscribe:
https://lists.osgeo.org/mailman/listinfo/qgis-developer
<https://lists.osgeo.org/mailman/listinfo/qgis-developer>
_______________________________________________
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org <mailto:QGIS-Developer@lists.osgeo.org>
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
<https://lists.osgeo.org/mailman/listinfo/qgis-developer>
Unsubscribe:
https://lists.osgeo.org/mailman/listinfo/qgis-developer
<https://lists.osgeo.org/mailman/listinfo/qgis-developer>
--
Alessandro Pasotti
w3: www.itopen.it <http://www.itopen.it>
_______________________________________________
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
