livereload.js with a different port(35729)?

[baalchina]

Bug Report

Hi, all,

Steps to reproduce

I have a docsify installed in a windows system, which behind my nginx.
Docsify listening in port 3000, and nginx proxy this port to 443, which works fine for have a year.

Yesterday I running another docsify site which listened in port 3001, but I found the firet site load very slow, and I found the livereload.js changed to port 35729. Which can not accessed.

So, is there anything wrong with my steps?

Thanks.

Here is the chrome shows:

Other relevant information

• Bug does still occur when all/other plugins are disabled?

• Your OS: Windows 10

• Node.js version: v16.13.0

• npm/yarn version: 8.1.0

• Browser version: Chrome or Edge

• Docsify version: 4.4.3

• Docsify plugins: n/a

Please create a reproducible sandbox

Mention the docsify version in which this bug was not present (if any)

[sy-records]

You can start the service without docsify-cli if you use nginx.

see https://github.com/docsifyjs/docsify/blob/develop/docs/deploy.md#vps

[baalchina]

You can start the service without docsify-cli if you use nginx.

see https://github.com/docsifyjs/docsify/blob/develop/docs/deploy.md#vps

thanks. the problem is, nginx in my campus is just a reverse proxy, it didnot serve the real site.

I tried in my windows server, using 127.0.0.1:3000, I found node.exe is listening on port both 35729 and 3000, seems to make docsify work, node.exe have to listening on two ports? How can I make them to listen on just 3000?

[sy-records]

Instead of using docsify-cli, you can try using python or php as a service startup