Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 05/23/26 in all areas

  1. The free plan is now back, and better than ever! The Johnny rebuild has been completed and free signups will be opening in about 30 minutes. If you don't already have an account you can signup at https://heliohost.org/signup/ We expect signups to fill pretty quickly, so be ready to click as fast as you can. On May 9th we emailed all of the active Johnny users, and offered them a free trial on Morty to get their websites back online during the rebuild. If you are one of those free users currently on Morty we will be emailing you to ask if you want to stay on Morty or go back to Johnny. If you want to stay on Morty you can use this link https://buy.stripe.com/7sI8wOe4p40y9q0147 to pay $5 which will last about 6 months without overages. If you make a payment let us know so we can make sure it gets applied to your account. If we don't hear back from your we will move you to Johnny automatically in a few days. If you decided not to accept a free trial, you can recreate your Johnny account by going to https://heliohost.org/status/ and entering your email or username. The website will recreate your account for you on the new Johnny server. The new account will be empty so if you want to restore your previous website you'll need to download your backup from https://heliohost.org/backup/ or use a backup that you made yourself. Keep in mind that if your backup is missing anything we may still be able to recover it for you. Just let us know what you're missing, and we can take a look. The new Johnny also has a number of upgrades such as Python 3.14, MariaDB 12.2, PostgreSQL 18.4, etc. If your script isn't working, make sure you're using the correct shebang version. Let us know if you have any questions.
    2 points
  2. Hello! I've added those domains to your account for you. Please note that it may take up to 2 hours for the domain changes to take effect. If after a full 2 hours they don't work on your side, please make sure you clear your web browser cache: https://wiki.helionet.org/Clear_Your_Cache
    1 point
  3. Thank you, fortunately, I'm not one of them. Because asking on this forum is the last thing I'd do before exhausting all of my options :))
    1 point
  4. Cool, sounds good. I'm going to mark this as solved, but I understand that webstats still isn't working on Tommy. It's not worth trying to fix it since we're going to be replacing the old Tommy server anyways soon.
    1 point
  5. The domain theclippercampaign.org has been added with a redirect to theclippercampaign.com. Yes. 1. Redirect .org to .com 2. Redirect .com to .org 3. No redirect. 301 permanent redirect https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Redirections
    1 point
  6. Yeah, that IP is not blocked. Seems like they noticed the loophole you were using and blocked it.
    1 point
  7. I've added those domains to your account for you. Please note that it may take up to 2 hours for the domain changes to take effect. If after a full 2 hours they don't work on your side, please make sure you clear your web browser cache: https://wiki.helionet.org/Clear_Your_Cache When we load tested Moodle, it caused a lot of load so the risk of suspension is high. Please make sure to keep a very close eye on your account load if you use Moodle. You can check your account load here: https://heliohost.org/dashboard/load/ You can check out the load testing report here, showing the results for Moodle in the table: https://wiki.helionet.org/Common_Software_Load
    1 point
  8. non-WordPress domain on this account) That's why I missed it...that domain has node instead. When I went through the domains, I saw that one had node enabled and just skipped over it, as I was focused on the WP stuff. Good news is that those files, while definitely malicious, likely would not have been able to run anyway since you had Node enabled (passenger redirects everything to node when enabled on a domain, so Apache never gets to run the PHP files). The interesting part is that the index.php is clearly meant for a nonexistent WP on that domain, and the mac.php looks like it may be the same or a very similar file to a file called bless24.php that was on the compromised lda.ng domain (I recognize this string from the top: xtamdxsirm from the other day).
    1 point
  9. This support request is being escalated to our root admins.
    1 point
  10. Krydos can install this for you.
    1 point
  11. Thank you, I am forwarding him how to archive the account.
    1 point
  12. 1 point
  13. I'll go ahead and mark this as [Solved] since there are no outstanding queries for support. If you run into any issues, please open a new ticket. Thanks!
    1 point
  14. Yes, the Johnny server allows up to 5 domains. If you need more than that, you could upgrade your account to the Tommy server, which allows up to 10 domains. If you need even more domains, your next upgrade option would be the Morty server, where you can have up to 15 domains on a single Morty account. On Morty, you can have more than 1 account too, so if you make 2 Morty accounts, you can host 30 domains, etc. You could also upgrade to a VPS which also allows for multiple domains to be hosted, once you set up the DNS. There was an issue when I tried to add the domain, but it's being worked on. Once added, an admin will post here to confirm it's been added for you.
    1 point
  15. Plesk generates the private key for the DKIM and stores it securely along with the private keys for SSL. When you send an email from Plesk with DKIM enabled it Plesk uses the private key to generate a DKIM signature that remote mail servers can use the public key provided via DNS to verify that the email is legitimate.
    1 point
  16. Please do not post multiple topics for the same issue. Requests can take up to 24 hours to receive a response.
    1 point
  17. Please do not create multiple topics for one request. Posting more than one topic on the same request/issue can result in a delay in service to you. You already posted here:
    1 point
  18. DKIM, SPF, and DMARC have been set up for all your domains.
    1 point
  19. That's good to know. Those files can vary quite widely by server version and database content, so the fact an off the shelf AI can convert the binary InnoDB database files back into .sql format without issue is quite impressive. Thank you for the info.
    1 point
  20. Nope not mistaken. An alias is exactly what you need if you don't want it to redirect. Alias has been added. Please be sure to configure DNS using our name servers or by using A and AAAA records pointed to the IPs shown in Plesk. The alias can take up to 2 hours to function.
    1 point
  21. .htaccess file is going to be your best friend here as moneybroz said above. We've had to block these scanners on our own sites as well as help other users with the same (usually on our other plans after they got suspended over it).
    1 point
  22. No, the backup from May will not contain databases. We were only able to recover the contents of the Home folder as of the day of the crash. The database server was damaged by the crash and associated disk issues, and the majority of the data was lost. If anything at all is recoverable, it's going to be raw server files that represent the table, and you'll need to spend some time trying to extract the data from them. The data will not be something that you can just import into a new account. Escalating to Krydos.
    1 point
  23. Sorry for the delay. I've been travelling the last few weeks, and somehow managed to miss this one. The requested DNS record has been added. In the future, if you don't receive a reply within 24 hours we encourage users to bump their support requests to make sure we don't miss it.
    1 point
  24. Great to hear you enjoyed the experience here and learn something from it! You should be able to cancel your VPS here: https://heliohost.org/dashboard/cancel/ If that doesn’t work, let us know and I’ll have Krydos cancel it for you.
    1 point
  25. Installed. You can see the current list of modules and their versions for Morty's Python 3.14 at https://morty2-info.heliohost.org/pyinfo/info3.14.py
    1 point
  26. DKIM, SPF, and DMARC have been set up for the domain dark.helioho.st. We recommend sending a real email (not just the word "test" or a blank email) to https://www.mail-tester.com/ to make sure that everything is set up correctly. If you get less than a 10/10 score please post a link to the full report so we can help you fix any other issues that there may be. You suspect correctly. It supports Johnny domains now.
    1 point
  27. Remote access enabled. host=65.19.154.90 port=5432 user=dvdbrugnoli_RestaurantManagerADMIN dbname=dvdbrugnoli_RM password=<set in Plesk>
    1 point
  28. Correct. SQLite3 is actually built into every Python 3.14 by default too, but we recommend using MariaDB or PostgreSQL because they're easier to get working, and better performance. This module is really ancient and doesn't even work with Python 3.0. For Python 3.14 I installed Beautifulsoup4 instead. You can see the current list of installed modules for Johnny's Python 3.14 at https://johnny-info.heliohost.org/pyinfo/info3.14.py
    1 point
  29. The configuration we recommend is to use the server hostname (tommy.heliohost.org in your case) as the mail server. Plesk loves to suggest using user domains for the mail server, but our experience is that it tends to cause issues. SSL connections for mail not working is a common problem with doing so, and another is that mail clients may refuse to send mail through it for security reasons (the server identifies itself as Tommy regardless of what domain you use to connect, some clients do not like the fact the domain in its settings and the domain the server identifies as don't match).
    1 point
  30. Weird. The system is unable to set up SPF/DMARC/DKIM on that domain. Keeps saying it can't find it despite the domain obviously existing. Based on the output, I suspect the DKIM setup tool on our side may not be capable of setting this up on Johnny domains (probably due to the rebuild). Flagging for Krydos...
    1 point
  31. Also, please note that once you change it in Plesk it can take several hours before the dashboard reflects the change.
    1 point
  32. You can do this yourself in Plesk > Click your username > Edit Profile and change the external email listed to the new one.
    1 point
  33. An administrator will be able to do this for you.
    1 point
  34. DKIM, SPF, and DMARC have been set up for the domain kittforhire.com. We recommend sending a real email (not just the word "test" or a blank email) to https://www.mail-tester.com/ to make sure that everything is set up correctly. If you get less than a 10/10 score please post a link to the full report so we can help you fix any other issues that there may be.
    1 point
  35. Domain changed. It may take several hours to start working.
    1 point
  36. I've changed the main domain on your account for you. Please note that it may take up to 2 hours for your new domain to fully work. If after a full 2 hours it doesn't work on your side, please make sure you clear your web browser cache: https://wiki.helionet.org/Clear_Your_Cache Please note there is a risk of data loss when main domains are changed, so I made a full backup for you before I made the changes, in case you need any files from the old domain. You can download the backup here: https://heliohost.org/backup If you're not sure how to extract the backup files, please follow our how-to guide here: https://wiki.helionet.org/Account_Backups
    1 point
  37. 2026/05/31 17:06:15 [emerg] 613206#613206: duplicate location "/" in /home/bawantha/conf/web/anonymizer.bawantha-beliwaththa.me/nginx.ssl.conf_flask.conf:1 It looks like you tried to add a custom nginx directive but you are trying to pass a location context to another proxy when Hestia already passes all traffic to Apache on port 8080, i fixed the error, and restarted nginx let us know if the error still persists. to add the proxy to port 5001 back, login to hestia, go to web and then click edit, on anonymizer.bawantha-beliwaththa.me, after that click Advanced options and then change the proxy template to python or node depending on what you are using, and then set 5001 in the backend port setting. i also made a backup of your code before making any changes which you can find in /home/bawantha/
    1 point
  38. Oh yeah, that domain could be an issue if changing it means having to update/replace the firmware on old embedded devices. I'll put it back for now for you as an alias so you have both. It could take up to 2 hours to work, and will show the same content as the .us domain. In the meantime, please update your service/documentation so that new users and updates going forward will access your service through the .us domain instead. There will eventually be a point where we eliminate the remaining .org domains from user accounts.
    1 point
  39. Thanks for quick reply and Morty2 information. What a difference between free and paid in performance and uptime! I am loving Morty and I am sure I will love Morty2 even more.
    1 point
  40. 24 hours... 😓 Well, now we know if someone else has trouble with git, I guess! Glad it's all sorted out! 🙂
    1 point
  41. Thank you so much for your help! I wanted to let you know that the repository has finally loaded. It took about 24 hours to finish, but it is no longer stuck in the queue. Since it loaded, we won't need to do the account reset. Thank you again for your support!
    1 point
  42. Domain added. It can take up to 2 hours to start working.
    1 point
  43. Sure. That domain has been added back.
    1 point
  44. thank you for all your hard work 🙏🏻
    1 point
  45. Domain changed. It can take up to 2 hours to function.
    1 point
×
×
  • Create New...