# Server clone issues

**URL:** <https://discourse.openondemand.org/t/server-clone-issues/2807>\
**Category:** Get Help\
**Tags:** ondemand2, question\
**Created:** [July 11, 2023, 8:15pm UTC](https://discourse.openondemand.org/t/server-clone-issues/2807 "2023-07-11T20:15:34Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![kenny.hanson](https://avatars.discourse-cdn.com/v4/letter/k/6de8d8/32.png) [@kenny.hanson](https://discourse.openondemand.org/u/kenny.hanson)\
**Post date:** [July 11, 2023, 8:15pm UTC](https://discourse.openondemand.org/t/server-clone-issues/2807/1 "2023-07-11T20:15:34Z")

</div>

Hi,  
I made a clone of my existing production OOD server (it’s a vmware vm) to test v3 and get ready for the migration in 3 weeks. I changed the hostname and updated ood\_portal.yml then ran the update\_ood\_portal script. I’m able to hit the new server but it immediately generates a dex login URL that points to the original production server. I checked the ondemand-dex config.yml and it’s pointing to the right hostname. I cleared the Apache cache in /var/cache/httpd and now it bypasses ondemand-dex and gives me a 500 Internal Server error.  
Is there an easy way to do this? Or should I just install from scratch?

Kenny

Kenny

---

<div class="post-metadata">

**Author:** ![travert](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/travert/32/3074_2.png) [@travert](https://discourse.openondemand.org/u/travert)\
**Post date:** [July 12, 2023, 2:32pm UTC](https://discourse.openondemand.org/t/server-clone-issues/2807/2 "2023-07-12T14:32:50Z")

</div>

Hey sorry for the trouble. Which OS are you using?

Are you following the upgrade instructions in the docs:  
[https://osc.github.io/ood-documentation/latest/release-notes/v3.0-release-notes.html#upgrade-directions](https://osc.github.io/ood-documentation/latest/release-notes/v3.0-release-notes.html#upgrade-directions)

If so, did you run the `ondemand-dex` update as well already?

---

<div class="post-metadata">

**Author:** ![kenny.hanson](https://avatars.discourse-cdn.com/v4/letter/k/6de8d8/32.png) [@kenny.hanson](https://discourse.openondemand.org/u/kenny.hanson)\
**Post date:** [July 12, 2023, 11:01pm UTC](https://discourse.openondemand.org/t/server-clone-issues/2807/3 "2023-07-12T23:01:01Z")

</div>

Hi Travis,  
I’m running Rocky Linux 8.8. I haven’t run any updates yet, was trying to get it to work first. /etc/ood/config/ood\_portal.yml is the only place I need to change the hostname, right?

Kenny

---

<div class="post-metadata">

**Author:** ![travert](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/travert/32/3074_2.png) [@travert](https://discourse.openondemand.org/u/travert)\
**Post date:** [July 13, 2023, 2:28pm UTC](https://discourse.openondemand.org/t/server-clone-issues/2807/4 "2023-07-13T14:28:16Z")

</div>

Yeah, that would be where the `hostname` would be changed. I ask about the `ondemand-dex` because the docs call out that if you are using `dex` you will also need to update `ondemand-dex` and I wondered if this was what is causing your auth error.

---

<div class="post-metadata">

**Author:** ![kenny.hanson](https://avatars.discourse-cdn.com/v4/letter/k/6de8d8/32.png) [@kenny.hanson](https://discourse.openondemand.org/u/kenny.hanson)\
**Post date:** [July 13, 2023, 8:50pm UTC](https://discourse.openondemand.org/t/server-clone-issues/2807/5 "2023-07-13T20:50:03Z")

</div>

Okay I fixed it. I had to go get a new certificate and also fix /etc/httpd/ssl.conf which was pointing to my production server. 🙂

I’ll try an upgrade path tomorrow.

Thanks Travis!

---

<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:** [January 9, 2024, 8:50pm UTC](https://discourse.openondemand.org/t/server-clone-issues/2807/6 "2024-01-09T20:50:14Z")

</div>

Closed on January 9, 2024, 8:50pm UTC

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