Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: layer from wfs source via https doesn't work #4909

Open
1 task
josemvm opened this issue Oct 23, 2024 · 17 comments
Open
1 task

[Bug]: layer from wfs source via https doesn't work #4909

josemvm opened this issue Oct 23, 2024 · 17 comments

Comments

@josemvm
Copy link
Collaborator

josemvm commented Oct 23, 2024

What is the bug? (in English)

imagem

Steps to reproduce the issue

try to add a layer from wfs source

Versions, safeguards, check summary etc

Versions :

  • Lizmap Web Client : 3.8.3-pre.7994
  • Lizmap plugin : 4.4.2
  • QGIS Desktop : 3.34.11
  • QGIS Server : 3.34.11
  • Py-QGIS-Server : not used
  • QGIS Server plugin atlasprint : 3.4.1
  • QGIS Server plugin lizmap_server : 2.11.2
  • QGIS Server plugin wfsOutputExtension : 1.8.2
List of Lizmap Web Client modules :
* multiauth : 1.2.2
List of safeguards :
* Mode : normal * Allow parent folder : no * Prevent other drive : no * Prevent PG service : no * Prevent PG Auth DB : no * Force PG user&pass : no * Prevent ECW : no

Check Lizmap plugin

  • I have done the step just before in the Lizmap QGIS desktop plugin before opening this ticket. Otherwise, my ticket is not considered valid and might get closed.

Operating system

Ubuntu 22.04

Browsers

Firefox

Browsers version

131.0.3

Relevant log output

qgis server logs:

13:24:53 WARNING Server[225942]: Error parsing post data as XML: at line 1, column 1: error occurred while parsing element. Assuming urlencoded query string sent in the post body.

13:24:53 INFO WfsOutputExtension[225942]: requestReady ran in 0.0s
@Gustry
Copy link
Member

Gustry commented Oct 23, 2024

@josemvm I do not replicate the issue, it works for me.

I'm adding a WFS layer, using https in #4910

Is your WFS layer quick enough ? It depends on your QGIS Server settings.
Is your layer visible in the map ?

@josemvm
Copy link
Collaborator Author

josemvm commented Oct 23, 2024

@Gustry

Is your WFS layer quick enough ?

not very very quickly but it visible in the map on qgis desktop (not in lwc) and i can work as well with it

It depends on your QGIS Server settings

what kind of settings in qgis server

i will test #4910 and if you want to test my layer I can provide the url as it is open data

@Gustry
Copy link
Member

Gustry commented Oct 23, 2024

There is nothing to test in #4910. It was just to add test data.

We got sometimes the issue about the SSL handshake being written in a SQLite from QGIS, where QGIS server didn't get write permissions on this file.
You should check QGIS Server logs if there is kind of data.
What is the error in LWC about this blank tiles ? or logs in QGIS server during this request ?

@josemvm
Copy link
Collaborator Author

josemvm commented Oct 30, 2024

We got sometimes the issue about the SSL handshake being written in a SQLite from QGIS, where QGIS server didn't get write permissions on this file.

22:03:56 WARNING WFS[1425]: Cannot create temporary SpatiaLite cache.: Cannot copy file to //.local/share/QGIS/QGIS3/profiles/default/cache/wfsprovider/pid_1425/cache_4.sqlite:

@josemvm
Copy link
Collaborator Author

josemvm commented Nov 12, 2024

the wfs layer is visible only at 1:250000, if i zoom to a major scale the layer disappears!
also the attribute table doesn't appear filled in, only the field names are visible

@rldhont
Copy link
Collaborator

rldhont commented Nov 13, 2024

@josemvm I think your QGIS Server needs the environmental variable to define the home directory

@josemvm
Copy link
Collaborator Author

josemvm commented Nov 13, 2024

@rldhont thanks for your answer

now i' ve the environmental variable

FcgidInitialEnv QGIS_OPTIONS_PATH "/home/qgis/.local/share/QGIS/QGIS3/profiles/default"

the structure folders:

/home/qgis/.local/share/QGIS/QGIS3/profiles/default

and the error remains:

WARNING WFS[4667]: Cannot create temporary SpatiaLite cache.: Cannot copy file to //.local/share/QGIS/QGIS3/profiles/default/cache/wfsprovider/pid_4667/cache_2.sqlite:

@Gustry
Copy link
Member

Gustry commented Nov 13, 2024

Cannot copy file to //.local/share/

I doubt that your process can write to this directory...

@josemvm
Copy link
Collaborator Author

josemvm commented Nov 13, 2024

I doubt that your process can write to this directory...

@Gustry i don't know why!
owner: root, group: www-data
permissions: all (777)

@Gustry
Copy link
Member

Gustry commented Nov 13, 2024

On which directory did you check this owner and group ? Look at the path in my message.

@josemvm
Copy link
Collaborator Author

josemvm commented Nov 13, 2024

On which directory did you check this owner and group ?

from qgis/.local/share/QGIS/QGIS3/profiles/default in /home/ to the end

@josemvm
Copy link
Collaborator Author

josemvm commented Nov 13, 2024

@Gustry please where do you point me with

Look at the path in my message

(?)

@Gustry
Copy link
Member

Gustry commented Nov 13, 2024

Cannot copy file to //.local/share/QGIS/QGIS3

It's trying to write in //.local.

@josemvm
Copy link
Collaborator Author

josemvm commented Nov 13, 2024

i think that one slash (/) = double (//) slash...
this mean that the process needs to write at root file system /.local ?

@josemvm
Copy link
Collaborator Author

josemvm commented Nov 13, 2024

ok! so the qgis server ignores the environmental variable QGIS_OPTIONS_PATH ... (?)
thank you so much @Gustry :-)

@Gustry
Copy link
Member

Gustry commented Nov 13, 2024

ok! so the qgis server ignores the environmental variable QGIS_OPTIONS_PATH ... (?)

No, it works, but then it's the value of QGIS_CUSTOM_CONFIG_PATH which overrides the other one.

Try to set both with the same value.

thank you so much @Gustry :-)

That's why I pointing you to read your own logs ;-)

@Gustry
Copy link
Member

Gustry commented Nov 13, 2024

There is also QGIS_AUTH_DB_DIR_PATH, and HOME.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants