Jump to content

allu62

Members
  • Posts

    128
  • Joined

  • Last visited

  • Days Won

    2

allu62 last won the day on July 30 2023

allu62 had the most liked content!

1 Follower

About allu62

  • Birthday 04/19/1962

Contact Methods

  • Website URL
    https://www.streetinfo.lu

Profile Information

  • Gender
    Male
  • Location
    Luxembourg

Recent Profile Visitors

1,603 profile views

allu62's Achievements

Enthusiast

Enthusiast (6/14)

  • Reacting Well Rare
  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done Rare

Recent Badges

6

Reputation

  1. The subscription is paid. If you don't find it, please, let me know, and I'll post the transaction number. Thanks a lot, and sorry again that I was some days too late. A nice day to the whole team!
  2. Hi. I think that the subscription for my VPS has ended some days ago. I'm really sorry, but I didn't pay attention and did not check the date, where I have to renew. The VPS is still running (big thanks). Can you please post me a link, where I can renew for another 6 (or 12) month (remember that I can't make an automatically done payment each 6 months, because it's not me paying myself). Sorry again, and thanks for the link (it's ok for me to pay a penality for not having been within the delays...).
  3. Thanks, Krydos. Everything OK again, including PHP. If you think that it's reasonable to let everything as is, that's really fine for me. The "Unable to connect" was probably due to a WiFi hotspot that blocks port 8083. Yes, and now a nice example that demonstrates that computers are sometimes more magic than science: For the first time during months, Hestia CP is entirely functional again! I could access the control panel, all was OK, except for spamassassin not running. No problem to start it...
  4. Hi, Krydos. Have you run any fixes on my VPS? I ask, because my website is up again! How is this possible? You said that my VPS is not on the server affected by the filesystem scan. So, what may have changed? I just tried to access the site; it not only works but response time seems better than usually. Static content, Perl and MySQL is all OK. Only PHP seems not to work anymore (I get an error 500 with my directory listings). Another thing that has changed is that https://vps43.heliohost.us:8083/login/ doesn't give an errror 500 as it did before, but an "Unable to connect" message from the web browser. Have you an idea what that means? Having in mind that it's really not the moment for me to stress myself with admin tasks, what would you suggest? Letting all run as it is? Updating Ubuntu and/or Hestia? How great is the risk that doing so will "kill everything"?
  5. If Krydos thinks that he can fix the problem in less than 40 minutes, it's ok. Otherwise, I think that the best solution is to delete all my webdata on your servers and cancel the accounts allu and allu62. Thanks for, during some 5 years (I think), you have given me the impression to exist, to be a real human being. Thanks to everyone in this really great community who gave me some advice and suggestions during this time.
  6. Maybe you remember that I couldn't access my VPS because of problems with Hestia (components not updating, nginx not working ...)? Well, I did a backup of the site some months ago, but I never started to find the problem with Hestia. So, I think that we can say that it was just a question of time before this happened. My fault! Starting with subscribing for a VPS. I should have known that I've neither the knowledge, nor the patience, nor the will to be a sysadmin. I guess that returning onto Tommy could be a solution. But, I think that perhaps the time has come to abandon my stupid idea to run a website. That the crash of the VPS happens at a moment where I've been another time betrayed by the social system of this f* country and where another time I am in a situation where I have to accept and to suffer without having any possibility to defend myself, even not to complain, is perhaps just a sign of the gods (whoever they are) that it's time for me to give up...
  7. Hello (after a long time). Yesterday evening still ok, I actually get a timeout for https://www.streetinfo.lu/ Pinging www.streetinfo.lu is ok, so no DNS problem... Can anyone, please, tell me if the site is down (it is hosted on vps43.heliohost.us)? Has anyone an idea what's the reason? What can I do/should I try? Thanks in advance for help...
  8. 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.
  9. 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.
  10. 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...
  11. 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!
  12. 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.
  13. 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.
  14. 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).
  15. 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!
×
×
  • Create New...