Leaderboard

HelioHost has released a new YouTube video on how to set up a Discord bot on any of our shared hosting plans, including the free Johnny plan. Check it out and subscribe at https://youtu.be/-9Q9SAONgtM Back in June 2021 we started a YouTube channel for HelioHost and began releasing videos on how to do various projects on our hosting. Our plan was to release a new video every 2 weeks, but then less than a month later we were forced to switch control panels. Since all of our systems, code, signup pages, and everything else were designed for our old control panel it was a massive undertaking to rewrite all of our websites and code to work with Plesk so we didn't have a lot of time to release new videos. Now that we're fully recovered, and our transition to Plesk is mostly done we decided it would be a good time to start releasing videos again. Please let us know if there is a specific topic that you think would be good for our next video. Also if you don't mind subscribing to our YouTube channel that would be a great way to get some free advertising. We are a small non-profit funded by donations so we don't have a huge budget to afford paid advertising, so the more word of mouth recommendations, the more social media likes, and the more subscribes we can get goes a long ways towards finding more users and continuing to grow. Even if you can't donate, this is a great way to help us for free. Thanks!

HelioHost has released a new YouTube video on how to install Nginx on a VPS. Check it out and subscribe at https://youtu.be/zHwWs7Tt2zc We are going to try to continue releasing new videos every 2 weeks, because some users find it much easier to follow a video guide rather than reading the text guides we have at https://wiki.helionet.org Please let us know if there is a specific topic that you think would be good for our next video. Also if you don't mind subscribing to our YouTube channel that would be a great way to get some free advertising. We are a small non-profit funded by donations so we don't have a huge budget to afford paid advertising, so the more word of mouth recommendations, the more social media likes, and the more subscribes we can get goes a long ways towards finding more users and continuing to grow. Even if you can't donate, this is a great way to help us for free. Thanks!

The discord/dmarc/dkim/atproto ones have names, so you need to actually ask for, for example, _atproto.tenkyuu.dev to see it. The file you posted is only the domain itself (i.e. records with no name or with the name of the domain). The root domain shows the same thing as your file: https://dnschecker.org/all-dns-records-of-domain.php?query=tenkyuu.dev&rtype=ALL&dns=google For the named ones, they do appear if you specify their names. For example, the _atproto and _discord ones: https://dnschecker.org/all-dns-records-of-domain.php?query=_atproto.tenkyuu.dev&rtype=ALL&dns=google and https://dnschecker.org/all-dns-records-of-domain.php?query=_discord.tenkyuu.dev&rtype=ALL&dns=google This is the expected behavior for the records provided.

Thank you!

Thank you!

Looks good if I check the actual DNS queries. Our admin tools still show (cloudflare) next to your domain which is why I said that. There's probably a stale cache somewhere on our side, but that shouldn't impact the domain itself since public DNS is showing the right name servers...it's just a UI issue in our admin tools...

You're using Cloudflare so you have to do this yourself. That said, the webmail and www CNAMEs exist already on our servers (they're standard) as well as the MX. The TXTs for the email stuff are generated by a script when you request SPF/DKIM/DMARC if you request email support, no need to supply values as our system generates them automatically. I've gone ahead and done this for you. I especially did not use that DMARC record. You'd be hating yourself if I did...you'll be spammed to all hell by the automated reports (and probably end up suspended for disk space, the ruf can get you thousands of emails a day!), and your sent mail likely won't deliver on reject as most providers already have enough trouble accepting our mail without us telling them to throw it away... This is your zone file on our side. You'll need to use our name servers though for it to actually do anything: $TTL 14400 @ 86400 IN SOA ns1.heliohost.org. heliohost4.gmail.com. ( 2025041701 ; serial, todays date+todays 3600 ; refresh, seconds 1800 ; retry, seconds 1209600 ; expire, seconds 86400 ) ; minimum, seconds tenkyuu.dev. 86400 IN NS ns1.heliohost.org. tenkyuu.dev. 86400 IN NS ns2.heliohost.org. tenkyuu.dev. IN A 64.62.151.106 tenkyuu.dev. IN AAAA 2001:470:1:1ee::2009 ipv6 IN AAAA 2001:470:1:1ee::2009 tenkyuu.dev. IN MX 0 johnny.heliohost.org. mail IN CNAME tenkyuu.dev. www IN CNAME tenkyuu.dev. ftp IN CNAME tenkyuu.dev. webmail IN A 64.62.151.106 webmail IN AAAA 2001:470:1:1ee::2009 tenkyuu.dev. IN TXT "google-site-verification=gP9DbLrjLTsnPdCxCB4aFindIrtjQTovp2uVO5OX_Ec" _atproto.tenkyuu.dev. IN TXT "did=did:plc:q74gsah26xz3q4qoe5ixx5jx" tenkyuu.dev. 14400 IN TXT "v=spf1 ip4:64.62.151.106 ip6:2001:470:1:1ee::2009 ~all" _dmarc 14400 IN TXT "v=DMARC1; p=quarantine" _domainkey.tenkyuu.dev. 14400 IN TXT "o=-" default._domainkey.tenkyuu.dev. 14400 IN TXT ( "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA+SDLc/Hl5PNixlC3Z1QqVI5F0WQUTC0wA2GHBtcHm+cqyRxqCWP7OmmV5Z7Vn3nos10c8TB7chpdkPiTVeO53mrpK6ZC9fjhlfFajdLReXJvRhqR+MBCwUEw1IimwFUz35YIRwqJ2bHaqvtjhuH4oOZ45qq79GB9gsc5OGC/A74pvZBOzMt1zYo3BvwUNo2LT" "gcyMDTunY+ZU15PBFyE34tj8iniPctiznyx+MboWzR4FCG/igoSwuksUm591bW8PblllmtUzdIQi7ORn9P+JO+bCW29gJlJ77wxupzvelwUMbi/iNWrCnyVbJVNxHxGQTu4jzvMg74BfIGZ1YErmQIDAQAB;" )

I believe this issue is already being handled in another thread: https://helionet.org/index/topic/64137-krydos-python-flask-500-internal-server-error/page/2/#findComment-288899 Please follow the above thread for further progress updates. All staff are volunteers. We all have full time jobs and lives outside of this project. We run this organization in our free time, and if we don't have very much free time things don't get done very quickly. Creating duplicate requests for help will only risk delays in enabling the volunteer staff to use their free time most efficiently in order to troubleshoot this for you: https://wiki.helionet.org/FAQ#Where_do_I_ask_for_help? Most for-profit hosting companies have a staff of full time employees who sit around providing support and working 40 hours a week. It's very rare for any of our volunteers to work more than an hour or so each day. None of our volunteers are required to log a certain number of hours and may come and go as they please. If we aren't having fun volunteering, providing support, chatting with the community, and developing new features then we take a break and do things that are more fun for us. This is why we don't have SLAs or ETAs for new features or repairs, and this is why things move a little slower than a for-profit company that you might be used to dealing with. Please see here for details on ETAs on support requests: https://wiki.helionet.org/ETA Sorry for locking this thread as a duplicate, but I'm locking this thread as a duplicate. Thanks for your continued patience. Please follow the original thread linked above for further progress updates.

Domain added. it can take up to 2 hours to start working.

Domain added. it can take up to 2 hours to start working.

You're welcome Please let us know if you need anything else.

You're welcome If you want to confirm the SPF and DKIM are working, you can try https://www.mail-tester.com/ Note that if you do this, you should send a real email to it (not just "Test"). If you send "Test" or similar, it'll give inaccurate results (it will likely show a PYZOR check failure and a spamassassin detection).

If you edit the target value of those DNS records to be johnny.heliohost.org instead of your domain, the autoconfig feature should work (no guarantees though, I'm not sure anyone has ever actually tried this before...) You also need to create a few other records: An MX record with a target of johnny.heliohost.org so you can receive mail. A TXT record for SPF. Create a TXT record with a blank name (or you may need to enter your domain as the name), and put this as the value: "v=spf1 ip4:64.62.151.106 ip6:2001:470:1:1ee::2009 ~all" A TXT record for DKIM. Create a TXT record called default._domainkey.tenkyuu.dev and put the below value in it: "v=DKIM1; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA+SDLc/Hl5PNixlC3Z1QqVI5F0WQUTC0wA2GHBtcHm+cqyRxqCWP7OmmV5Z7Vn3nos10c8TB7chpdkPiTVeO53mrpK6ZC9fjhlfFajdLReXJvRhqR+MBCwUEw1IimwFUz35YIRwqJ2bHaqvtjhuH4oOZ45qq79GB9gsc5OGC/A74pvZBOzMt1zYo3BvwUNo2LTgcyMDTunY+ZU15PBFyE34tj8iniPctiznyx+MboWzR4FCG/igoSwuksUm591bW8PblllmtUzdIQi7ORn9P+JO+bCW29gJlJ77wxupzvelwUMbi/iNWrCnyVbJVNxHxGQTu4jzvMg74BfIGZ1YErmQIDAQAB;"

You should set up the client manually, do not use autoconfig. When entering the connection info, enter johnny.heliohost.org (not your domain!) as the server address. If you enter your domain as the server in a mail client, it will not work. If you want the auto config to work, change the domain name in the target of those SRV records to johnny.heliohost.org as well. Also, did you create an MX record? You need to create an MX record pointed to Johnny.heliohost.org so you can actually receive mail. If you plan to send it, you also need to create TXT records for SPF and DKIM.

Strict mode is a known issue. The recommended settings are Full (but not strict). Plaske is unable to issue certificates when strict mode is enabled because Lets Encrypt requires a plain HTTP connection to verify the domain. This is especially problematic when the current certificate is already expired, or is missing, as Cloudflare will block all traffic to the site if the certificate is invalid, including plain HTTP. Some features such as "keep domain secured" will not function properly with strict mode enabled.

Probably not. I tried changing your password several times, and Plesk didn't update the git password correctly. I suspect if you change your account password the git password will remain the same as the one I emailed you.

This support request is being escalated to our root admins who can look into this more for you. Typically, requests are marked [Solved] by the volunteer staff when they have actioned what was being asked for, so we don't get a case of multiple people picking up the same request. Just because something is marked as Solved doesn't mean we won't keep trying to help you if needed. 🙂 Making a new thread as you have done is great. Sometimes folks go back and update the [Solved] thread, which is okay too since we try to check all new messages, but it's easier for this thread here to stick out as not Solved so it's less likely to be accidentally missed. I don't believe there should be any extra config you'd need to do once the SPF, DKIM, and DMARC have been set up, since I've seen users get a 10/10 grading on the mail-tester report right after it's all been set up. Getting a low score after that point, from the things I've seen, can be down to the user just putting 'test' in the test email or because they're using a domain that's typically associated with abuse (like .xyz or some of the less-trusted ones). But none of those things apply to you, so the root admins can doublecheck what's happening with the records they set up.

Try this Login at https://heliohost.org/login/ Continue to Plesk Click your username in the top right corner Click edit profile Change the password Go to https://ygo.helioho.st/plesk-git/comforting.git/ Try logging in with the new password

I spent some time trying this out for myself and ran into the same error. I've escalated your thread so an administrator can look into this further.

The domain thelema93.com.br has been added to your account.

WSGI control access has been enabled on the domain talesazoeto.heliohost.us. To restart your Flask app and load new code changes in simply edit /home/talesaz.heliohost.us/talesazoeto.heliohost.us/oeto/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.

Krydos can enable this for you

thank you

I could connect now. Thanks!

Remote access enabled for IP specified. Host: lily.heliohost.org Port: 3306 Username: paladin2

Because your MariaDB is on Lily, this is something Wolstech will be able to help you out with. I've escalated this thread for his attention. ? As a note to any other users who may find this post when searching the forum: Users on the Morty, Tommy, and Johnny servers can enable their own remote access to MariaDB / MySQL themselves. Inside Plesk, go to: Databases > click on the database User name > Scroll down to the Access Control section > Choose one of the "Allow remote connections from.." options > Click OK to save.

Installed. You can see the current list of installed modules for Tommy's Python 3.12 at https://krydos1.heliohost.org/pyinfo/info3.12.py

This support request is being escalated to our root admins.

Dear Team, Thank you a lot for your help and time. Kind regards, World Kryptonite

Hello, Sorry for the late reply. I was not finding the option to view my ticket . I am using python version 3.12 and the latest version of duckduckgo-search (https://pypi.org/project/duckduckgo-search/) will be good. Thank you for the positive reply and for the link. Kind regards, World Kryptonite

You can now upgrade the storage space on your account by going to https://heliohost.org/dashboard/storage/ This process is fully automated, and you no longer have to contact an admin to increase your storage space. Unlike most hosting providers we don't charge a monthly rate for storage space on our shared hosting accounts. We just charge a flat one-time donation of $5 per 1000 MB. The storage space, once increased, stays with your account forever. If you switch hosting plans, the storage transfers with your account. If you go inactive and your account is archived, the storage space will still be there years from now when you renew your account. Let us know if you have any comments or run into any issues upgrading your own storage space.

Dear Heliohost Team, Today I made a small donation to help you with this fantastic work. My account user name: sapatpirescoxe Paypal transaction ID: 00821791WF217374E Many Thanks MR

thank you very much for your help

Your last rebuild was only 10 days ago. The rule is you only get one free rebuild per month, but since you signed up about a year ago and this is only your second rebuild in twelve months we'll give you another. Your next free rebuild will be available on 2025-05-01. If you need another rebuild before then they can be purchased for $1 each. You'll get an email in a bit when the rebuild finishes.

No problem Please let me know if you need any help getting your application running.

Thanks for taking the time to complete this.

Please check your PMs for information regarding your Lily account.

I've removed your domain name now, please let me know if I missed any. Unfortunately, users' post editing ability had to be restricted because 2 users who decided to break our Terms of Service tried to blank out their posts to hide the evidence of their rule-breaking. ? Admins can still edit posts, so in your case if you want your domain name removed after a request has completed, just let us know and we're happy to help you!

Thank you, I will wait.

hi krydos and kazvee, 10/10 https://www.mail-tester.com/test-gq00bxp27 thank you very much! if i'm not wrong, i used to config gmail to get them through imap. or is there an another way? thx

I've moved the new email questions into a new thread to make it easier for helpers to follow instead of continuing the discussion under the [Solved] thread about adding your domain. The default email quota is 50 per day and 10 per hour. If you need more emails, you'll need to answer the following questions so the root admins can understand what you're sending, who you're sending it to, whether you sell your user's data, and how you'll handle unsubscribing and complaints. If HelioHost receives an abuse report for your account's emails, you'll be suspended for spam. 1) How many emails you plan to send per day? 2) Where you get the email addresses from? 3) How can recipients of your emails unsubscribe? 4) Do you have an unsubscribe@yourdomain.com address set up? 5) Do you have an abuse@yourdomain.com address set up? 6) Does each email have a link to unsubscribe? 7) Do you share or sell email addresses that you get? 8) Post an example of the messages being sent. Please note that providing these details does not guarantee approval from the root admins to increase the email limit, but it gives them all the details they need to consider doing so. We usually recommend not sending a test email with just the words "test" inside but mail-tester seemed fine with that and gave you a green checkmark for that part anyway. ? I've never seen that before, so just be aware that usually to get a good score in that section, you should use something that looks like a normal email. I'm not sure of a workaround to not need to check your HelioHost webmail, but I'm escalating this thread so the root admins can set up the email DNS for you and they can probably advise you better on this question, too.

Your records are correct, there is an Archived account on Johnny, but it doesn't have any domains in common with your active account on Tommy. As long as you don't login to the old Johnny account, you shouldn't fall foul of the Multiple Account Detection system. We could even look into deleting the old Johnny one if you want, just let us know if you want more details on how we could get that done for you. For the Tommy account you're having domain issues with, what problems are you having exactly? Without more details, I'd probably first suggest that you check that your domain and all subdomains either have their NS records pointed to the HelioHost nameservers: `ns1.heliohost.org` and `ns2.heliohost.org`, or that you've created A/AAAA records and pointed them to our IPv4/IPv6 address. (To find the correct IPs, please go to: Login > Plesk > Websites & Domains > [domain name] > and check at the bottom of the page.) If you've already checked all that, please give us more info about what issues you're having and we'll be happy to try to help troubleshoot further. Edited to add: Wolstech obviously types faster than I do! ?

The reason your domain doesn't work on your Tommy account is because the IP addresses in your external DNS are incorrect. The correct ones are shown in Plesk. To fix the issue, you need to correct DNS entries on your external DNS server, ensure the domains are enabled in Plesk, then wait 2 hours. The account michaelpyl is archived. It neither violates the TOS nor has any impact on your Tommy account. As long as you don't restore it, you're fine. If you do want to restore the Johnny account at some point, you'll need to delete your Tommy account first to avoid violating the TOS.

Remote access enabled. host=64.62.151.106 port=5432 user=funslemmens_vijfblad dbname=funslemmens_boris password=<set in Plesk>

I've added those subdomains to your account for you. Please note that it may take up to 2 hours for the changes to take effect. If after a full 2 hours your new subdomains don't work on your side, please make sure you clear your web browser cache: https://wiki.helionet.org/Clear_Your_Cache

Changing your main domain won't create any problem, but there is more involved with changing a main domain than there is just adding or removing addon domains. It's not a problem if you know what to expect. Right now, your main domain is a helioho.st domain, and your custom domain is the addon. You can keep that if it works for you. Later on, if you want to change your main domain to your custom domain, what would happen is: - We would need to delete your custom domain from being an addon domain, which would delete the folder inside Plesk for it, and all its files. If you have a backup made, this isn't really a problem, but you would need to re-upload the files after the changes are made. - We would make your custom domain the new main domain, which would delete all the existing files inside httpdocs that belong to the free helioho.st domain you have now. This isn't really a problem either if you made a backup of the files you had. If you even wanted the helioho.st domain put back on to your account as an addon domain, we could do that (but you would need to re-upload all files). The only difference I've noticed between my main domain and my addon domains is that the main domain files go into httpdocs, and my custom domain files don't. They go into a folder that has the same name as my custom domain. I actually prefer it this way so I don't accidentally upload things to the wrong place (since I use my main domain mostly for testing), but you may prefer it the other way around. I hope the above was helpful but please let us know if you have any questions.

The free domains we offer end in: "helioho.st" and "heliohost.us". As for adding the domain, that's been done now for you. Please note that it may take up to 2 hours for the domain change to take effect, and it will not work until you set up your DNS with your domain registrar. To configure your DNS, you can either: 1) Set NS records pointed to the HelioHost nameservers: `ns1.heliohost.org` and `ns2.heliohost.org`, or 2) Manually create DNS records: a) Add an A record (IPv4) pointing to your server's IPv4 address b) Add an AAAA record (IPv6) pointing to your server's IPv6 address To find the correct IPs, please go to: Login > Plesk > Websites & Domains > [domain name] > and check at the bottom of the page. If after a full 2 hours your new domain doesn't work on your side, please make sure you clear your web browser cache: https://wiki.helionet.org/Clear_Your_Cache

WSGI control access has been enabled on the domain alfrededison.helioho.st. To restart your Flask app and load new code changes in simply edit /home/alfrededison.helioho.st/httpdocs/vn30/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.

Here is the final final solution Here is the detail 1. wget --header="TOKEN:secured_token" "http://mbo.helioho.st/cgi-bin/my_script_for_build.py" : this cgi script contains the commands that run "npm install" + "npm run build" 2. touch tmp/restart.txt : after "npm run build" I need to restart the Node JS application, according to Plesk documentation it can be done by creating a file named "restart.txt" in folder "tmp" 3. wget "http://mbo.helioho.st/api/version" : when creating the file "tmp/restart.txt" the server will restart after the next request, that's why I immediately send a request to my application in order it to restart immediately after my new build

Have you ever thought that WordPress is slow? Have you ever been suspended for causing high load because of WordPress? Did you think that other CMSs like Joomla and Drupal have an outdated dashboard and/or are overwhelming for beginners? Then look no further. Publii is an AMAZING FREE static site CMS. Static sites can load WAYY faster than sites coded with an admin page (using PHP for example). Faster websites increases SEO, user engagement, and so much more. Unlike other static site generators or the simply static WordPress plugin, you can actually edit and update your site(s) with a simple to use, user friendly admin page (instead of having to manually code your website). It has an easy to use, beginner friendly user interface. Yet with customization features good for people with experience with code. After all this CMS generates static files that you can easily edit through the cPanel interface (or your favorite code editor) if you want more customization. To get started, go to Publii and just download their app. Then install the app on your computer. Done, it is that easy to setup. To create your first website, you need to click on add a new website. When you add a new website it will tell you to choose a name, symbol and author name. Then click add. Before you start anything, I recommend that you choose a theme. To choose a theme, go to this website: Themes and Plugins and download your preferred theme. Then go to the Publii dashboard and click on the three dots on the upper right hand corner. Select themes, click on install themes and select the zip file you downloaded. When you are finished, you can start creating your website. You can create your website in multiple different ways. If you have an existing (or backed up) WordPress installation, you can easily upload the website using the WordPress importer. If not, you can easily create your first post either using a WYSIWYG editor (kind of like the WordPress classic editor), block editor (pretty much identical as the WordPress Gutenberg editor), or Markdown editor (for the tech savvy people to code a page). When you finish writing your posts/pages (they are called the same thing), you can explore and play around with everything since the website hasn't been published yet. For example: tags, menus, authors, theme settings, site settings, backups, custom CSS, custom html, File Manger (not for existing files but to upload a new file), Log viewer, Regenerate Thumbnails, AMP (accelerated mobile pages), WordPress Importer(etc.). Now you just need to connect to a server so your website can be public. You can either choose to publish your website on cPanel or using GitHub Pages, whichever one you choose. To do that, click on Server in the side menu and choose your method of publishing. You can either upload using ftp (here you enter your site URL and ftp server, username, and password), using GitHub Pages, or manually uploading the files (not recommended as you will need to upload a fresh copy every time you edit your website). To publish your changes just click on sync your website and it will automatically upload a fresh copy of your website and rewrite the old copy of your website. Voila, you have just created a FAST and SECURE static site. Pictures of the Dashboard: