nextcloud / nextcloud/nextcloudpi
Internal Server Error, cannot access NCP dashboard/files
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 2.9k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
I've run the steps in #1913 and still cannot use my NCP (since last 6 months or so; usage broke without my intervention, with some background update). I get an Internal Server Error and unable to load the dashboard. I can access Panel, which shows all services/checks ok/up. PHP I believe used to be down, but at least that appears fixed now. (I downgraded to version 8.1). I'm on v1.55.3, image NextCloudPi_10-08-21. Have even been using AI to diagnose and help with fixing to no avail. Can anyone help?
I get this in the Panel log after reboot, unsure if it's important: read error on connection to /var/run/redis/redis.sock:0.
Command: systemctl status redis.service check shows the service as active.
NCP report attached
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached NCP report and the Panel log entry about /var/run/redis/redis.sock, then review the reported systemctl status redis.service result and the steps in #1913. Determine why the dashboard and files return an Internal Server Error on v1.55.3, and verify that both are accessible after the cause is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, redis, shell
- Domain
- backend, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100