OSM plugin is no longer available?

[Samuel Ives]

last year I used the osm plugin without problems, however this time I always come across these errors, other plugins like esri and mapbox are working normally

[raven-worx]

@Samuel-Ives
seeing those warnings in the background you should provide OpenSSL libs to your application (or at least in the PATH variable)
Probably osm switched to https:// urls

[Samuel Ives]

Just to ensure I put the OpenSSL dlls together with the application, but continued, I added network in my .pro file but it did not work, I think this is some problem with the plugin because the page does not warn about having to acquire the OpenSSL libraries

[raven-worx]

@Samuel-Ives
so the ssl errors are gone now?

Regarding the second warning about the disabled tile server:
https://blog.qt.io/blog/2017/03/09/provisioning-openstreetmap-providers-in-qtlocation/

[Samuel Ives]

Plugin{
        id: osm
        name: "osm"
        PluginParameter{name: "osm.useragent"; value: "TGAdmin"}
        PluginParameter{name: "osm.mapping.custom.host"; value: "https://tile.openstreetmap.org"}
        PluginParameter{name: "osm.mapping.providersrepository.disabled"; value: true}
    }

Solved, just to ensure I also setted the tile host as OSM itself as indicated here:
https://wiki.openstreetmap.org/wiki/Domain_names