KazVee

You do not have to choose a new username if you don't want to. The hosting account username is linked to your forum account, and will be the same username as your forum account. So only the email address listed on forum account username tata2676 can use the matching hosting username. If you signup for a hosting account using the same email as an existing forum account it will suggest your old username and allow you to reuse it. If you want username tata2676 for your hosting account, please check the email address associated with your forum account username tata2676 and use that same email address. Please let us know if you still have any trouble.

Thank you for making sure to backup your data. ? I've reset your account as requested. You should receive an email shortly so you can take the next steps to recreate it. During the account recreation process, you'll be asked to confirm the domain you want, so you can enter the eu.org domain at that point. If you need more addon domains added on afterwards, please raise a new request and let us know any additional (you can have up to 10 total) domains/subdomains you'd like us to add. We also try to make backups as part of the account reset process, so if you discover you need any of your old files and there's any issue with your local backup, 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

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 In the meantime, please make sure you configure DNS for the new domain. You can either: Set NS records pointed to the HelioHost nameservers: `ns1.heliohost.org` and `ns2.heliohost.org`, or Manually create DNS records: Add an A record (IPv4) pointing to your server's IPv4 address. 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. 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 Just to make sure you are aware: You are allowed to have up to 10 domains total on your account. Instead of changing your main domain, we could add more domains for you, if you have a few projects in progress and this would work better for you. It's entirely up to you, but I wanted to make sure you knew this was a possibility. You can read more info on addon domains here: https://wiki.helionet.org/Addon_Domains

I've added that domain to 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 to In the meantime, please make sure you configure DNS for the new domain. You can either: Set NS records pointed to the HelioHost nameservers: `ns1.heliohost.org` and `ns2.heliohost.org`, or Manually create DNS records: Add an A record (IPv4) pointing to your server's IPv4 address. 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.

Some of the old wiki links won't work anymore because a few weeks ago we switched to a self-hosted MediaWiki site away from the old Gitbook that'd been in use for 5 years, and it handles underscores and dashes in URLs a little differently. All the same content can be found in the new wiki but if you bookmarked specific pages you may need to update your bookmarks. I'm more familiar with just uploading files to create websites, too. I haven't used Publii personally but my understanding is that it's similar to WordPress in terms of it giving you a web interface (or in Publii's case, a local-machine-only interface) where you would type in your posts and customize the text in the built-in (used to be called WYSIWYG) editor, instead of using html code to format the raw text files being uploaded. Then, because it's all running locally, this is why the wiki page points out that you would need to upload every time you post. Since you're familiar with creating and uploading html files, it would be no surprise to you that the changes you made in your text editor on your computer won't show up on your website until you upload and overwrite the old file. But we point this out for the folks who have only used WordPress before, where pages they edit are already live on their deployed site as soon as they save their changes, since that extra upload step to get a Publii page deployed isn't something they'd have had to do with their WP site. The server (and server load) that the wiki mentions refers to the shared hosting server (Johnny, Tommy, or Morty). When someone uses WordPress on the shared hosting, when they open their WP site to create and edit posts and format the text, etc., all the compute power that WP uses to make that happen is taking place on the shared server. When you also take into account that using lots of WP plugins increases the load, plus the risk of bot attacks, account suspensions can happen due to high load caused by their account on the shared resources. I suspect a lot of WP users aren't comfortable using a text editor to create and upload website files. The way Publii avoids account load issues is that it only runs on your local machine for any real-time editing. Then when you're done editing on your machine, there's probably a build process to generate a bunch of static files to upload via FTP. A static site will cause practically no account load on the shared hosting servers. If you're comfortable using text editors to make websites and you only want static pages, you could definitely just upload html files into your httpdocs folder to create a site that way. The options mentioned on the Wiki WP Alternatives page are just other ways for folks who like using frameworks (or who maybe don't know how to build a website in html from scratch) as other lower risk ways to build a site that's less likely to get their accounts suspended. If you're familiar with Markdown, I've found that Astro is another nice option to quickly get a decent looking site up without too much fuss, if you only need a few pages. Apparently it'll also render html code nicely but I haven't experimented with that. I hope some of the above was helpful but please let me know if I explained anything badly. ? I'm not sure about how best to deploy a customized version of a software package offered inside Softaculous. Hopefully the author of the Easy!Appointments customizations gives you some tips on that, if they've encountered this type of thing before, but if not please let us know and we can try to dig a little more.

Domains that don't end with helioho.st or heliohost.us are custom domains that our users bought from a domain registrar that they want hosted here. By adding the domain to HelioHost, they can upload the files for their site here. You can have up to 10 domains total (made up of free domains, custom domains, subdomains, etc.), so sometimes folks like to have different domains for various projects hosted with us. Some, but not all, domain registrars will also offer file hosting. I've never had the same company handle both for me, but I think in some cases it can be a challenge to move the domain off of the original company's file hosting service and over to another host, which is why some people don't like to have the same company handle both parts for them. You can get a custom domain from many registrars, but HelioHost has an affiliate agreement with Namecheap so if you get a domain with them, HelioHost gets a bit of commission for the referral. You can see a little more detail on that here: https://wiki.helionet.org/How_You_Can_Help#Use_Our_Affiliate_Links If you decide to get a domain with Namecheap, they will often have a discount code for new customers. For example you can get some .com domains right now for $6.49 for the first year with promo code NEWCOM649. (But it's also worth checking the renewal price for the years after that, if it's a domain you want to have longer term.)

That domain was indeed available, so I've added it to your account. 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 I've also moved this request into the right section. For support requests like this, please post them in the Customer Service section here: https://helionet.org/index/forum/45-customer-service/ The Website Management and Coding section you posted this in originally is more for general discussion, so support requests posted in there could be accidentally missed.

This support request is being escalated to our root admins.

Could you please let us know what domain this is happening on, so we can try to help you a bit further?

I've added that subdomain to your account for you. Please note that it may take up to 2 hours for your new subdomain 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 let us know if we can help with anything else. ?

We added that domain to your account for you yesterday, in this thread and by changing your registrar config to point to the HelioHost nameservers (ns1.heliohost.org and ns2.heliohost.org) that's all you need to do to host the site with us. In fact when I check that site now, I see the default contents, so if you login to Plesk you should see a folder for the domain inside your home directory. I'm not sure what else you mean about needing DNS set up. Do you mean you want SPF, DKIM, and DMARC records set up for email, like we say we can do for you on this page? Please could you give us a little more information about what you need done, and we'll be happy to try to help.

I've added that domain, and the go subdomain, to your account for you. Please note that it may take up to 2 hours for them to fully work. 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 In the meantime, please make sure you configure DNS for them. You can either: Set NS records pointed to the HelioHost nameservers: `ns1.heliohost.org` and `ns2.heliohost.org`, or Manually create DNS records: Add an A record (IPv4) pointing to your server's IPv4 address. 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. The "webmail" subdomain is reserved for Plesk's Roundcube. If you planned to use a different service, we recommend using your account's server name ('tommy.heliohost.org') as the host address anyway. You can view our email accounts guidance page for more details, but please let us know if you have any questions.

Glad to hear, I'll mark this [Solved] as requested then. ? Please give us a shout (by making a new thread) if you need help with anything else.

Hello! There's currently no option for private support of any kind. There's been discussions about offering private support, but if it is implemented, private support will likely be a paid service since it ties up an admin's time and prevents other users from assisting. There is currently no ETA on if or when private support may be offered. When users need to provide details they don't want kept public on the forum forever, I've seen them go back and edit the info out of their posts, once the admins have used it to make whatever changes are needed. Maybe this would work for you as an alternative to waiting for private paid support to be implemented? As for your Cloudflare question, we have a guide here on using CF to manage DNS: https://wiki.helionet.org/Cloudflare_DNS_Records I can't comment if it's easier or not, but I've noticed a few users who were new to DNS management and able to use CF without any problems. It seems pretty straightforward to set up and I believe CF have good help documents if you get stuck. Edit: I didn't see Wolstech had already replied before I typed this up ? I'll leave it in case the links are still helpful.

I've added that domain to 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 In the meantime, please make sure you configure DNS for the new domain, as you did for your main domain.

This support request is being escalated to our root admins.

We accept payment with debit or credit cards, where PayPal acts as the payment processor for the card transaction but users do not need a PayPal account to signup. You may need to check with the card issuer to find out why it is being declined. We do have many users from Türkiye who are on the Tommy server, so it's possible to sign up for an account from your country with debit/credit. You may need to try with a different card.

The score changes for me too when I check the report link you shared. I saw it at 9/10 and then I refreshed the page and it went to 7/10. I don't know why it's happening but figured I'd pop a note here so you know it's not only you seeing this happen! It seems the content of the email message you sent was basically just "testing", and this can cause a lower score because of the message contents. You should have better luck getting 10/10 with a message that looks real. If you send out a regular newsletter or something, then try using some text from one of those. It doesn't have to be a long message, I think I've gotten 10s with just a quick pretend "reminder of tomorrow night's shopping plans and a list of items to buy" or something like that, that looks like a genuine non-test email. I can't remember the limit per day that we can use the mail-tester site, but I remember I got limited because I tried too often, so my suggestion would be to wait for more help with that -3 section first, and then if you're asked to send another test email, make sure it has a real-looking message inside it as well.

Please do not create multiple posts for the same request. You have received two answers to your original request: here and here. Please read both the answers you were given. You can post any replies in the other thread. Thanks!

I'll check it out, thanks for sharing! RSS feeds are one of those things I heard about and thought it'd be cool to use but then just never did. ? I didn't really even know they were still popular, so maybe I'll finally get one set up for myself.

I've added that domain to 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 In the meantime, please make sure you configure DNS for the new domain. You can either: Set NS records pointed to the HelioHost nameservers: `ns1.heliohost.org` and `ns2.heliohost.org`, or Manually create DNS records: Add an A record (IPv4) pointing to your server's IPv4 address. 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.

I don't know about free RSS readers, but I did a quick test with a php file and got a test website up with the latest news inside a footer. I limited it to the last 5 news posts since it seemed like enough, but this could be edited. This may be an option for you, since it doesn't need any RSS reader service? This is the little blue footer at the bottom: To build this, I made an .htaccess file with this inside: <IfModule mod_headers.c> SetEnvIf Origin "https://my-website.heliohost.us" CORS_ALLOWED Header set Access-Control-Allow-Origin "https://helionet.org" env=CORS_ALLOWED Header set Access-Control-Allow-Methods "GET" env=CORS_ALLOWED Header set Access-Control-Allow-Headers "Content-Type" env=CORS_ALLOWED </IfModule> Then I made a get-feed.php file with this inside: <?php $cacheFile = 'rss_cache.xml'; $cacheTime = 1800; if (@file_exists($cacheFile) && (filemtime($cacheFile) + $cacheTime > time())) { $response = file_get_contents($cacheFile); } else { $response = @file_get_contents('https://helionet.org/index/rss/1-news.xml'); if ($response === FALSE) { die('Error fetching the RSS feed.'); } file_put_contents($cacheFile, $response); } header('Content-Type: application/rss+xml'); echo $response; ?> And usually I'd move the styling out into a separate file, but for now it's all inside index.html: <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <title>Website with News Footer</title> <style> body { display: flex; flex-direction: column; height: 100vh; margin: 0; padding: 0; } .content { flex-grow: 1; padding: 0 20px; } footer { background-color: #d0fefe; padding: 10px; text-align: center; font-family: Arial, sans-serif; display: flex; flex-direction: column; align-items: center; margin-top: 10px; font-size: 16px; } #rss-news { display: flex; flex-direction: row; gap: 15px; justify-content: center; flex-wrap: wrap; margin-top: 10px; } #rss-news div { text-align: center; font-size: 14px; line-height: 1.5; } #rss-news a { text-decoration: none; color: #0073e6; font-weight: bold; font-size: 14px; } #rss-news a:hover { text-decoration: underline; } #rss-news small { color: #666; font-size: 12px; } h4 { font-size: 16px; margin-bottom: 10px; } </style> </head> <body> <div class="content"> <h1>Welcome to My Website</h1> <p>This is the main content of the website.</p> </div> <footer> <h4>Latest HelioHost News</h4> <div id="rss-news"> </div> </footer> <script> const rssUrl = 'get-feed.php'; fetch(rssUrl) .then(response => response.text()) .then(data => { const parser = new DOMParser(); const xmlDoc = parser.parseFromString(data, "application/xml"); const items = xmlDoc.querySelectorAll("item"); const newsContainer = document.getElementById("rss-news"); let newsHTML = ""; items.forEach((item, index) => { if (index < 5) { const title = item.querySelector("title").textContent; const link = item.querySelector("link").textContent; const pubDate = item.querySelector("pubDate").textContent; const formattedDate = new Date(pubDate).toLocaleString("en-US", { year: 'numeric', month: 'short', day: 'numeric', hour: '2-digit', minute: '2-digit' }); newsHTML += ` <div> <a href="${link}" target="_blank">${title}</a> <br><small>${formattedDate}</small> </div> `; } }); newsContainer.innerHTML = newsHTML; }) .catch(error => { console.error('Error fetching RSS feed:', error); const newsContainer = document.getElementById("rss-news"); newsContainer.innerHTML = "<p>Unable to load the latest news. Please try again later.</p>"; }); </script> </body> </html> You could probably make it look a lot better but I liked the idea of a "latest news" embed in a footer for those who wanted to have it on their page!

On the new Wiki, there are 2 links in the footer to see latest news, too. The Announcements link goes to the forum's News section, and there's also an RSS Feed link. I don't use an RSS reader myself but I think this link could be added into an existing RSS reader to get the latest HelioHost news along with the other news topics people follow in their reader. If you try to use the RSS feed, please let us know how it works for you, it'd be great to have another example to show people how they can stay up to date with what's happening at HelioHost. ?

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 In the meantime, please either: - Point your domain to the HelioHost nameservers: `ns1.heliohost.org` and `ns2.heliohost.org`, or - Create an A or AAAA record and point it to the IP address for the server you're on. You can find the IP address to use inside Plesk > Websites & Domains > [domain name] > and check at the bottom of the page. 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

Hello! I just installed Nextcloud (using Softaculous) on my test account and I can replicate the issue of not being able to login. I've flagged it in our staff channel, along with the error logs I'm seeing. Here is a link explaining how to view error logs on your account, I figured I'd share it since it's just good to know how to do anyway: https://wiki.helionet.org/View_Error_Logs If you do have a look at your logs, if you see anything different than the errors I get below, please let us know. But for right now I think it's safe to say it's not an issue isolated to your account, so we'll look into it and post more updates when we can.