depends if you are using chrome or not, seems like a mixed content error(tm is http and osm is https) chrome now blocks mixed content.
Last time I tried to enable HTTPS on TM2 it broke syncing with JOSM as it would try to open up a self signed cert(not accepted by default) on port 8112 with no errors or feedback. So I either brake ID boundaries or JOSM(unless a user knows how to accept cert) On Fri, Mar 23, 2018, 11:01 AM Jonathan Brown, <jonab...@gmail.com> wrote: > It would be good to have a screen shot demonstrating these kinds of > errors. We could use these screen shots of good and bad examples to > demonstrate good practices. James, will the TM2 issue affect our March 29 > mapathon? > > > > Jonathan > > > _______________________________________________ > Talk-ca mailing list > Talk-ca@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-ca >
_______________________________________________ Talk-ca mailing list Talk-ca@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-ca
