bluet / bluet/docker-cronicle-docker
HTTP connection has closed: c540 - caprover
- Dominant language
- Shell
- Stars
- 146
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description

I'm installing it on caprover, even with active websocket the login and password don't appear, they just stay on the "Waiting for master server..." page. Locally on my notebook, it worked perfectly.
```
023-12-14T14:21:20.332444331Z [1702563680.332][2023-12-14 11:21:20][cc4b1acbcd36][13][WebServer][debug][9][Sending compressed HTTP response with gzip: 200 OK][{"Content-Type":"text/javascript","Access-Control-Allow-Origin":"*","Server":"Cronicle 1.0","Content-Length":90,"Content-Encoding":"gzip"}]
2023-12-14T14:21:20.333433784Z [1702563680.333][2023-12-14 11:21:20][cc4b1acbcd36][13][WebServer][debug][9][Request complete][]
2023-12-14T14:21:20.333700930Z [1702563680.333][2023-12-14 11:21:20][cc4b1acbcd36][13][WebServer][debug][9][Response finished writing to socket][{"id":"r541"}]
2023-12-14T14:21:20.333853923Z [1702563680.333][2023-12-14 11:21:20][cc4b1acbcd36][13][WebServer][debug][9][Request performance metrics:][{"scale":1000,"perf":{"total":9.003,"queue":0.145,"read":0.029,"filter":4.109,"process":0.512,"encode":0.845,"write":1.835},"counters":{"bytes_in":650,"bytes_out":236,"num_requests":1}}]
2023-12-14T14:21:20.333973305Z [1702563680.333][2023-12-14 11:21:20][cc4b1acbcd36][13][WebServer][debug][9][Keeping socket open for keep-alives: c540][]
2023-12-14T14:21:20.334753974Z [1702563680.334][2023-12-14 11:21:20][cc4b1acbcd36][13][WebServer][debug][8][HTTP connection has closed: c540][{"ip":"::ffff:10.0.1.8","port":3012,"total_elapsed":12,"num_requests":1,"bytes_in":650,"bytes_out":236}]
```
Do I need to put a specific env var for it to work in production?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the Docker deployment on CapRover and compare it with the working local installation. Use the supplied WebServer log, especially the keep-alive and closed-connection entries, to investigate why the login page remains waiting for the master server. Done means the production deployment displays the login and password fields and the required configuration is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100