Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #1419] SSL_ERROR_RX_RECORD_TOO_LONG #907

New Issue
Closed
opened 2026-02-22 18:22:08 -05:00 by yindo · 10 comments
yindo commented 2026-02-22 18:22:08 -05:00
Owner
Copy Link
Copy Source

Originally created by @yongshengma on GitHub (May 16, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1419

Hello

I followed this info to setup on Ubuntu 22:

https://github.com/Mintplex-Labs/anything-llm?tab=readme-ov-file#how-to-setup-for-development

When I access the the browser, it gives error: SSL_ERROR_RX_RECORD_TOO_LONG

node -v
v18.20.2

Any idea please?

Sincerely,

Yongsheng

Originally created by @yongshengma on GitHub (May 16, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1419 Hello I followed this info to setup on Ubuntu 22: https://github.com/Mintplex-Labs/anything-llm?tab=readme-ov-file#how-to-setup-for-development When I access the the browser, it gives error: SSL_ERROR_RX_RECORD_TOO_LONG node -v v18.20.2 Any idea please? Sincerely, Yongsheng
yindo closed this issue 2026-02-22 18:22:08 -05:00
yindo commented 2026-02-22 18:22:09 -05:00
Author
Owner
Copy Link
Copy Source

@atljoseph commented on GitHub (May 16, 2024):

Don’t use localhost when using docker

@atljoseph commented on GitHub (May 16, 2024): Don’t use localhost when using docker
yindo commented 2026-02-22 18:22:09 -05:00
Author
Owner
Copy Link
Copy Source

@atljoseph commented on GitHub (May 16, 2024):

See markdown file in docker dir

@atljoseph commented on GitHub (May 16, 2024): See markdown file in docker dir
yindo commented 2026-02-22 18:22:09 -05:00
Author
Owner
Copy Link
Copy Source

@atljoseph commented on GitHub (May 16, 2024):

This really is not an issue with anything LLM. It is just how networking works in general for docker containers. I understand your frustration as I too lost time to this error recently.

@atljoseph commented on GitHub (May 16, 2024): This really is not an issue with anything LLM. It is just how networking works in general for docker containers. I understand your frustration as I too lost time to this error recently.
yindo commented 2026-02-22 18:22:09 -05:00
Author
Owner
Copy Link
Copy Source

@yongshengma commented on GitHub (May 17, 2024):

See markdown file in docker dir

Hi atljoseph

I'm not using docker. I setup manually in ubuntu 22. No nginx. Can you give any details how to configure it to solve this ssl issue?

Thanks!

Yongsheng

@yongshengma commented on GitHub (May 17, 2024): > See markdown file in docker dir Hi atljoseph I'm not using docker. I setup manually in ubuntu 22. No nginx. Can you give any details how to configure it to solve this ssl issue? Thanks! Yongsheng
yindo commented 2026-02-22 18:22:09 -05:00
Author
Owner
Copy Link
Copy Source

@atljoseph commented on GitHub (May 17, 2024):

No idea sorry

On Fri, May 17, 2024 at 3:46 AM Yongsheng Ma @.***>
wrote:

See markdown file in docker dir

Hi atljoseph

I'm not using docker. I setup manually in ubuntu 22. No nginx. Can you
give any details how to configure it to solve this ssl issue?

Thanks!

Yongsheng

—
Reply to this email directly, view it on GitHub
https://github.com/Mintplex-Labs/anything-llm/issues/1419#issuecomment-2116951338,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF632FM4CMZ2LIIPNACIBC3ZCWYV3AVCNFSM6AAAAABHZW6E2CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJWHE2TCMZTHA
.
You are receiving this because you commented.Message ID:
@.***>

@atljoseph commented on GitHub (May 17, 2024): No idea sorry On Fri, May 17, 2024 at 3:46 AM Yongsheng Ma ***@***.***> wrote: > See markdown file in docker dir > > Hi atljoseph > > I'm not using docker. I setup manually in ubuntu 22. No nginx. Can you > give any details how to configure it to solve this ssl issue? > > Thanks! > > Yongsheng > > — > Reply to this email directly, view it on GitHub > <https://github.com/Mintplex-Labs/anything-llm/issues/1419#issuecomment-2116951338>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AF632FM4CMZ2LIIPNACIBC3ZCWYV3AVCNFSM6AAAAABHZW6E2CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJWHE2TCMZTHA> > . > You are receiving this because you commented.Message ID: > ***@***.***> >
yindo commented 2026-02-22 18:22:09 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 17, 2024):

@yongshengma
Are you using NGINX? This is an NGINX error, not AnythingLLM.

In your server block for HTTP are you using listen 443 ssl;? Some people just put listen 443 which listens on the port but is the SSL port standard and will lead to issues like that.

@timothycarambat commented on GitHub (May 17, 2024): @yongshengma Are you using NGINX? This is an NGINX error, not AnythingLLM. In your server block for HTTP are you using `listen 443 ssl;`? Some people just put `listen 443` which listens on the port but is the SSL port standard and will lead to issues like that.
yindo commented 2026-02-22 18:22:09 -05:00
Author
Owner
Copy Link
Copy Source

@yongshengma commented on GitHub (May 20, 2024):

@yongshengma Are you using NGINX? This is an NGINX error, not AnythingLLM.

In your server block for HTTP are you using listen 443 ssl;? Some people just put listen 443 which listens on the port but is the SSL port standard and will lead to issues like that.

Sorry. Using https is my mistake. I should have used http.

I use http now and get an issue as below. it could be somewhere I didn't correctly configure. BTW no nginx. Please let me give more details.

  1. env
    cd anything-llm-master
    cat frontend/.env
    VITE_API_BASE='/api'

  2. yarn setup

  3. yarn dev:server

yarn run v1.22.22
$ cd server && yarn dev
$ NODE_ENV=development nodemon --ignore documents --ignore vector-cache --ignore storage --ignore swagger --trace-warnings index.js
[nodemon] 2.0.22
[nodemon] to restart at any time, enter rs
[nodemon] watching path(s): .
[nodemon] watching extensions: js,mjs,json
[nodemon] starting node --trace-warnings index.js
$ node ./swagger/init.js
[TELEMETRY STUBBED] Anonymous Telemetry stubbed in development.
[CommunicationKey] RSA key pair generated for signed payloads within AnythingLLM services.
Primary server in HTTP mode listening on port 3001
Swagger-autogen: Success ✔
Swagger-autogen: Patched servers.url ✔

  1. yarn dev:frontend
  2. yarn dev:collector
  3. http://192.168.6.116:3001/

When I access the URL, it responds: 404 Not Found

Thanks!

@yongshengma commented on GitHub (May 20, 2024): > @yongshengma Are you using NGINX? This is an NGINX error, not AnythingLLM. > > In your server block for HTTP are you using `listen 443 ssl;`? Some people just put `listen 443` which listens on the port but is the SSL port standard and will lead to issues like that. Sorry. Using https is my mistake. I should have used http. I use http now and get an issue as below. it could be somewhere I didn't correctly configure. BTW no nginx. Please let me give more details. 1. env cd anything-llm-master cat frontend/.env VITE_API_BASE='/api' 2. yarn setup 3. yarn dev:server yarn run v1.22.22 $ cd server && yarn dev $ NODE_ENV=development nodemon --ignore documents --ignore vector-cache --ignore storage --ignore swagger --trace-warnings index.js [nodemon] 2.0.22 [nodemon] to restart at any time, enter `rs` [nodemon] watching path(s): *.* [nodemon] watching extensions: js,mjs,json [nodemon] starting `node --trace-warnings index.js` $ node ./swagger/init.js [TELEMETRY STUBBED] Anonymous Telemetry stubbed in development. [CommunicationKey] RSA key pair generated for signed payloads within AnythingLLM services. Primary server in HTTP mode listening on port 3001 Swagger-autogen: Success ✔ Swagger-autogen: Patched servers.url ✔ 4. yarn dev:frontend 5. yarn dev:collector 6. http://192.168.6.116:3001/ When I access the URL, it responds: 404 Not Found Thanks!
yindo commented 2026-02-22 18:22:09 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 20, 2024):

Are you trying to run the service in production or in development? Looks like you are running the server in development mode in which case the frontend needs to be run separately and will be on port 3000 yarn dev:frontend.

If you are trying to run this in production you should only be running yarn prod:server and only be running this after yarn prod:frontend && cp -R frontend/dist server/public.

Then the frontend will be bundled and present in server/public and the whole app will live on 3001

@timothycarambat commented on GitHub (May 20, 2024): Are you trying to run the service in production or in development? Looks like you are running the server in development mode in which case the frontend needs to be run separately and will be on port 3000 `yarn dev:frontend`. If you are trying to run this in production you should only be running `yarn prod:server` and only be running this after `yarn prod:frontend && cp -R frontend/dist server/public`. Then the frontend will be bundled and present in `server/public` and the whole app will live on 3001
yindo commented 2026-02-22 18:22:10 -05:00
Author
Owner
Copy Link
Copy Source

@yongshengma commented on GitHub (Jun 4, 2024):

@timothycarambat

I find it's caused by STORAGE_DIR. Now I can start it up in production by following the steps you gave. Appreciate!

Sorry to abuse this post as a newbie. Just one more question. Where's the login page or user front?

@yongshengma commented on GitHub (Jun 4, 2024): @timothycarambat I find it's caused by STORAGE_DIR. Now I can start it up in production by following the steps you gave. Appreciate! Sorry to abuse this post as a newbie. Just one more question. Where's the login page or user front?
yindo commented 2026-02-22 18:22:10 -05:00
Author
Owner
Copy Link
Copy Source

@atljoseph commented on GitHub (Jun 4, 2024):

The way the storage dir works between the normal and the render image is a
bit odd. I fought and fought with the normal image the longest time. Tim
mentioned the render image, and that worked great, but not 100% sure why
both images are needed. Maybe the render image is helpful to you. Maybe
not.

On Tue, Jun 4, 2024 at 9:37 AM Yongsheng Ma @.***>
wrote:

@timothycarambat https://github.com/timothycarambat

I find it's caused by STORAGE_DIR. Now I can start it up in production by
following the steps you gave. Appreciate!

Sorry to abuse this post as a newbie. Just one more question. Where's the
login page or user front?

—
Reply to this email directly, view it on GitHub
https://github.com/Mintplex-Labs/anything-llm/issues/1419#issuecomment-2147557769,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF632FNTDHPHHNXCTE6UGILZFW7ILAVCNFSM6AAAAABHZW6E2CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBXGU2TONZWHE
.
You are receiving this because you commented.Message ID:
@.***>

@atljoseph commented on GitHub (Jun 4, 2024): The way the storage dir works between the normal and the render image is a bit odd. I fought and fought with the normal image the longest time. Tim mentioned the render image, and that worked great, but not 100% sure why both images are needed. Maybe the render image is helpful to you. Maybe not. On Tue, Jun 4, 2024 at 9:37 AM Yongsheng Ma ***@***.***> wrote: > @timothycarambat <https://github.com/timothycarambat> > > I find it's caused by STORAGE_DIR. Now I can start it up in production by > following the steps you gave. Appreciate! > > Sorry to abuse this post as a newbie. Just one more question. Where's the > login page or user front? > > — > Reply to this email directly, view it on GitHub > <https://github.com/Mintplex-Labs/anything-llm/issues/1419#issuecomment-2147557769>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AF632FNTDHPHHNXCTE6UGILZFW7ILAVCNFSM6AAAAABHZW6E2CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBXGU2TONZWHE> > . > You are receiving this because you commented.Message ID: > ***@***.***> >
yindo changed title from SSL_ERROR_RX_RECORD_TOO_LONG to [GH-ISSUE #1419] SSL_ERROR_RX_RECORD_TOO_LONG 2026-06-05 14:37:52 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#907
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?