# Jupyterlab (Kubernetes) + Prodigy: "ERROR: Can't fetch project. Make sure the server is running correctly."

**URL:** <https://support.prodi.gy/t/jupyterlab-kubernetes-prodigy-error-cant-fetch-project-make-sure-the-server-is-running-correctly/2606>\
**Category:** Uncategorized\
**Tags:** usage, solved, docker, jupyter, server\
**Created:** [February 28, 2020, 8:27pm UTC](https://support.prodi.gy/t/jupyterlab-kubernetes-prodigy-error-cant-fetch-project-make-sure-the-server-is-running-correctly/2606 "2020-02-28T20:27:34Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\
**Post date:** [March 3, 2020, 10:16am UTC](https://support.prodi.gy/t/jupyterlab-kubernetes-prodigy-error-cant-fetch-project-make-sure-the-server-is-running-correctly/2606/5 "2020-03-03T10:16:48Z")

</div>

Yes, the path prefix is the problem here. We currently don't have a satisfying solution for modifying the paths, so subdomain-based routing is the easiest solution.

@honnibal explained this in more detail here:

> [@Feature request: URL prefixing](https://support.prodi.gy/t/feature-request-url-prefixing/1898/2):
>
> We actually provide the source for the server app within Prodigy, so if worse comes to worst you could make the changes you need to the app.py -- have a look within your Prodigy installation. Unfortunately, there's no easy way to make the front-end aware of the prefix without recompiling the app. I've definitely struggled through this before as well, so I feel the pain. What I've ended up concluding is that path-based routing is just more trouble than it's worth, and you're much better off just…

---

_[View the full topic](https://support.prodi.gy/t/jupyterlab-kubernetes-prodigy-error-cant-fetch-project-make-sure-the-server-is-running-correctly/2606)._