Krydos

DKIM, SPF, and DMARC have been set up for the domain hdrtattoo.helioho.st. We recommend sending a test 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 can purchase a dedicated IP for $2 per month, or save $4 by purchasing a year for $20. Your reputation will be entirely based on your emails alone, because no one but you will be sending emails from it. If we could give you a free dedicated IP we would, but we have to pass our costs along to the end user. Yes, these are available for all HelioHost accounts. We have had a few people request 2FA for their HelioHost logins, and we plan on implementing it eventually. You can set a password for each email account, but I'm not sure you can set multiple passwords for the same email address. Spam assassin is already available for all email accounts hosted on our servers. The first gigabyte is free on Johnny, or $1 on Tommy. If you need 2 GB they can be purchased for a one-time donation of $5 on either Johnny or Tommy. The maximum storage available on Johnny or Tommy is 6000 MB, but we plan on increasing that to 7000 MB in early 2025. You can send 50 emails per day, and receive an unlimited number of emails per day. The send limit can be raised as well if needed. TLDR: We already have everything you listed except app specific passwords for email accounts and 2FA, but we're planning on adding 2FA eventually. For what you described it would be $6 setup fee, and then $20 per year after that.

I'm guessing that is a PayPal error. I recommend contacting PayPal support, or trying a different card or something.

Your subscription has been canceled and you won't be billed again. Thank you for using our VPS service.

Yeah, that should work to forward them all into 1 email account for Gmail to download from. No clue if it would count towards your 50 emails to day limit. Try it and find out I guess.

Your rebuild has been started and you'll get an email in about 20 minutes when it's done. Your next free rebuild will be available on or after 2024-11-09. If you need additional rebuilds prior to that date they can be purchased for $1.00 each. Let us know if you want the link to pay for another rebuild, or if you need help with anything else. We can also install a free web based control panel on your VPS for you if you aren't too familiar with SSH so you can set up your website with your browser. Keep in mind that control panels must be installed on a completely empty fresh OS install though, so if you install some other stuff, and then decide you want a control panel we would need to do another rebuild first before the control panel could be installed. The most popular free control panel is Hestia https://hestiacp.com/ but a lot of users like KeyHelp https://www.keyweb.de/en/keyhelp/keyhelp/ as well. Plesk can be installed on a VPS as well, but it isn't free and it would add $15.50 per month https://www.plesk.com/pricing/ to the cost of your VPS for a total of $19.50 per month.

The problem with forwarding emails automatically through our servers is if someone sends you spam, and then you forward it to Gmail, or any other email provider, and they decide it is spam then Gmail blocks our server for sending spam. They don't care if it's forwarded or not. They see the spam coming from our server and the thousands of other users sharing an IP with you can no longer send emails to Gmail addresses anymore either. Do you think it's fair for some other user to remove your ability to send emails to Gmail because they are forwarding spam that is sent to them through their account and off to Gmail? Why don't you use some external email provider if you insist on forwarding spam? Why don't you just set up an email client to connect to our server and read the spam you receive directly rather than forwarding it somewhere else to get our whole server blocked?

The database has been running 12 hours with the current settings, and there is still zero swap usage. I think 6 GB memory, 8 CPUs, and 50 GB storage will be good for your website. I applied the 10% discount for the 6 month subscription, and you can pay with this link https://heliohost.org/vps/pay/?code=qgo8KlUulGNV2QxU

I did a little research on wsgi logs and it basically boils down to: Some types of errors go to the virtualhost log, which you have access to, and other types of errors go to the main system error log, which you do not have access to. It is not possible to securely give you access to just your parts of the main system error log because it contains the private information of thousands of other people on the server. So, the reason your other project was putting its errors directly into the log you have access to is because it was the right type of error. The type of error I posted above apparently always goes into the main system error log. So fix the above error and the rest of your errors should hopefully go into the log you can see.

Plesk still isn't filtering the new logs correctly either [Wed Oct 09 02:20:41.641245 2024] [wsgi:error] [pid 4180750:tid 4180815] [remote x.x.x.x:55078] mod_wsgi (pid=4180750): Failed to exec Python script file '/home/ujcis.helioho.st/alutagram.helioho.st/flask.wsgi'. [Wed Oct 09 02:20:41.641414 2024] [wsgi:error] [pid 4180750:tid 4180815] [remote x.x.x.x:55078] mod_wsgi (pid=4180750): Exception occurred processing WSGI script '/home/ujcis.helioho.st/alutagram.helioho.st/flask.wsgi'. [Wed Oct 09 02:20:41.642342 2024] [wsgi:error] [pid 4180750:tid 4180815] [remote x.x.x.x:55078] Traceback (most recent call last): [Wed Oct 09 02:20:41.643060 2024] [wsgi:error] [pid 4180750:tid 4180815] [remote x.x.x.x:55078] File "/home/ujcis.helioho.st/alutagram.helioho.st/flask.wsgi", line 7, in <module> [Wed Oct 09 02:20:41.643104 2024] [wsgi:error] [pid 4180750:tid 4180815] [remote x.x.x.x:55078] from myapp import app as application [Wed Oct 09 02:20:41.643155 2024] [wsgi:error] [pid 4180750:tid 4180815] [remote x.x.x.x:55078] File "/home/ujcis.helioho.st/alutagram.helioho.st/myapp.py", line 12, in <module> [Wed Oct 09 02:20:41.643181 2024] [wsgi:error] [pid 4180750:tid 4180815] [remote x.x.x.x:55078] db = SQLAlchemy(app) [Wed Oct 09 02:20:41.643199 2024] [wsgi:error] [pid 4180750:tid 4180815] [remote x.x.x.x:55078] ^^^^^^^^^^^^^^^ [Wed Oct 09 02:20:41.643241 2024] [wsgi:error] [pid 4180750:tid 4180815] [remote x.x.x.x:55078] File "/usr/local/python3.12/lib/python3.12/site-packages/flask_sqlalchemy/extension.py", line 278, in __init__ [Wed Oct 09 02:20:41.643265 2024] [wsgi:error] [pid 4180750:tid 4180815] [remote x.x.x.x:55078] self.init_app(app) [Wed Oct 09 02:20:41.643306 2024] [wsgi:error] [pid 4180750:tid 4180815] [remote x.x.x.x:55078] File "/usr/local/python3.12/lib/python3.12/site-packages/flask_sqlalchemy/extension.py", line 373, in init_app [Wed Oct 09 02:20:41.643331 2024] [wsgi:error] [pid 4180750:tid 4180815] [remote x.x.x.x:55078] self._apply_driver_defaults(options, app) [Wed Oct 09 02:20:41.643373 2024] [wsgi:error] [pid 4180750:tid 4180815] [remote x.x.x.x:55078] File "/usr/local/python3.12/lib/python3.12/site-packages/flask_sqlalchemy/extension.py", line 627, in _apply_driver_defaults [Wed Oct 09 02:20:41.643412 2024] [wsgi:error] [pid 4180750:tid 4180815] [remote x.x.x.x:55078] os.makedirs(app.instance_path, exist_ok=True) [Wed Oct 09 02:20:41.643456 2024] [wsgi:error] [pid 4180750:tid 4180815] [remote x.x.x.x:55078] File "<frozen os>", line 225, in makedirs [Wed Oct 09 02:20:41.643560 2024] [wsgi:error] [pid 4180750:tid 4180815] [remote x.x.x.x:55078] PermissionError: [Errno 13] Permission denied: '/home/ujcis.helioho.st/alutagram.helioho.st/instance' It looks like your Flask app is trying to create a new directory and getting denied due to permissions. In order to create a directory you probably need to give 777 permissions to the directory above it, but why are you trying to create a directory anyways? Seems kind of odd. Just create the directory yourself through SFTP or Plesk File manager and it will be 10,000% easier.

This guide is for Flask which uses WSGI. This guide is for Python CGI. CGI and WSGI are two very different mechanisms for running Python code. Which are you trying to do exactly because they aren't the same thing, and it was never intended to do both guides at the same time?

WSGI control access has been enabled on the domain alutagram.helioho.st. To restart your Flask app and load new code changes in simply edit /home/ujcis.helioho.st/alutagram.helioho.st/flask.wsgi. Adding a blank line, removing a blank line, adding a space, or removing a space are examples of editing the file. As long as the last modified timestamp changes it will clear the server cache. Let us know if you run into any issues.

After the changes, and letting MariaDB run overnight you were using 900 MB of swap, as expected. I increased your memory another 1 GB, and we'll let it run for a while again. The performance is already looking a lot better, and giving MariaDB more memory to work with is definitely reducing the disk I/O. The other good news is even though you were using some swap this morning, your load was about 0.90 which is under the 1.00 that I was targeting.

You can have up to 10 domains on your 1 account for free. Would you like us to add another free domain, and see if putting the second project on its own domain fixes the logs?

I ran the tuner and made some adjustments. MariaDB will likely use more memory now, so if your free memory drops too low the load may spike high and things may seem slower than before. That is our indication to add more memory to the server. One of the changes I made should make it easier to analyze the performance, but the database needs to run without a restart for at least 24 hours before we can run the tuner again. If your site gets too slow within those 24 hours please let us know and I can add some more memory.

I took another look at your VPS, and the memory looks pretty good. The load is still a little higher than I would like though. It's bouncing around between 2.5 and 3.0. Like I said a few weeks ago it would be best if it was below 1.0. I think the largest bottleneck right now is the disk I/O. Since your database is so large MariaDB can't load very much of it into memory at a time so it has to constantly read and write from the hard drive. If you want I could run a database tuner on your VPS to see if we can squeeze a little more performance out of the database settings. Most likely, since your database is so large, the tuner will tell us that it needs more cache space, which would require increasing the memory on the VPS again. We've already got you on the fastest hard drives we own, but memory is thousands of times faster than even the fastest hard drives, so the more data MariaDB can hold in memory the less slow reading and writing to the hard drive would occur. I have converted your VPS to a 6 month plan and applied the 10% discount. You can set up a subscription with this link https://heliohost.org/vps/pay/?code=8Lk5SWqTry3oGpcr but if you do want to run the tuner, and most likely increase the memory again, it might be better to hold off on setting up the subscription for a day or two because increasing the memory will change the price for the subscription.

Does the logs for the second project work if you delete the first project?

You used 116% of your daily memory allowance in 81 minutes. If you hadn't gotten automatically suspended you would have used about 2062 GB of memory over 24 hours at that rate, when the limit is 100 GB per 24 hours. That's more than 20 times what you're allowed to use on the $1 plan. If your website wasn't even online yet I can't imagine the load is going to get smaller with more visitors. Perhaps you should look a VPS for this website instead? https://heliohost.org/vps/

During the recent upgrade of the Tommy server we identified a bug partway through the move that caused SFTP to not work correctly after the account was on the new server. We fixed the bug in the move process, but several hundred accounts were moved prior to the fix. If your account was moved early in the migration, SFTP probably hasn't been working for you for the last week or so. We're happy to announce that all of the accounts on Tommy should now have functional SFTP again. If you're still having issues please let us know so we can take a closer look at your particular account.

Does it work now?

If you're going to run commands designed to be run on a VPS you should get a VPS to run them on https://heliohost.org/vps/ If you want to use Node.js on the free shared hosting you should follow the guide that we wrote to use Node.js on the free shared hosting https://wiki.helionet.org/tutorials/node.js

It looks like you started these two processes npm run start node index.js and they were running up until 2 hours ago. When you start processes that never exit they ... never exit. If you want to run a Node.js website we strongly recommend following the guide that we wrote https://wiki.helionet.org/tutorials/node.js It uses Passenger which means if you don't get any page hits for 5-10 minutes your Node.js processes are killed and when someone views your website again they are started again. Unless you are getting constant visitors to your website every few minutes it will save you massive amounts of memory usage. If you follow some random Node.js guide on the internet they will most likely tell you to run a command like the above that never exits, and you will most likely end up suspended. If you didn't run the above commands then you should change your password because someone else has access to your account.

Remote access enabled. host=65.19.154.90 port=5432 username=pyepezc1_pabloDB dbname=pyepezc1_EnsayoDB password=<set in Plesk> host=65.19.154.90 port=5432 username=pyepezc1_pablo dbname=pyepezc1_album password=<set in Plesk>

It was fixed for everyone who was moved after you. You haven't been moved again since the fix.

Remote access enabled. host=65.19.154.90 port=5432 username=peterlasvera_admin dbname=peterlasvera_dacen password=<set in Plesk> We do plan on adding remote PostgreSQL copying when moving between servers in the future so you won't have to request it again.