[-] lemmyselfhosted@lemmy.world 3 points 9 months ago

I did lol, cool pic

[-] lemmyselfhosted@lemmy.world 1 points 9 months ago

It's a brand new deployment.

7

Hello, I have issue with the most recent version of Ubergeek77 Lemmy instance deploy.

After deployment when I open the website URL, I get the Lemmy Error screen. Https is working but I just get Error message, saying restart the server or contact Lemmy support. The server is Debian 11, and the Lemmy edition is 0.19.2.

Do you know how can I resolve that issue?

19

Hello, how can I migrate Lemmy from one host to another?

It is deployed via the ubergeek77 method with Docker images.

Do I need to transfer them to a new host and change the DNS settings? Do you know how the transfer should be done?

[-] lemmyselfhosted@lemmy.world 1 points 11 months ago* (last edited 11 months ago)

Thank you for the reply. The deployment is good, and the VPS is not that expensive, so it’s not a problem.

I was thinking something along the lines of Docker inside Docker, or Docker Linux Instance that can host the second deployment, I’m jut not sure if that can even happen, or I haven’t figured out how to do it yet.

4

Is there a way I can use the ubergeek77 Easy-Deploy method, to deploy second instance on my server? What files should I edit? I tried to install Lemmy via the official Docker documentation, but it just ain't working for me, so I'm looking for easier way if there is one available. Thanks.

13

I use ubergeek77 to deploy Lemmy instance on my Debian server, however I don't know how to make a second one on the same machine. Do you have any ideas how I can achieve that with this method of deployment?

[-] lemmyselfhosted@lemmy.world 1 points 1 year ago

Thank you for the help, I will try it out!

[-] lemmyselfhosted@lemmy.world 2 points 1 year ago* (last edited 1 year ago)

Thank you for the replies. Nginx was causing the issue. I installed it, but now I face the 526 Invalid SSL certificate error.

I tried putting my API Token in the conf.env and redeply with ./deploy -f but the error persists. Maybe I should somehow manually enter the Cloudflare certificate, but I'm not sure where (or if) I should do it.

From where I bought the domain, they do not let me to use their DNS servers to point to anything but their servers, so I used Coudflare for setting up the DNS records for the domain.

When I first opened the https:// on my server after I got it, the nginx had SSL certificate, the connection was secure. I suppose I have to manually do something here, but not sure what.

lemmyselfhosted

joined 1 year ago