# 302 loop after restoring the database from another xibo server

**URL:** https://community.xibo.org.uk/t/302-loop-after-restoring-the-database-from-another-xibo-server/25656
**Category:** CMS Features and Functionality
**Created:** [August 31, 2021, 8:57am UTC](https://community.xibo.org.uk/t/302-loop-after-restoring-the-database-from-another-xibo-server/25656 "2021-08-31T08:57:23Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![mondwan](https://community.xibo.org.uk/user_avatar/community.xibo.org.uk/mondwan/32/11208_2.png) [@mondwan](https://community.xibo.org.uk/u/mondwan)
#### Post date: [September 3, 2021, 3:26am UTC](https://community.xibo.org.uk/t/302-loop-after-restoring-the-database-from-another-xibo-server/25656/2 "2021-09-03T03:26:59Z")

</div>

I figure this out.

The looping is due to `FORCE_HTTPS` setting. My original server is running in HTTPS while my new server (development) is running in HTTP. If I import the database (the backup database) directly into my HTTP (development) server, there is a loop between HTTP, and HTTPS since `FORCE_HTTPS` is enabled.

In order to turn off `FORCE_HTTPS`, we can follow instructions in [this post](https://community.xibo.org.uk/t/force-https-cant-reach-page/22960/2)

IMO, is it possible to add an environment `SET_FORCE_HTTPS` such that `entrypoint.sh` can do this update at all?

---

_[View the full topic](https://community.xibo.org.uk/t/302-loop-after-restoring-the-database-from-another-xibo-server/25656)._