[Question]: PDF Upload Fails After Domain Deployment (Docker,nginx)

[kihyunnn]

What is your question?

Please give as many details as possible.

I'm experiencing issues with PDF uploads after deploying my LibreChat application to my domain. The application was built following Digital Ocean, Docker, and Nginx documentation. Locally, when running with Docker, image and PDF uploads work without any problems. However, after deploying to my domain (neversleepgpt.kro.kr), PDF uploads fail. The following logs are being generated. I have set client_max_body_size to 25M and tested the pdf upload with a 1MB file with no success.

More Details

Please provide more details if needed.

Here are the detailed logs from various components:

Librechat-NGNIX Log:
- [26/Jan/2025:03:16:07 +0000] "POST /api/files HTTP/2.0" 500 35 "https://mydomain/c/new" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36" "-"
This is when the file upload fails.

LibreChat-API Log:

KeyvMongo connection error: connection timed out
There was an uncaught error: connection timed out

These errors are thrown when the server starts up

error: Error uploading vectors The request was made but no response was received: socket hang up.
error: [/files] Error processing file: socket hang up

These errors occur when uploading files.

librechat-rag_api-1 Log:

error: Error uploading vectors The request was made but no response was received: socket hang up.
error: [/files] Error processing file: socket hang up

librechat-vectordb-1 Log:

WARNING:  autovacuum worker started without a worker entry
WARNING:  there is already a transaction in progress
WARNING:  there is no transaction in progress
WARNING:  there is already a transaction in progress
WARNING:  there is no transaction in progress

MongoDB (chat-mongodb) Logs:

1. WiredTiger Checkpoint Problem

{"t":{"$date":"2025-01-26T03:25:35.735+00:00"},"s":"I", "c":"WTCHKPT", "id":22430, "ctx":"Checkpointer","msg":"WiredTiger message","attr":{"message":{"ts_sec":1737861935,"ts_usec":735558,"thread":"1:0x7fe297e336c0","session_name":"WT_SESSION.checkpoint","category":"WT_VERB_CHECKPOINT_PROGRESS","category_id":7,"verbose_level":"DEBUG_1","verbose_level_id":1,"msg":"saving checkpoint snapshot min: 1967, snapshot max: 1967 snapshot count: 0, oldest timestamp: (0, 0) , meta checkpoint timestamp: (0, 0) base write gen: 191"}}}

This log shows the WiredTiger checkpoint process isn't creating snapshots, indicated by snapshot count: 0 and the oldest timestamp: (0, 0) not updating.

2. serverStatus Command Delay

{"t":{"$date":"2025-01-26T03:16:31.610+00:00"},"s":"I", "c":"COMMAND", "id":20499, "ctx":"ftdc","msg":"serverStatus was very slow","attr":{"timeStats":{"after basic":315,"after asserts":453,"after batchedDeletes":469,"after bucketCatalog":469,"after catalogStats":525,"after changeCollections":525,"after changeStreamPreImages":565,"after collectionCatalog":578,"after connections":578,"after electionMetrics":615,"after extra_info":1995,"after featureCompatibilityVersion":3127,"after flowControl":3580,"after globalLock":3956,"after indexBuilds":4179,"after indexBulkBuilder":4222,"after indexStats":4346,"after internalTransactions":4363,"after locks":4398,"after logicalSessionRecordCache":4985,"after mirroredReads":5070,"after network":5110,"after opLatencies":5126,"after opWorkingTime":5126,"after opcounters":5144,"after opcountersRepl":5144,"after oplog":5144,"after oplogTruncation":5161,"after querySettings":5161,"after queues":5161,"after readConcernCounters":5194,"after readPreferenceCounters":5195,"after repl":5195,"after scramCache":5208,"after security":5208,"after shardSplits":5225,"after storageEngine":5238,"after tcmalloc":5341,"after tenantMigrations":5357,"after trafficRecording":5376,"after transactions":5376,"after transportSecurity":5376,"after twoPhaseCommitCoordinator":5396,"after wiredTiger":6217,"at end":6317}}}

This log indicates the serverStatus command takes a long time to execute, especially in the wiredTiger step.

here is my Nginx config

# Secure default configuration generated by Mozilla SSL Configuration Generator
# generated 2024-01-21, Mozilla Guideline v5.7, nginx 1.24.0, OpenSSL 3.1.4, intermediate configuration
# https://ssl-config.mozilla.org/#server=nginx&version=1.24.0&config=intermediate&openssl=3.1.4&guideline=5.7

server {
    listen 80 default_server;
    listen [::]:80 default_server;

    # To Configure SSL, comment all lines within the Non-SSL section and uncomment all lines under the SSL section.
    ########################################  Non-SSL  ########################################
    server_name mydomain;
    # https://docs.nginx.com/nginx/admin-guide/web-server/compression/
    # gzip on;
    # gzip_vary on;
    # gzip_proxied any;
    # gzip_comp_level 6;
    # gzip_buffers 16 8k;
    # gzip_http_version 1.1;
    # gzip_types text/css application/javascript application/json application/octet-stream;

    # 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$request_uri;
    }

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

    ########################################  SSL  ########################################
    #    # Redirect all http traffic to https
    #    location / {
    #        return 301 https://$host$request_uri;
    #    }
}

server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;

    ssl_certificate /etc/letsencrypt/live/mydomain/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/mydomain/privkey.pem;

    server_name mydomain;

    # 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;
    }
}

What is the main subject of your question?

No response

Screenshots

No response

Code of Conduct

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

[danny-avila]

KeyvMongo connection error: connection timed out

This is the main issue in your setup, the instance absolutely needs a successful mongo connection to start.

The specific build of Mongo you have may be incompatible with your OS or based on CPU architecture.

See this note on mongodb setup:

https://www.librechat.ai/docs/user_guides/mongodb#note