|
There are some tile endpoints that are simply never loading data. For example, this never loads an image: https://b.tile.osm.org/5/7/12.png It's causing our maps feature to be very buggy and sometimes not work at all. What is going on? |
|
I don't think that the link is the problem. We use the full link, and also have performance issues. "https://b.tile.openstreetmap.org/19/271514/171461.png" Screenshot I now see what's the problem of onenine90 is. And I've opened my own question to not disturb this one. It was a coincidence that we both saw gray areas at the same time, so it seems.
(11 Feb '20, 12:09)
Foeketijn
|
|
You need to use the correct domain/subdomain: Also, drop the attitude. Asking "But why should we have to do this?" in an entitled fashion is entirely the wrong attitude to take to a volunteer-run service that is provided free of charge, funded mostly from donations. If you want an SLA, pay a company that provides one. Sorry to offend you Richard. Thanks for the answer. Can you address the other user's problem as well? Thanks!
(10 Feb '20, 16:45)
onenine90
I appreciate this community and the open source software that is provided, and I understand that there should be less expectations and more appreciation in open source. Sorry to come off rude.
(10 Feb '20, 16:50)
onenine90
|
|
Hmmm. It looks like something changed with DNS. Did someone at OpenStreetMap recently change a server IP address or something? Because when I change my DNS server to 8.8.8.8 (google's public name server), things seem to work better. But why should we have to do this? See screenshot of DNS propagation failures: https://www.dropbox.com/s/n6lupli8c01ar0v/Screenshot%202020-02-10%2009.35.48.png?dl=0 It looks like the same issue as https://help.openstreetmap.org/questions/72968/fetching-maps-that-are-on-my-multiple-sites-have-stopped-working , and the same advice applies - use the full site name.
(10 Feb '20, 15:41)
SomeoneElse ♦
|
