I am using this template (Proxy HestiaCP to port 443 · GitHub) and today after months of not logging in the page can’t be reached. I can’t enter with the subdomain, ip port combo or domain only. I had a custom port also and I think hestia changed it with the update, back to 8083, but that doesnt work either its been 2 months since I last logged in. How can I enter my panel?
When I go to the subdomain
Any help appreciated, thank you!
Check systemctl status hestia, probaly your service needs a restart.
Hi ScIT. No, the restart didn’t work.
This is the only error I found, and it dates back to Oct of last year. It’s strange that I can’t login via IP:Port either.
#0 /usr/local/hestia/web/fm/vendor/league/flysystem/src/Filesystem.php(328): League\Flysystem\Filesystem->assertPresent()
#1 /usr/local/hestia/web/fm/backend/Services/Storage/Filesystem.php(68): League\Flysystem\Filesystem->getSize()
#2 /usr/local/hestia/web/fm/backend/Services/Storage/Filesystem.php(128): Filegator\Services\Storage\Filesystem->isDir()
#3 /usr/local/hestia/web/fm/backend/Services/Archiver/Adapters/ZipArchiver.php(74): Filegator\Services\Storage\Filesystem->readStream()
#4 /usr/local/hestia/web/fm/backend/Services/Archiver/Adapters/ZipArchiver.php(65): Filegator\Services\Archiver\Adapters\ZipArchiver->addFileFromStorage()
#5 /usr/local/hestia/web/fm/backend/Controllers/FileController.php(125): Filegator\Services\Archiver\Adapte" while reading response header from upstream, client: , server: _, request: "POST /fm/?r=/zipitems HTTP/1.0", upstream: "fastcgi://unix:/var/run/hestia-php.sock:", host: "cp.-------.net", referrer: "https://cp.-----------.net/fm/"
2020/10/05 04:36:33 [error] 2343#0: *609 open() “/usr/local/hestia/web/phpmyadmin” failed (2: No such file or directory), client: , server: _, request: “GET /phpmyadmin HTTP/1.0”, host: “cp.----.net”, referrer: “https://cp.-----.net/list/db/”
What happens when you run apt update && apt upgrade
Will it update Hestia?
It seems to be getting the release from the repository. https://apt.hestiacp.com buster InRelease. I am on version 1.3.3 and I believe it updated on its own.
The issue is not the template… But I have no idea what could be wrong.
If you DM me the login details I will have a look in the morning…
Normally an 500 error is caused by an php error some where