Open MeijiRestored opened 1 day ago
I can confirm this issue. No more Reverse Geocoding after update to 0.15.4 I also use the photon api
What does everyone have set for their PHOTON_API_HOST
variable?
I know that I had to play around with variations such as:
hostname
https://hostname
http://hostname:2322
hostname:2322
https://hostname:2322
etc.
@Freika is this possibly because of using the new Geocoder library code https://github.com/Freika/dawarich/issues/300#issuecomment-2414606291 ?
It works great for me without https
using:
PHOTON_API_HOST=photon:2322
Maybe now only http works and not https?
@Freika I can confirm that while it now works to contact a photon server via http
, it seems unable to contact any photon server via https
regardless of how I set up the PHOTON_API_HOST
variable.
I think maybe the call to Geocoder needs to specify whether or not to use https now?
Changing it to this seems to make it work for HTTPS endpoints?
settings[:photon] = { use_https: true, host: PHOTON_API_HOST }
Although please test it yourself, I'm not 100% sure.
The options for Geocoder seem to be here: https://github.com/alexreisner/geocoder/blob/19f3cd1c717f5670aafaf690aa3b20955822ea88/lib/geocoder/configuration.rb#L53
The use_https
part didn't matter/work before when Geocoder only did https, but maybe it matters now?
If that is the fix, then there will need to be more code to either parse the PHOTON_API_HOST
variable for the protocol or have a 2nd variable for PHOTON_API_USE_HTTPS
.
I am having the same issue. I am trying to use Nominatim
with REVERSE_GEOCODING_ENABLED: true
but no luck. Does the fix mentioned above also help with Nominatim
users?
Describe the bug All reverse geocoding tasks fail with
Geocoder::ResponseParseError
.Version 0.15.4
Logs
Additional context Happens with both default geocoder (Nominatim) and self-hosted Photon instance (served over HTTPS from a remote server). It is happening only since the latest 0.15.4 update.
Here is an example query from my Photon instance in case it could be the issue (probably not since Nominatim fails as well):
/reverse?lon=2&lat=50