# Trying to enable pipelines on a project without success

**URL:** <https://discuss.circleci.com/t/trying-to-enable-pipelines-on-a-project-without-success/35421>\
**Category:** Build Environment\
**Created:** [April 12, 2020, 5:52pm UTC](https://discuss.circleci.com/t/trying-to-enable-pipelines-on-a-project-without-success/35421 "2020-04-12T17:52:26Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![amitz](https://avatars.discourse-cdn.com/v4/letter/a/90ced4/32.png) [@amitz](https://discuss.circleci.com/u/amitz)\
**Post date:** [April 12, 2020, 5:52pm UTC](https://discuss.circleci.com/t/trying-to-enable-pipelines-on-a-project-without-success/35421/1 "2020-04-12T17:52:26Z")

</div>

I’m trying to enable pipelines on a certain project. I can freely move the button to on or off, but pipelines don’t get enabled. The previous behavior I remember was that I could move the button to “on” but not back to off.

---

<div class="post-metadata">

**Author:** ![angelisa](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/angelisa/32/22776_2.png) [@angelisa](https://discuss.circleci.com/u/angelisa)\
**Post date:** [April 13, 2020, 8:33pm UTC](https://discuss.circleci.com/t/trying-to-enable-pipelines-on-a-project-without-success/35421/2 "2020-04-13T20:33:53Z")

</div>

Hi @amitz! Welcome to the CircleCI community! We are now enabling pipelines for all projects moving forward with our new UI on it’s way. Can you confirm you are using the `version: 2.1` in your configuration in order to run pipelines?

Reference: [https://circleci.com/docs/2.0/build-processing/](https://circleci.com/docs/2.0/build-processing/)

---

<div class="post-metadata">

**Author:** ![amitz](https://avatars.discourse-cdn.com/v4/letter/a/90ced4/32.png) [@amitz](https://discuss.circleci.com/u/amitz)\
**Post date:** [April 14, 2020, 12:48pm UTC](https://discuss.circleci.com/t/trying-to-enable-pipelines-on-a-project-without-success/35421/3 "2020-04-14T12:48:44Z")

</div>

Hi @angelisa ,  
Thanks for your response. It actually turned out that the pipeline was enabled correctly, but we couldn’t get to the pipelines page. The reason was that the project name had capital letters in its repo name in github. In the old UI it was listed under the lowercase version of the name and this worked. The new UI appears to be case sensitive, so when clicking the Pipelines link we got a Page Not Found error.

---

<div class="post-metadata">

**Author:** ![angelisa](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/angelisa/32/22776_2.png) [@angelisa](https://discuss.circleci.com/u/angelisa)\
**Post date:** [April 21, 2020, 4:05pm UTC](https://discuss.circleci.com/t/trying-to-enable-pipelines-on-a-project-without-success/35421/4 "2020-04-21T16:05:40Z")

</div>

Hi @amitz, that’s great to hear your issue is resolved. The VCS should be lowercase such as `github`. Thanks for calling that out, I’ll be sure to relay this experience with our teams internally. Happy building!

---

<div class="post-metadata">

**Author:** ![amitz](https://avatars.discourse-cdn.com/v4/letter/a/90ced4/32.png) [@amitz](https://discuss.circleci.com/u/amitz)\
**Post date:** [April 21, 2020, 4:33pm UTC](https://discuss.circleci.com/t/trying-to-enable-pipelines-on-a-project-without-success/35421/5 "2020-04-21T16:33:14Z")

</div>

Not the VCS. The issue is with the repo name.  
If the repo is called e.g. myservice, both UIs (old and new) will be have more or less the same

If the repo is called e.g. MyService, the behavior on each UI will be different - the old will work with the name myservice but the new requires exact case, i.e. MyService. However, the links generated by the UI itself don’t take this into account and send you from the old UI to an incorrect URL in the new UI and you receive an error message!
