Hi, I habe recovered a Backup File from the cloud instance. After recovering it on my own debian server, the URL / Title of the page can be seen the login page is however white. “Safe Mode” does not work. Browser Cache is cleaned. I have rebuilt the app, no difference. Do you have an idea, what still could be done? These errors have been reported according to the browser console: [report] I have checked it in the production log as well, The connection to REDIS Servers seems not to work. [image] I have deleted the container, rebooted the VM and installed Discourse once again. I have received this error: Docker: driver failed programming external connectivity on endpoint app … [image] Thank you for your suggestions. I.

that could come from your app.yml, what do you have there ? ## Uncomment these two lines if you wish to add Lets Encrypt (https) # - "templates/web.ssl.template.yml" # - "templates/web.letsencrypt.ssl.template.yml" you might also have hit a letsencrypt’s renew limit…

I have stopped nginx and rebuilt the app. According to production log REDIS doesnt work´: [image] Do you have any idea what to do? I have already rebooted, rebuilt, container destroyed and it newly pulled etc. nothing has helped …

:thinking: sudo systemctl status redis ?

Redis is not found … [image] How can I start redis in the discourse container properly? If I try to start it, it doesn´t work: [image] regards I.

I have been actually able to install it first with a help of a tutorial. After I have recovered a backup from a discourse-hoster, I have received only white pages. Since that time I am not able to install it … It can be that my reboots, rebuilds have crashed the vm itself.

[image] ITAS-Isti: installed Discourse once again How did you do that ? ./discourse-setup again ?

I have made it, many times, of course.

I think the problem is that redis works no longer and I do not now how to start it. I have already pulled the discourse container, it has not helped however. I think I destroy the container, delete the directory, pull the container from git and start from scratch again …

As you see, I have made it as simple as possible: [image]

After recoverying a Backup file on new "On-premise" VM - Site no longer works

Product Support Self-hosting

Benjamin_D (Benjamin Decotte) August 14, 2021, 5:59pm 2

you might have something listening on the 80 port (nginx ?)

Topic		Replies	Views
Hangs discourse and discourse restore FAILED Self-hosting	24	2510	August 26, 2020
Error connecting to Redis Self-hosting	17	7468	March 21, 2023
Restore specific discourse backup version Product Support backups	20	669	August 29, 2025
Redis Error after upgrade Self-hosting	13	1898	June 3, 2020
Installed OK. Working fine for one day. Suddenly stopped working Self-hosting	14	3071	June 20, 2018

After recoverying a Backup file on new "On-premise" VM - Site no longer works

Related topics