# Badgr server installation giving issues

**URL:** <https://discuss.openedx.org/t/badgr-server-installation-giving-issues/518>\
**Category:** Site Operations Help\
**Created:** [September 18, 2019, 11:52am UTC](https://discuss.openedx.org/t/badgr-server-installation-giving-issues/518 "2019-09-18T11:52:01Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![vrios](https://avatars.discourse-cdn.com/v4/letter/v/e495f1/32.png) [@vrios](https://discuss.openedx.org/u/vrios)\
**Post date:** [December 11, 2019, 9:19am UTC](https://discuss.openedx.org/t/badgr-server-installation-giving-issues/518/6 "2019-12-11T09:19:45Z")

</div>

We were running openedx on bitnami’s installation.

We wound up integrating badgr server with bitnami’s edx with a couple of modifications on badgr server’s code.

The fixes are described here. [Error updating user preferences. Credentials not provided?](https://discuss.openedx.org/t/error-updating-user-preferences-credentials-not-provided/643/3)

I forgot I had two threads on the same issue.

As badgr server is its own django application it should work with any edx install.

My fix merely makes slugs editable on badgr server through its django app.

You can see what badges are being requested by edx through trial and error and make the slugs match or give every badge the openedx\_\_course issuing component and make the slug openedx\_\_coursebadgeslug on badgr server side(ie badge1 on edx with issuing component openedx\_\_coursebadge1).

If badging functionation changes wildly on edx beyond hawthorn in terms of how the slug works or how edx requests the badges to badgr server, bitnami was at hawthorn, then I can’t be of any help.

---

_[View the full topic](https://discuss.openedx.org/t/badgr-server-installation-giving-issues/518)._