Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

front end white screen #356

Open
rds11080 opened this issue Nov 22, 2022 · 6 comments
Open

front end white screen #356

rds11080 opened this issue Nov 22, 2022 · 6 comments

Comments

@rds11080
Copy link

hi, i follow the instruction and setup front end back end but i got white screen on front end(map white screen, search text white screen, direction text white screen but i can click on location)
the debug mode screen work
do i miss any library?

@frodrigo
Copy link
Member

frodrigo commented Nov 22, 2022 via email

@rds11080
Copy link
Author

rds11080 commented Nov 23, 2022

I do not know what you call the debug screen. Can you check the console of the browser key F12. Le mar. 22 nov. 2022, 22:38, rds11080 @.> a écrit :

hi, i follow the instruction and setup front end back end but i got white screen on front end(map white screen, search text white screen, direction text white screen but i can click on location) the debug mode screen work do i miss any library? — Reply to this email directly, view it on GitHub <#356>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANT5DRYHGCTTXDUXZZDQYTWJU4NNANCNFSM6AAAAAASII5Q64 . You are receiving this because you are subscribed to this thread.Message ID: @.
>

*debug screen is debug map
*i check F12 and cant find livereload.js (ip is wrong, how can i change ip, im using docker install)
Failed to load http://172.17.0.2:35729/livereload.js?snipver=1
when i CTRL+U to view source of file, it was
<script type="text/javascript" src="[//172.17.0.2:35729/livereload.js?snipver=1](http://172.17.0.2:35729/livereload.js?snipver=1)" async="" defer="">
i think it was missing "http" in the src

@rooton
Copy link

rooton commented Dec 27, 2022

The same issue.

Error in console:
GET https://api.mapbox.com/v4/mapbox.streets/13/2344/[email protected]?access_token=pk.eyJ1IjoibXNsZWUiLCJhIjoiclpiTWV5SSJ9.P_h8r37vD8jpIH1A6i1VRg 410 (Gone)

@JohnAnthony
Copy link

I had the same issue. It looks like those mapbox files actually are gone. Choosing to use the openstreetmap.org or openstreetmap.de.org files (menu at the bottom-left) gives a visible map.

@1ec5
Copy link
Member

1ec5 commented Jun 14, 2023

Mapbox deprecated the Maps API v4 (raster tile) endpoint years ago; at that point, they were no longer updating the tiles to reflect the latest OSM data. Looks like they finally got rid of it.

/ref Leaflet/Leaflet#7173

@asiudoisjdfo
Copy link

When running OSRM-frontend with the local OSRM-backend, it still yields a blank page (no tiles served?). The routing engine works.

This is by using the official instructions on https://hub.docker.com/r/osrm/osrm-backend/ .

How can we use the OSRM-frontend along with the backend? it seems like a this bug...? sorry if it is not correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants