After update v 1.30 panel doest load up

Community Support
1

Hi,

I just updated my ubuntu 20.04 vps for version 1.30 .
After update the hestiapanel doesnt open any more?
Please help.

2

Panel does 500 error only while the installer rebuilds and configures Hestia.

Patience…

3

i waited and rebooted my vps but still

4

Do not use the web interface use cli

5

What cli command should i use?

6

aswell do not crosspost or check both threads if you do so :).

7

Yes i did, and the update went succesfull,but there after no panel.

8

what’s the output of systemctl status hestia?

9

root@vps:~# systemctl status hestia
â—Ź hestia.service - LSB: starts the hestia control panel
Loaded: loaded (/etc/init.d/hestia; generated)
Active: active (running) since Tue 2020-10-27 09:38:32 -03; 5min ago
Docs: man:systemd-sysv-generator(8)
Process: 1493 ExecStart=/etc/init.d/hestia start (code=exited, status=0/SUC>
Tasks: 3 (limit: 1111)
Memory: 18.9M
CGroup: /system.slice/hestia.service
├─1581 nginx: master process /usr/local/hestia/nginx/sbin/hestia-n>
├─1582 nginx: worker process
└─1641 php-fpm: master process (/usr/local/hestia/php/etc/php-fpm.>

Oct 27 09:38:30 vps.mydomain.com systemd[1]: Starting LSB: starts the hestia c>
Oct 27 09:38:31 vps.mydomain.com hestia[1493]: * Starting hestia-nginx hestia>
Oct 27 09:38:31vps.mydomain.com hestia[1493]: …done.
Oct 27 09:38:31 vps.mydomain.com hestia[1493]: * Starting hestia-php hestia-p>
Oct 27 09:38:32 vps.mydomain.com hestia[1493]: …done.
Oct 27 09:38:32 vps.mydomain.com systemd[1]: Started LSB: starts the hestia co>
lines 1-18/18 (END)…skipping…
â—Ź hestia.service - LSB: starts the hestia control panel
Loaded: loaded (/etc/init.d/hestia; generated)
Active: active (running) since Tue 2020-10-27 09:38:32 -03; 5min ago
Docs: man:systemd-sysv-generator(8)
Process: 1493 ExecStart=/etc/init.d/hestia start (code=exited, status=0/SUCCESS)
Tasks: 3 (limit: 1111)
Memory: 18.9M
CGroup: /system.slice/hestia.service
├─1581 nginx: master process /usr/local/hestia/nginx/sbin/hestia-nginx
├─1582 nginx: worker process
└─1641 php-fpm: master process (/usr/local/hestia/php/etc/php-fpm.conf)

Oct 27 09:38:30 vps.mydomain.com systemd[1]: Starting LSB: starts the hestia control panel…
Oct 27 09:38:31 vps.mydomain.com hestia[1493]: * Starting hestia-nginx hestia-nginx
Oct 27 09:38:31 vps.mydomain.com hestia[1493]: …done.
Oct 27 09:38:31 vps.mydomain.com hestia[1493]: * Starting hestia-php hestia-php
Oct 27 09:38:32 vps.mydomain.com hestia[1493]: …done.
Oct 27 09:38:32 vps.mydomain.com systemd[1]: Started LSB: starts the hestia control panel.

10

What happens after a server reboot or systemctl restart hestia?

11

root@vps:~# systemctl restart hestia
root@vps:~#

12

Everything that they talk about in this thread happened to me, and it helped me to restart by commands “systemctl restart hestia”
Thank you @Raphael

13

Mine still stuck :frowning:

14

Well I will tell you my procedure guiding me from this thread and others:

  1. Update and get error 500, restart the server.
  2. Then I put “apt update && apt upgrade”
  3. Finally restart hestia “systemctl restart hestia”
    I don’t know if you didn’t do any but it would be good to see what happened it helped me.
15

I did,
i just did this:
root@vps:~# v-update-sys-hestia-all
v-update-sys-hestia-all: command not found

seems not to work?

16

Try /usr/local/hestia/bin/v-update-sys-hestia-all

But apt update && apt upgrade should be enough

1 Like
17

Still not,
When it is working i had set my panel port to 2083
Is it so that after the update that could have been changed?
How to check this ?

18

No, the update sets back the “old” port. Infact you see a internal server error, the port has been set properly aswell for your system.

Any usefull in /usr/local/hestia/log/nginx-error.log?

19

root@vps:~# nano /usr/local/hestia/log/nginx-error.log
GNU nano 4.8 /usr/local/hestia/log/nginx-error.log
2020/07/25 02:02:00 [error] 964#0: recv() failed (111: Connection refused) while requesting certificate status, responder: ocsp.int-x3.letsencrypt.org, peer: 96.17.68.99:80, certificate: “/usr/local/hestia/ssl/certificate.crt”
2020/07/25 02:02:00 [error] 964#0: OCSP responder prematurely closed connection while requesting certificate status, responder: ocsp.int-x3.letsencrypt.org, peer: 96.17.68.99:80, certificate: “/usr/local/hestia/ssl/certificate.crt”
2020/10/15 19:42:25 [error] 1521#0: *130 open() “/usr/local/hestia/web/stalker_portal/c/version.js” failed (2: No such file or directory), client: 134.122.105.106, server: _, request: “GET /stalker_portal/c/version.js HTTP/1.1”, host: ">
2020/10/15 19:42:28 [error] 1521#0: *133 “/usr/local/hestia/web/client_area/index.php” is not found (2: No such file or directory), client: 134.122.105.106, server: _, request: “GET /client_area/ HTTP/1.1”, host: “129.146.94.205:2083”
2020/10/15 19:42:32 [error] 1521#0: *136 FastCGI sent in stderr: “Primary script unknown” while reading response header from upstream, client: 134.122.105.106, server: _, request: “GET /system_api.php HTTP/1.1”, upstream: "fastcgi://uni>
2020/10/15 19:42:35 [error] 1521#0: *140 FastCGI sent in stderr: “Primary script unknown” while reading response header from upstream, client: 134.122.105.106, server: _, request: “GET /streaming/clients_live.php HTTP/1.1”, upstream: "f>
2020/10/15 19:42:39 [error] 1521#0: *144 “/usr/local/hestia/web/stalker_portal/c/index.php” is not found (2: No such file or directory), client: 134.122.105.106, server: _, request: “GET /stalker_portal/c/ HTTP/1.1”, host: "129.146.94.2>
2020/10/15 19:42:42 [error] 1521#0: *147 FastCGI sent in stderr: “Primary script unknown” while reading response header from upstream, client: 134.122.105.106, server: _, request: “GET /api.php HTTP/1.1”, upstream: "fastcgi://unix:/var/>
2020/10/15 19:42:45 [error] 1521#0: *151 FastCGI sent in stderr: “Primary script unknown” while reading response header from upstream, client: 134.122.105.106, server: _, request: “GET /login.php HTTP/1.1”, upstream: "fastcgi://unix:/va>
2020/10/15 19:42:48 [error] 1521#0: *155 open() “/usr/local/hestia/web/streaming” failed (2: No such file or directory), client: 134.122.105.106, server: _, request: “GET /streaming HTTP/1.1”, host: “129.146.94.205:2083”
2020/10/15 19:42:49 [error] 1521#0: *158 FastCGI sent in stderr: “Primary script unknown” while reading response header from upstream, client: 134.122.105.106, server: _, request: “GET /streaming/clients_live.php HTTP/1.1”, upstream: "f>
2020/10/15 19:42:50 [error] 1521#0: *162 FastCGI sent in stderr: “Primary script unknown” while reading response header from upstream, client: 134.122.105.106, server: _, request: “GET /streaming/nyJT7a43LN.php HTTP/1.1”, upstream: "fas>
2020/10/24 22:29:50 [error] 1521#0: *679 FastCGI sent in stderr: “Primary script unknown” while reading response header from upstream, client: 188.166.79.11, server: _, request: “GET /system_api.php HTTP/1.1”, upstream: "fastcgi://unix:>
2020/10/24 22:29:54 [error] 1521#0: *683 open() “/usr/local/hestia/web/c/version.js” failed (2: No such file or directory), client: 188.166.79.11, server: _, request: “GET /c/version.js HTTP/1.1”, host: “129.146.94.205:2083”
2020/10/24 22:29:57 [error] 1521#0: *686 FastCGI sent in stderr: “Primary script unknown” while reading response header from upstream, client: 188.166.79.11, server: _, request: “GET /streaming/clients_live.php HTTP/1.1”, upstream: "fas>
2020/10/24 22:30:01 [error] 1521#0: *690 open() “/usr/local/hestia/web/stalker_portal/c/version.js” failed (2: No such file or directory), client: 188.166.79.11, server: _, request: “GET /stalker_portal/c/version.js HTTP/1.1”, host: "12>

20

Last log is from 4 days ago?