Krydos

Added. Since you're using Cloudflare make sure you create an A record with the value 65.19.141.77 and an AAAA record with the value 2001:470:1:1ee::2002

I started the rebuild earlier and then went out. When I got home I went to install Hestia for you, but it looks like you're logged in already installing stuff. HestiaCP needs a fresh OS without anything else installed so it's unlikely the install will succeed at this point.

Installed. Some comments though. First, you requested Flask 2.1.2 when Flask 2.2.2 is already installed. Since everyone on the server shares the same Flask version we don't downgrade any modules ever because that is almost guaranteed to break someone else's website. It's more likely that a newer version of a module is backwards compatible though. If it doesn't work for some reason you'll have to change your code to support the newer version of Flask. Second, Flask-MySQLdb cannot be installed because mysqlclient cannot be installed. The module mysql-connector-python is already installed so that is the way you'll need to connect to your database. It's kind of redundant to have 15 different MySQL modules that do exactly the same thing anyways. Finally, if you need any other modules installed please reference https://johnny.kairion.eu.org/pyinfo/info3.10.py first and only request modules that aren't already installed. It saves me quite a bit of time to not have to check 15 different modules that are already installed.

Are you able to connect to SSH now?

Thanks for the feedback. There aren't a lot of people that use Java, but it's definitely one of our most popular features. It also sets HelioHost apart from other hosting services because there aren't many that provide Java hosting for free.

I can enable ipv6 remote access if you need it, but for simplicity only ipv4 is enabled when remote access is requested.

Part of the reason that Tommy is overloaded is because there are too many domains hosted. Before I add any new domains to your account I would like to clean up any unused domains. purosdisenos.com.mx - Appears to not even be registered anymore. Can I delete it? gorisnic.kg.heliohost.org - Subdomains like this are just trash that cPanel created. Plesk doesn't need it. Are you using it for anything? If not can I delete it? purosdisenos.kg.heliohost.org - Same as above.

https://www.gofundme.com/f/heliohosts-morty-server We've made some great progress towards buying our new server. At this rate we'll probably have it purchased and set up before the end of the year. The last 25% is the toughest part of any fundraiser though. To the 63 people who have donated so far, we send out a huge thank you for supporting our cause to provide free or low cost hosting to those in need. We really appreciate you. To the 2035 active accounts who haven't donated yet, we have a question for you. What can we do to improve HelioHost that would make you consider donating too? We have hundreds of ideas and projects that we're working on, but we need your help prioritizing what should be done first. HelioHost is far from perfect, and small annoyances or lack of features are probably stopping some people from donating. Obviously we're still in the process of completely overhauling HelioHost so most of our services are pretty bare bones, and you need admin assistance for a lot of things still, but we've made a lot of progress over the last year. What should we do next to make HelioHost even better? Should we make adding domains without admin help the highest priority? Should being able to edit your own DNS records be the most important thing? Should we put more effort into making Tommy faster? Should we make Java available again on free hosting? Should we allow more free signups per day? Should we update our documentation to make complex tasks like Node.js and Discord bots easier to figure out? Should we make more YouTube videos? Should we make Ruby on Rails available on free hosting? Should we provide memory usage and CPU usage graphs in the dashboard? Should we make it so users can enable remote PostgreSQL access themselves? Should we implement password resets through our website rather than having an admin send you a link? Should we put more effort into accepting donation from more than just PayPal? Should we look into accepting cryptocurrency for VPS payments automatically instead of an admin having to verify it? Should we allow users to install Python modules themselves through the dashboard? Those are just some of the major ideas we're already working on. Is there anything else you can think of? We're going to have an amazing new powerful server soon, and we can use it to help make some of your visions come true.

The domain has been added, but in order to actually host it with us you must do 1 of the following 2 options. Use our nameservers by logging in to your registrar and setting your NS records to ns1.heliohost.org and ns2.heliohost.org Use any external DNS that you want, Cloudflare is a popular free option, and create an A record with the value 65.19.141.67 and an AAAA record with the value 2001:470:1:1ee::2009

Remote access enabled.

There you go https://cobvan.helioho.st/ Problems I found: Your domain was disabled. I assume you did that on purpose because of my warning that you had used 530 GB of memory in the last 24 hours. I re-enabled it. Node.js was disabled on your domain. Maybe this got disabled when you disabled the domain, but obviously Node isn't going to work while it's disabled so I re-enabled it. Your app.js file doesn't look anything like the guide. I assume you started with the wiki version and then just started randomly changing things and it evolved into what it was. I backed up your copy with the name app.js.bak and set app.js to exactly what the guide says to use. Most of your memory usage was coming from npm so I renamed package.json to package.json.bak in case it was interfering, and if nothing else it disables it so npm won't try to read from it or anything. It's not needed for the basic wiki guide anyways. The index.html file in httpdocs takes precedence over your Node app if it exists. I deleted it. Now that you have a working copy I recommend making small changes, and testing it frequently. Keep in mind that it gets cached, unless you hit the restart app button, so if you make some changes and they don't show up remember to restart it. A big mistake that most people make is just dropping in a Node app that wasn't designed to run on Passenger and expecting it to just work because "it works on my computer." As long as you make small changes you can see immediately when something goes wrong, revert it, and figure out why it's not working. Regarding the high load, 497+ GB of memory was from your random npm stuff. The Passenger memory usage was only 17 GB. Honestly, you don't ever have to run npm at all. Just download all the dependencies on your home computer and then upload the node_modules directory. Like I said on Discord, try to keep your memory usage under 200 GB per day. If you're curious how much memory you're currently using, just ask.

Added.

Added. Since you're using Cloudflare make sure you create an A record with the value 65.19.141.67 and an AAAA record with the values 2001:470:1:1ee::2009

Added.

If you're not too familiar with SSH command lines we can install a control panel for you. Plesk, like you have on Johnny is not free though, and would add $13.50 per month to whatever VPS plan you choose. So a Mercury VPS running Plesk with 1 GB memory, 2 CPUs, and 50 GB storage would be $17.50 per month total. We can also install a free control panel for you. The two most popular free control panels that people use are Hestia and KeyHelp. As far as moving your sites over you would basically just need to create a backup of your Johnny account and then extract the files and databases and whatever you need to upload to the VPS. We can help you with your DNS settings for moving your domains over.

Remote access enabled.

Remote access enabled.

Your subscription has been canceled so you won't be charged again, and your VPS has been deleted. Thanks for using our VPS service.

Oh wow, sorry about that baymin. Not sure how that one slipped through the cracks. We've actually been discussing the best way to make sure no posts get forgotten like this. The domain has been added.

Your VPS has been powered back on so you can take whatever backups you need. Let us know when you're done so we can delete it.

What user would you like to have remote access?

The most common issue I've seen with Hestia autoupdates is when the old Hestia process refuses to exit for the new process to start. This is the type of error you will see when that happens. The old process is already using the 8083 port so the new process can't bind to it. Yes, all Linux systems have a user named root.

I haven't used Hestia enough to know if it does automatic updates or not, but I'm guessing even if it does update automatically it only updates its own components, not the rest of the operating system. Running apt update && apt upgrade should be done yourself maybe once a month at the least. Be ready to fix something if it breaks though so don't run the update unless you've got an hour or two to fix anything that goes wrong. When the VPS is created the VPS admins, currently only Yashrs and myself, have root access to the system. You can remove access if you want, but if you ask for support we can get root access again easily enough. Leaving the access we currently have allows us to save about 15 minutes though per support request. As we get more VPS subscriptions we may train another admin to help, but for now it's just the two of us. Technically all of the root admins, Ashoat, Byron, Wolstech, and myself, have access, but since they're not all trained it's unlikely they'll ever need to. Our policy is we don't log in to VPS unless we have a good reason to believe that they are breaking our terms of service, their VPS has been hacked, or if someone asks for help.

There you go [root@control ~]# dig +noall +answer -x 65.19.191.154 154.191.19.65.in-addr.arpa. 21600 IN CNAME 154.subnet144.191.19.65.in-addr.arpa. 154.subnet144.191.19.65.in-addr.arpa. 14400 IN PTR mail.eason.email. [root@control ~]# dig +noall +answer -x 2001:470:1:1ee::71 1.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.e.e.1.0.1.0.0.0.0.7.4.0.1.0.0.2.ip6.arpa. 14400IN PTR mail.eason.email.

I ran the updates for your VPS. There were 150 packages that needed to be updated. I logged in via SSH and ran the commands sudo apt update sudo apt upgrade Which you can do yourself occasionally in the future if you want to. If the update asks you to keep your existing config or overwrite it I would select N for keep your existing config.