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
{{ message }}
This repository has been archived by the owner on Dec 1, 2020. It is now read-only.
Hi
When using quickfinder to search for an address i receive the two following error messages:
QuickFinder: An unknown error related to the remote content was detected
QuickFinder: The Network Access API cannot honor the request because the protocol is not known
I have never had this issue before and the plugin was working earlier in the day. No settings were changed before this began happening. I updated the plugin and it still gives the same errors.
why is this happening?
Thanks
The text was updated successfully, but these errors were encountered:
I seem to have fixed my problem although I am not entirely sure why it worked.
I imported a openstreetmap layer into my project (which I have never needed for this plugin to work). osm now returns results
Hi,
I encounter the same problem, and I have an additional element of answer.
I have the same error messages as you, but for the results to appear, just pass the projection in WGS 84 / Pseudo Mercator (ESPG 3857).
So the problem is with the projection of the project.
Nevertheless, as we work in a local projection, this plugin would be very useful: does somebody have a solution?
(I specify that if the results of searches appear, the error messages continue also to appear)
Thanks !
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi
When using quickfinder to search for an address i receive the two following error messages:
QuickFinder: An unknown error related to the remote content was detected
QuickFinder: The Network Access API cannot honor the request because the protocol is not known
I have never had this issue before and the plugin was working earlier in the day. No settings were changed before this began happening. I updated the plugin and it still gives the same errors.
why is this happening?
Thanks
The text was updated successfully, but these errors were encountered: