[Question]: How to make it work with Nginx Proxy Manager

[Harrenkyym]

What is your question?

Hi. I'm trying to make LibreChat work in my NAS.

That's what I would expect to do to make it work in NPM, as I do with any other service running in my NAS.

But I don't know how to set my .env:

HOST=0.0.0.0 (?)
PORT=3080

DOMAIN_CLIENT= (?)
DOMAIN_SERVER= (?)

Thanks!

What is the main subject of your question?

Installation

Screenshots

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[danny-avila]

Did you check out the nginx.conf file in the client folder?

[Harrenkyym]

I already have 2 https domains: https://librechat.custom.duckdns.org and https://librechat.custom.com

Both are being redirected to my NAS internal IP:port. But obviously my .env and nginx.conf aren't well configurated. I have a question, would it be possible to have something like this?

HOST=0.0.0.0
PORT=3080

DOMAIN_CLIENT=https://librechat.custom.duckdns.org,https://librechat.custom.com
DOMAIN_SERVER=https://librechat.custom.duckdns.org,https://librechat.custom.com

and in my .env file: server_name librechat.*; so it works for both? I've seen this wildcard here #890

[danny-avila]

I have a question, would it be possible to have something like this?

Probably, but this is beyond my expertise. I say try to get something working and then experiment or consult AI on your setup.

[Harrenkyym]

Hey, Danny. I told you I'm a tryharder. I'm a fucking tryharder.

I did it. It's running.

If anyone ever asks again:

My problem was the folder api/logs/ wasn't being created. So after many tries (tried to explicit it in the Dockerfile/Dockerfile.multi, tried to gave permissions, tried to set UID and GID for the api in the deploy-compose, etc.) I decided to create the folder manually then map the volume in the deploy-compose: - ./api/logs:/app/api/logs

Then, my .env (I modified many things apart from that)

DOMAIN_CLIENT="https://librechat.custom.duckdns.org https//librechat.custom.com"
DOMAIN_SERVER="https://librechat.custom.duckdns.org https//librechat.custom.com"

And my nginx.conf:

server {

  listen 80;
  listen 443 ssl;

  # ssl_certificate /etc/nginx/ssl/nginx.crt;
  # ssl_certificate_key /etc/nginx/ssl/nginx.key;

  server_name librechat.*;

   # Increase the client_max_body_size to allow larger file uploads
   # The default limits for image uploads as of 11/22/23 is 20MB/file, and 25MB/request
  client_max_body_size 25M;

  location /api {
    proxy_pass http://api:3080/api;
  }

  location / {
    proxy_pass http://api:3080;
  }
}

I think I haven't forgot anything.

Now is when I tell you that my internal ip:port is working. So I can proxy reverse it with NPM. And now is when I tell you too, that I have tried both ddns at the same time and they are working. Perfect! But I thought... what if I try a third one that I have not specified in the .env file and the subdomain is not even librechat as I set in my nginx.conf? Something like https//gpt.custom.com... It works too! So I'm happy, but I'm pretty sure that part of the code of Librechat is useless. Because if I have to set both domain client and server to supposedly make it work, and it works even if I'm using a different one... I don't even know if the syntax I'm using for two domains is correct. I asked ChatGPT and that was the answer, but I can't confirm it.

Well, it's working. :)

[danny-avila]

Amazing!! So sorry you had to deal with that pesky folder permission issue. I also forgot to mention that DOMAIN_CLIENT/SERVER is only relevant for OAuth logins, forgive me as it's been 7 months since I've worked with those values hands on.

Happy you got it setup and hope it serves you well, man.

[CXwudi]

So does it means that if I disabled the OAuth, I can comment out DOMAIN_CLIENT/SERVER?

[dltj]

My problem was the folder api/logs/ wasn't being created. So after many tries (tried to explicit it in the Dockerfile/Dockerfile.multi, tried to gave permissions, tried to set UID and GID for the api in the deploy-compose, etc.) I decided to create the folder manually then map the volume in the deploy-compose: - ./api/logs:/app/api/logs

@Harrenkyym : This is where I get stuck...how did you create the folder manually? Did you need to add RUN mkdir /app/api/logs and RUN /app/client/public/images to a Dockerfile and rebuild?

[Harrenkyym]

Man, I use Windows on my laptop, and I have access to some shared folders of my NAS, so I literally created it manually, I didn't use any command.

[dltj]

Ah, thanks. I ended up creating the directories in the clone, and those got copied into the Docker image. That'll work for my purposes.