Hi everyone,
I have the following problem with
• QGIS LTR, Windows 11 Pro
• Lizmap plugin 4.5.9 / LWC 3.9.6, 4 configured servers
Every time the Lizmap plugin starts, two consistent delays occur (visible in the QGIS log):
20:37:58 Saving server metadata from network : 2 - my-server.example.com
20:38:06 Version checker : NO QPM, nothing we can do now… ← ~8 sec
20:38:33 Loading all layouts from the QGIS project ← ~27 sec
Total delay before the plugin is usable: ~35 seconds. All servers and external URLs (versions.json, analytics.3liz.com) respond instantly when tested directly. IPv6 is disabled both on the adapter and via registry.
Questions
- What causes the delay after Version checker : NO QPM? Is this a known issue when QPM is unavailable?
- What network request causes the ~27 sec wait before Loading all layouts?
- Is there a way to reduce or configure these timeouts?
Regards
Tested also with the latest alpha version 5.0.0-alpha.3:
The delays are identical and version-independent. With the alpha, QPM is found and the version checker completes successfully (running a higher version than on ``plugins.qgis.org), but the two timeouts remain unchanged (~17 sec after version check, ~35 sec before loading layouts). This confirms the issue is not related to the NO QPM message itself.
Between Version checker : NO QPM, nothing we can do now and Loading all layouts from the QGIS project, the plugin loads the lizmap config…
The file is large and parsing is slow or access to files is very slow and the disk may be damaged.
Hardware: AMD Ryzen 7 9700X, Windows 11 Pro, SSD – no disk performance issues expected.
File sizes:
Both files are local on SSD. Reading 137 KB should take milliseconds, not 40+ seconds. So slow file access seems unlikely as the root cause.
After further investigation, we suspect this is a Windows 11 25H2 network issue rather than a Lizmap-specific problem. The delays also affect general QGIS network requests (not just the Lizmap plugin), as shown by these warnings appearing in the QGIS log: `Network request https://forchheim.webgis.biz/index.php/view/app/metadata took too long`
This occurs with both the OSGeo4W and standalone QGIS installations. The same setup works without any delays on a Windows 11 24H2 machine. KB5077181 is installed but did not resolve the issue.
Has anyone else observed similar behavior on Windows 11 25H2?
Just another thought - have u tried it with a fresh qgis user profile?
I had already tried that, and now I’m trying it again.
Created a new profile, installed only the Lizmap plugin (4.5.9), and defined a server.
Subsequent test:
12:46:32 Plugin starting in the initGui
12:46:49 Version checker : running a higher version… → 17 seconds
12:49:13 Webdav is not installed
12:49:14 Version checker : running a higher version…
→ another 21 seconds
12:49:35 Loading all layouts…
Unfortunately, no improvement—the delays are identical to before. The new profile didn’t help, which continues to suggest the Windows 25H2 issue.
After a long, long search:
Solution found: The delays were caused by a mapped network drive (Z:) pointing to a PC that is rarely powered on. QGIS apparently tries to access all mapped network drives when opening the Lizmap dialog, and Windows waits for the timeout (~20 seconds) before giving up on unreachable drives.
Fix: Disconnect the unavailable mapped network drive. This immediately resolved the periodic 22-second delays we were experiencing.
If you have mapped network drives that are not always available, this could be the cause of your Lizmap startup delays on Windows.
Oh noo, now i feel terribly Bad - I had this problem a couple of years back, and also had tried alot(!) to find the culprit - I posted my solution back then as answer on gis.stackexchange
Sorry for not coming up with that idea earlier, and nice that you finally found a solution 
Yeah, now that I think about it, it sounds familiar to me too.
I think the QGIS-DE Association once funded an improvement to QGIS regarding these network drives. But that was aimed at larger organizations. I’ll have to check with my colleagues in the association. Maybe there’s room for further improvement there.
Because you really never think of it, especially since it only affected the Lizmap plugin in this case.