Jump to content

Krydos

Chief Executive Officer
  • Posts

    26744
  • Joined

  • Last visited

  • Days Won

    954

Krydos last won the day on July 21

Krydos had the most liked content!

About Krydos

Profile Information

  • Gender
    Male

Recent Profile Visitors

105043 profile views

Krydos's Achievements

Grand Master

Grand Master (14/14)

  • Reacting Well Rare
  • Well Followed Rare
  • Very Popular Rare
  • Conversation Starter Rare
  • Dedicated Rare

Recent Badges

2.1k

Reputation

  1. Ok, I'm not sure why your Wordpress install disappeared then. I assumed you installed it after the move started.
  2. The email you received when the move began explained If you can suggest a clearer way to explain that would have helped you and others to understand the issue, we would appreciate the feedback. It appears as if you've been deleting the Softaculous installed files via File Manager. This messes up Softaculous because the files it expects to be there are suddenly missing. If you wish to remove an installation that was installed via Softaculous we strong recommend using the delete button inside Softaculous so that the state of the files and installs remains in sync. Softaculous thought there was a Wordpress install in httpdocs/wp, a Concrete install in httpdocs/conc and another Wordpress install located in httpdocs/main but all of these files were deleted without using Softaculous delete button. I was getting the same error as you even after cleaning up the mess. This is why we invite beta testers to test out the new server before we start bulk moving all of the accounts to the upgraded server. There was an issue with Softaculous connecting to MariaDB. It seems to be fixed now, and I was able to install Wordpress successfully on your account which can be seen at https://phoule.helioho.st/wp/ If you want to delete it please remember to use the delete button inside Softaculous, not just deleting the files through File Manager. Thanks for helping to test the new Tommy2 server, and finding an issue that needed to be fixed.
  3. Remote access enabled. host=65.19.154.93 port=5432 user=elkhaddir_us dbname=elkhaddir_data password=<set in Plesk> Make sure you ask for the PostgreSQL username and PostgreSQL database name before you escalate these. In this particular case, the user only has 1 database user and 1 database so it was easy to figure out, but most of the time there are multiple users and multiple databases so we can't just guess.
  4. It looks like you sent an HTML email without the <html> tag Send a real email and it should be a 10/10.
  5. DKIM, SPF, and DMARC have been set up for the domain interworldmusic.qzz.io. 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.
  6. Closing due to inactivity since there has been no response in this thread for over a week. If you're still having this issue or need help with something else please open a new ticket.
  7. Cool. Let us know if you need help with anything else.
  8. Alright, the additional FTP accounts have been recreated. Are you able to login to them all, and are they jailed to the correct directories?
  9. Was there a problem with this link? I don't see any record of it being used.
  10. Are these FTP accounts supposed to be jailed to some subdirectory or have access to your whole account?
  11. I've unsuspended your account and started you moving to Tommy2. Let us know if you notice an improvement in speed, and a reduction in 502 and 504 errors.
  12. 99% of the CPU usage is from systemd which primarily comes from cron jobs and SFTP. If you missed the news post and the email from yesterday, we have a new server named Tommy2 that we're going to be moving everyone to. That should solve the 502 and 504 errors. Are you interested in moving over to the new server now or do you want to wait a bit?
  13. Is this a real business or is it a demo site? You can read more about the free trials at
  14. Krydos

    Tommy Upgrade

    Tommy is getting upgraded! Johnny may have thrown a tantrum and demanded to jump ahead of his place in line, but our exclusive donor server hasn't been forgotten, and is finally going to get even faster and even more up-to-date. We will be starting a major upgrade soon, and wanted to let you know what to expect. What is changing: PHP: All of the versions of PHP currently available on Tommy will still be available after the upgrade. Node.js: We are adding versions 26 and 25. All other versions of Node.js currently available on Tommy will remain available after the upgrade. Python: We are adding version 3.14. Version 3.9 will remain the same. Version 3.12 will be removed. Django: We are adding version 6.0.7 running on Python 3.14. We are removing version 6.0.3 running on Python 3.12. Flask: We are adding version 3.1.3 running on Python 3.14. We are removing version 3.0.3 running on Python 3.12. MariaDB: We are adding version 12.3. We are removing version 10.5. PostgreSQL: We are adding version 18.4. We are removing version 13.23. Unfortunately, we don't have a way of tracking which accounts are using which Python modules right now. So if you're using any modules, please take a look at https://tommy2-info.heliohost.org/pyinfo/info3.14.py as soon as possible, and request any modules that you'll need that aren't already available. In the future, we plan to add a system for tracking which modules each account needs, allowing us to pre-install them before an account is moved. For now, you will need to re-request them. You can use this link https://helionet.org/index/forum/45-customer-service/?do=add to let us know if any modules you need are missing. Another thing to keep in mind during an upgrade like this is that your IP address will be changing. If you use our nameservers, ns1.heliohost.org and ns2.heliohost.org, your DNS records will be updated to the new values for you. If you use external DNS, such as Cloudflare, you'll need to manually update your DNS records yourself. You will receive an email with the correct values when it's time to change them. If you don't want downtime due to incorrect DNS records, you could temporarily use our DNS until you're moved, and then go back to the external DNS afterwards. You will receive an email when your account begins its migration to the new hardware, and a second email when the move has completed. We are taking volunteers to be the first ones to experience the upgraded speed and features, so if you're ready to move, let us know. If you need a little more time to make sure your website is ready for the upgrade, let us know, and we can move you to the end of the list too. If we don't hear from your we will assume you're ready to move now. Let us know if you have any questions.
  15. Reverse DNS set.
×
×
  • Create New...