allu62

I'm relieved; I really thought something was wrong on my system. Of course, for you it's not so funny. I hope that you'll find a solution soon... Concerning MBAM, interesting to see that you use it, too. The blacklisting must be recent, I suppose, because it's only during the last few weeks that Browser Guard complained. And concerning people, who use free website hosting platforms for phishing ... in my opinion, they should be banned forever... Thanks. And as I said, I hope that you get rid of the DDoS attacker soon.

Is it possible that Heliohost was down during some time today (around 16-17 o'clock GMT+2)? I got a time-out for both heliohost.org and my VPS. Neither of them could be pinged and vps43.heliohost.us was not resolved. I just ask because such things "make me crazy" and I want to be sure that there's nothing wrong with my connection or whatever on my computer. Another question: Do you have any idea why Heliohost (at least some of your pages) are blackmailed by Malwarebytes Browser Guard? Thanks.

Thanks. I backed up /etc (seems to contain the ssh config) and the entire /var. Not to restore, but to have it, if (in the case of a necessary OS reinstallation) I should need some files located there... Concerning Hestia and Nginx, I hope that I'll find the courage to do what I have to do during the next weeks. Concerning the backup of a Linux server and the use of the "tar" command, if there are other people who run a VPS without being a "real" sysadmin and who are not sure how to proceed, the new tutorial on my website, describing in detail what I did to bakup /home and my MaraiDB databases, might perhaps be helpful...

I still haven't looked to solve my "Hestia down" problem, but a first step is made: I've made a backup of the /home directory (using tar) and exported my databases (using phpMyAdmin). New things learned 🙂 The question that remains is if there is any need respectively any sense to back up other directories? Is there any important data (such as configuration files), that I would or could need in the case I'd have to reinstall the whole, outside the home directory? Would a "real" sysadmin back up another directory or part of it? Thanks for any suggestion. A nice day to everyone!

Thanks a lot. And sorry not to do "as I should". But, I think that it would be respectless to make an automatic renewal debit on the credit card of someone else... I'll make the payment tomorrow or Thursday. Do you still have the email address of my sponsor (it's that email that will appear on the payment documents)? Can you please confirm me what exactly you did when Hestia was down on my VPS? An update of Ubuntu (not of Hestia)? I ask because it's happening again. For the major part my own fault, because I didn't update Ubuntu (Hestia updates automatically, I think). No doubt that if I don't want to risk to loose my website, I'll have to become more serious concerning the administration of the VPS! Have a nice day.

The subsription of my VPS ends on 7th July and I wanted to ask if you can post me a link, giving me the possibility to renew for another 6 months (or 12 months if this should be possible). Or, is there menwhile a general link, where subscription payments from 6 months to 6 months (each time a new payment, no automatic renewal) may be made? Thanks.

So, if I understand, Hestia may break the system by doing its updates? I think that the actual web interface has an option to disable automatic updates. Wouldn't that be the better choice? After all, at least I suppose so, doing a system update would also update Hestia? But, I guess this is only the case if Hestia is an official Ubuntu package? So, perhaps the best practice would be to run apt-get and then run hestia-update manually? Concerning your root access (does that mean that Ubuntu has a user "root"?) to my VPS, that's more than ok. First, there is no reason not to trust you; second there is nothing that's not anyway publically accessible, and third it may be more than useful for me (and letting you lose a little bit less time).

Sorry that you had all this work because of me. I should take the administration of my VPS more seriously and regularly checking if updates have been done, checking the logs and graphs, etc. Thanks a lot! Two questions (curious and trying to understand): 1. Have you any idea how such problems can occur? If there weren't any updates done, all remained as it was and as it worked how can it suddenly stop to work? Perhaps, because some components did do an update? Normally this would mean that all dependencies would also be updated. Or is the Linux "perfect package system" not really perfect and the system can break due to packaage incompatibilities? 2. How did you do to connect to my VPS? Using a sudo account that you created when installing Ubuntu? Anyway, I'm really grateful. Thanks to all those who, during the last years, helped me to keep my website running!

Playing around with Windows 3.x ist the best way to be convinced that computers aren't only logic but also magic. Things that work one day, but no more the next, or vice-versa. Thing that only work if others, apparently no related, are present, or don't work if they are present. I don't know if you did something on my VPS. If yes, it was the right thing. If not ... yeah, then it was just magic! Hestia CP is back, with a new SSL certificate for 3 months. When I accessed it, all servers were running, except spam assassin, that I restarted without any problems. Hestia has been updated to version 1.6.8, hestia-php to version 8.2.5 (as far as I remember this information is a new feature of the control panel). Remains a problem with hestia-nginx: in the updates section, version 1.23.0 is marked with a yellow exclamation mark. Does that mean that update failed? Or that something went wrong? What is the best action I can take to resolve this? I'm really happy that things figured out this way. Having given up my website would have been having given up my conviction that, even if you live in the street, you can live a "normal" life, and do useful things that are helpful to other people. Thanks a lot to Kairion for his great support! This is what I like at HelioHost, and I hope that I can be a part of this great community for the next years....

I think that it's you who is patient and if there is someone to say sorry, it's me... The "netstat" command is no longer available by default on Ubuntu; trying to install "net-tools" gives the following error (maybe this gives you some supplementary information concerning my Hestia problem). sudo apt install net-tools Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: net-tools 0 upgraded, 1 newly installed, 0 to remove and 150 not upgraded. 1 not fully installed or removed. Need to get 196 kB of archives. After this operation, 864 kB of additional disk space will be used. Get:1 http://us.archive.ubuntu.com/ubuntu focal/main amd64 net-tools amd64 1.60+git20180626.aebd88e-1ubuntu1 [196 kB] Fetched 196 kB in 0s (472 kB/s) Selecting previously unselected package net-tools. (Reading database ... 162082 files and directories currently installed.) Preparing to unpack .../net-tools_1.60+git20180626.aebd88e-1ubuntu1_amd64.deb ... Unpacking net-tools (1.60+git20180626.aebd88e-1ubuntu1) ... Setting up net-tools (1.60+git20180626.aebd88e-1ubuntu1) ... Setting up hestia-php (8.2.5) ... dpkg: error processing package hestia-php (--configure): installed hestia-php package post-installation script subprocess returned error exit status 1 Processing triggers for man-db (2.9.1-1) ... Errors were encountered while processing: hestia-php Error: Timeout was reached E: Sub-process /usr/bin/dpkg returned an error code (1) does I searched the Internet to find a replacement for netstat. I think that "lsof" does what you are looking for. Here the output: sudo lsof -i:8083 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME hestia-ng 1111 admin 6u IPv4 26937 0t0 TCP *:8083 (LISTEN) Trying to restart Hestia fails, as described in my post of April, 13th. Concerning the reinstallation of hestia-nginx and hestia-php, I wanted to ask first if this is secure, in the sense if it isn't it a risk that my website (still full functional, including PHP) wouldn't work correctly anymore? Thanks a lot for your concern and efforts to help me!

There is not lots to see. The same error message, again and again, here the last lines of the file: 2023/04/18 05:35:19 [emerg] 1018155#0: bind() to 0.0.0.0:8083 failed (98: Address already in use) 2023/04/18 05:35:19 [emerg] 1018155#0: bind() to 0.0.0.0:8083 failed (98: Address already in use) 2023/04/18 05:35:19 [emerg] 1018155#0: bind() to 0.0.0.0:8083 failed (98: Address already in use) 2023/04/18 05:35:19 [emerg] 1018155#0: bind() to 0.0.0.0:8083 failed (98: Address already in use) 2023/04/18 05:35:19 [emerg] 1018155#0: bind() to 0.0.0.0:8083 failed (98: Address already in use) 2023/04/18 05:35:19 [emerg] 1018155#0: still could not bind()

Really not capable to take whatever decision at the moment. Not only concerning my VPS... However, I tried to get some details concerning Hestia CP. Using SSH, I tried to start the servive - this failed. Here the output: allu62@vps43:~$ sudo /usr/local/hestia/bin/v-start-service hestia [sudo] password for allu62: Job for hestia.service failed because the control process exited with error code. See "systemctl status hestia.service" and "journalctl -xe" for details. allu62@vps43:~$ I did as told, here the result: allu62@vps43:~$ sudo systemctl status hestia.service ● hestia.service - LSB: starts the hestia control panel Loaded: loaded (/etc/init.d/hestia; generated) Active: failed (Result: exit-code) since Mon 2023-04-10 12:25:26 UTC; 4min 43s ago Docs: man:systemd-sysv-generator(8) Process: 187706 ExecStart=/etc/init.d/hestia start (code=exited, status=1/FAILURE) Tasks: 1 (limit: 2273) Memory: 10.0M CGroup: /system.slice/hestia.service └─1111 nginx: worker process Apr 10 12:25:22 vps43.heliohost.us hestia[187706]: * Starting hestia-nginx hestia-nginx Apr 10 12:25:23 vps43.heliohost.us hestia[187710]: nginx: [emerg] bind() to 0.0.0.0:8083 failed (98: Address already in use) Apr 10 12:25:24 vps43.heliohost.us hestia[187710]: nginx: [emerg] bind() to 0.0.0.0:8083 failed (98: Address already in use) Apr 10 12:25:24 vps43.heliohost.us hestia[187710]: nginx: [emerg] bind() to 0.0.0.0:8083 failed (98: Address already in use) Apr 10 12:25:25 vps43.heliohost.us hestia[187710]: nginx: [emerg] bind() to 0.0.0.0:8083 failed (98: Address already in use) Apr 10 12:25:25 vps43.heliohost.us hestia[187710]: nginx: [emerg] bind() to 0.0.0.0:8083 failed (98: Address already in use) Apr 10 12:25:26 vps43.heliohost.us hestia[187710]: nginx: [emerg] still could not bind() Apr 10 12:25:26 vps43.heliohost.us systemd[1]: hestia.service: Control process exited, code=exited, status=1/FAILURE Apr 10 12:25:26 vps43.heliohost.us systemd[1]: hestia.service: Failed with result 'exit-code'. Apr 10 12:25:26 vps43.heliohost.us systemd[1]: Failed to start LSB: starts the hestia control panel. No idea, what this means. Is the problem related to nginx? This service is running; I did a sudo service --status-all and otherwise the website would not work, I suppose... Thanks for any suggestions. And in the eventuality that I'll give up (the SSL certificate expires in June and I suppose that without Hestia there is no possibility to renew it), thaks for having had the opportunity to be part of this without any doubt best community on the net!

If I correctly understand, this means that the only reasonable action to take would be to start from scratch: backup, request to rebuild the VPS, reinstall of Hestia CP (or other control panel), manual reconfig of all servers, restore... 2023 is without any doubt one of the worst years in my life and I think that there's no chance to find the force, will and patience for this... So, what can I do: 1. Nothing at all. Letting the site running without Hestia (is there a possibility to check if Hestia is entirely dead?) until the website breaks down, too. 2. Migrating back to Tommy. No idea if this is possible!? 3. Doing nothing and migrating back to Tommy when the website breaks down (if this possibility exists). 4. Accept that if you haven't the necessary knowlege, you shouldn't install a VPS. Or even, that if you haven't the necessary means, you shouldn't create a website. Or, even further, that if you live in the street, you shouldn't try to live a "normal-people-like" life. I suppose that I will do the same that I've done for lot of things these last 12 months: Doing nothing and waiting what happens... Important however: I guess that a broken Hestia could result in security issues. If these issues could affect the HelioHost network or other user's website, please, let me know. In this case, I'll shut my site down, of course.

I finally tried to update the certificate via SSH and got the message "ERROR: Restart of Hestia failed". So, I suppose that Hestia is dead!? To follow your advice, am I right that I'll have to do the following: 1. Backup (home directory, databases, anything else?). The databases may be saved using phpMyAdmin, but for the filesystem backup, how should I do? Is there any software that you'd recommend? 2. Install another webinterface. The big question here is: How does that affect my website? Will the servers be re-installed? Will their presence be recognized and they therefor automatically added to the new panel? Or, have I to add them manually? Redo the configuration that I did when installing Hestia (that did all server installation + basic configuration)? 3. Remove Hestia. No idea, how this can be done. And what are the effects? As Hestia installed all servers, is there a risk that some servers will be uninstalled, too? Will the servers continue to run correctly when Hestia is uninstalled (I guess so, as they do now, where Hestia seems to be definitively dead)? And another important question: What about HTTPS? Will I further get SSL-certificates for free (I think that until now this was linked to Hestia)? Sorry, to bother you with all these questions. But, I think that I haven't another choice than to do something. Searching the Internet for solutions is not a good idea: It's too important to fall on some "wrong information". So, the only possibility, I see, is hoping for help (advice, suggestions...) from the HelioHost forum members... Big thanks in advance!

I know for several months that I have to backup my VPS and to update Hestia CP. One of the reasons why I didn't do it, is that I fear to mess up a well running website. When I tried to access the Hestia CP webpage on my VPS this morning, Firefox complained that the SSL certificate's validity has ended for some time. Is it normal that certificates aren't automatically renewed? I don't think that I ever did it manually... The problem seems to be limited to Hestia CP. All servers on my domain seem to work correctly. And the webserver at myvps.heliohost.us also works. I have no idea what the problem could be. And no idea what I must, should or can do to solve it. But, must I do anything at all? I practically never use Hestia, uploading my files using secure FTP, viewing statistics or other files after downloading them. Is there a problem just letting all as it is (maybe installing another webadmin interface later)? Can I get problems because all servers were actually installed by Hestia? Is the SSL certificate for my domain renewed without Hestia being working? Sorry, if these are stupid questions. But my sysadmin knowlege is more than limited and winter is not really a good time to do sysadmin work, if you mostly have to use some Internet connections outside. Thanks for any suggestions.