Open answerquest opened 6 years ago
Thanks for reporting, @answerquest
I guess tasks.openstreetmap.in would have to get an SSL certificate to resolve this.
From what I remember, when we last setup SSL for the site using letsencrypt
, we got https working, but there were a number of things on the Tasking Manager that broke with https
, and we had to roll back. I'm a bit worried that this (older) version of Tasking Manager we are running does not quite work correctly over HTTPS. And moving to the new Tasking Manager is potentially a bigger lift than we're able to do right now.
I see two options:
We can definitely try setting up SSL again - configuring the SSL itself was not much of an issue, IIRC, but I don't think the bugs on Tasking Manager when running under https
have been resolved.
If that doesn't work, we should look at upgrading to the new TM3 code-base at some point. If someone would have the bandwidth to look into it, I'm happy to try and support, but I don't think I have the bandwidth to take this on myself.
@geohacker please correct me if my memory is wrong - but I do remember setting up SSL for this, and then having to roll-back because of application-level errors with https
. Do you know if they've been solved upstream?
@answerquest thank you for the ticket.
@batpad yes, I do remember us setting up SSL and then running into problems with application requests. Looks like there's been a bunch of work to make TM2 work on https https://github.com/hotosm/osm-tasking-manager2/pulls?q=is%3Apr+is%3Aclosed - we could try to pull the latest code and setup SSL.
But I agree that we should just find some time and move to TM3.
We've gotten project creating permissions on tasks.teachosm.org at our end, are using that to do activities this month, so no time pressure on this.
@geohacker @batpad
Console log in OSM editor tab upon launching from tasking manager:
I guess tasks.openstreetmap.in would have to get an SSL certificate to resolve this. Craig had mentioned in email that this issue seems to have come up with recent updates of web browsers, making the https requirement stricter.