# Allow HPC-Toolset Demo external access

**URL:** <https://discourse.openondemand.org/t/allow-hpc-toolset-demo-external-access/2364>\
**Category:** Get Help\
**Tags:** question\
**Created:** [November 9, 2022, 7:46pm UTC](https://discourse.openondemand.org/t/allow-hpc-toolset-demo-external-access/2364 "2022-11-09T19:46:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![SilasMarner](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/silasmarner/32/1372_2.png) [@SilasMarner](https://discourse.openondemand.org/u/SilasMarner)\
**Post date:** [November 9, 2022, 7:46pm UTC](https://discourse.openondemand.org/t/allow-hpc-toolset-demo-external-access/2364/1 "2022-11-09T19:46:07Z")

</div>

Hello we are looking into OpenOndemand and trying to look at the nice hpc-toolset demo pulled from  
[https://github.com/ubccr/hpc-toolset-tutorial/blob/master](https://github.com/ubccr/hpc-toolset-tutorial/blob/master)

I have an internal OpenStack setup where I have my virtual machine and pulled down the containers and everything is working with that regard.

The virtual machine has no browser or X or remote forwarding to launch and interact it as if we were logged in to it directly so we would like to access the demo ‘remotely’. I have firewall rules which allow me to access the cloudfront interface on 1.2.3.4:2443 as well as the other ports.

When I am trying to get to the actual ondemand interface it keeps redirecting to localhost:3443. Is there a way to get the demo to all listen and use 1.2.3.4 so we can test it out and see how the pieces connect together.

Thank you.

---

<div class="post-metadata">

**Author:** ![jeff.ohrstrom](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/jeff.ohrstrom/32/136_2.png) [@jeff.ohrstrom](https://discourse.openondemand.org/u/jeff.ohrstrom)\
**Post date:** [November 10, 2022, 5:41pm UTC](https://discourse.openondemand.org/t/allow-hpc-toolset-demo-external-access/2364/2 "2022-11-10T17:41:26Z")

</div>

Hi and welcome! I’m not sure if this is possible out of the box. Here are some hacks you’d likely need to do:

1. use the host network for the ood container. This will ensure that the `hostname` apache has to recognize is valid.  
[Compose file version 3 reference | Docker Documentation](https://docs.docker.com/compose/compose-file/compose-file-v3/#network_mode)
2. Create and mount a file `/etc/ood/config/ood_portal.yml` that has the `servername` attribute that you’d like (i.e., not `localhost`).

And that may actually do it.

That said - if you have easy VM technology (like OpenStack) you may be better off just installing the `.rpm` (or `.deb`) and installing on the host directly.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex015/uploads/osc/original/2X/b/bae70bd0ed39a3ae769c2108155f4cb3e9da8385.png) [@system](https://discourse.openondemand.org/u/system)\
**Post date:** [May 9, 2023, 5:41pm UTC](https://discourse.openondemand.org/t/allow-hpc-toolset-demo-external-access/2364/3 "2023-05-09T17:41:56Z")

</div>

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.