GraphHopper stuck at "Starting Server" on Windows 11 (WSL) – need help!

Open Source Routing Engine
1

Hi everyone,

I’m an architecture student trying to use GraphHopper for urban analysis. I’m running it on Windows 11 using WSL, with 16GB of RAM. I’m working with the Zverik 15-minute model from GitHub.

The problem: when I run GraphHopper, the logs stop at something like:

Started Server@xxxx{STARTING}[10.0.xx,sto=30000] @xxxxms

…and it just… stays there. I’ve left it for more than 30 minutes, and nothing happens. No errors, no progress, just stuck.

I’ve tried:

  • Different RAM settings (-Xmx6G)

  • Checking ports (nothing else running on 8989)

  • Using both GraphHopper 10.0 and 11.0

I don’t know if it’s a WSL issue, a config issue, or something else entirely. I even asked ChatGPT for help, because English isn’t my first language… so if my wording is weird, blame AI

Has anyone experienced this “stuck at STARTING” problem? Any advice would be hugely appreciated.

Thanks!

2

This is most likely a WSL networking issue. Why don’t you run graphhopper natively under Windows?

3

If you run the server command it will wait at this line (which indicates “success”) and accept routing requests either via API or /maps. If you just wanted to create the graph-gh folder then use the import command.

If you still have problems, please show the command and config.yml you used and the entire log output.