# Installation galaxy-ng not working

**URL:** <https://forum.ansible.com/t/installation-galaxy-ng-not-working/4958>\
**Category:** Get Help\
**Tags:** galaxy-ng\
**Created:** [April 15, 2024, 5:29pm UTC](https://forum.ansible.com/t/installation-galaxy-ng-not-working/4958 "2024-04-15T17:29:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![malins](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/malins/32/2892_2.png) [@malins](https://forum.ansible.com/u/malins)\
**Post date:** [April 15, 2024, 5:29pm UTC](https://forum.ansible.com/t/installation-galaxy-ng-not-working/4958/1 "2024-04-15T17:29:35Z")

</div>

Hello,

I’m trying to install galaxy-ng following the guide in the documentation ([Installation - Galaxy NG](https://ansible.readthedocs.io/projects/galaxy-ng/en/latest/usage_guide/installation/)).

When trying to access the UI, I cannot login. I can see that the following API requests lead to 404 errors.

http ://myhost:8080/api/galaxy/\_ui/v1/feature-flags/  
http ://myhost:8080/api/galaxy/\_ui/v1/me/  
http ://myhost:8080/api/galaxy/\_ui/v1/settings/

The only adaption to the configuration file (pulp\_settings.env) was replacement of “localhost” with my own FQDN.

Any help appreciated. Is there an alternative way to install ansible-ng on my own server?

Thank you,  
Manuel

---

<div class="post-metadata">

**Author:** ![Denney-tech](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/denney-tech/32/1556_2.png) [@Denney-tech](https://forum.ansible.com/u/Denney-tech)\
**Post date:** [April 15, 2024, 6:06pm UTC](https://forum.ansible.com/t/installation-galaxy-ng-not-working/4958/2 "2024-04-15T18:06:39Z")

</div>

> Any setting containing “localhost:8080” will be environment specific. Whenever the system is spun up, the backend expects incoming and redirected requests to go to that address. This example uses “localhost:8080” because we will use docker in the next step to bind the underlying host’s port 8080 to the container’s port 80.

> The container uses the s6 init system to spin up postgresql, gunicorn, nginx and various pulp services all in the same container. Once migrations have finished and the log entries settle and end with a “New worker XXXXXX discovered”, the system is ready to use.

I don’t think you can change `localhost:8080` and use the given docker deployment as is (you might need to set up a reverse proxy, for .e.g). If you want to do a standalone deployment, you might be better off following the instructions here:

> **[End User Installation](https://github.com/ansible/galaxy_ng/wiki/End-User-Installation)**
>
> Ansible Galaxy Server - Issues on https://forum.ansible.com Docs on https://galaxy-ng.readthedocs.io/ - ansible/galaxy\_ng

Edit: You might not have a UI at all either, since that’s a separate image.