KazVee

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.

Hi Atiq! I've added those 2 domains 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

I didn't have issues the last time I installed Nextcloud with Softaculous, but now that you've requested an account reset it's not possible to troubleshoot the issue further. I'll mark this thread as [Solved] since no further action is possible, but once you have recreated your account, if you have trouble with anything please create a new support request thread.

I've reset your account as requested. You should receive an email shortly so you can take the next steps to recreate it. I made a backup before the reset, so if you discover you need any of your old files after all, 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/tutorials/plesk/account-backups

I've escalated this request so a root admin can delete the files and database you mentioned to get you back under the account limit again. Once they've done so, they'll update this thread to let you know.

The maximum number of domains you can have on an account is 10. That total is spread out over domains, subdomains, and aliases, so it's maximum of 10 of any combination of those things. I've added those subdomains for you now, please note they may take up to 2 hours 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/misc/clear-your-cache In meantime, same as you did when you set up your main domain, please either: • Point your subdomains to the HelioHost nameservers: `ns1.heliohost.org` and `ns2.heliohost.org`, or • Create A / AAAA records and point them 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.

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/misc/clear-your-cache In the meantime, please either: Point your domain to the HelioHost nameservers: `ns1.heliohost.org` and `ns2.heliohost.org`, or Create A/AAAA records and point them to the IP address(es) for the server you're on. You can find the IP address details here: 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/tutorials/plesk/account-backups

I'll mark this thread as [Solved] since the VPS signup has been successful. Please create a new request if you need help with anything else.

Please doublecheck the nameservers you've used on your domain registrar's site to make sure you have entered the correct ones. The HelioHost nameservers are: ns1.heliohost.org and ns2.heliohost.org not 'helionet' as you mentioned in your message. 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/misc/clear-your-cache 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/tutorials/plesk/account-backups

That account is suspended for Phishing.

Please don't make duplicate threads for the same request. Since there is a second post asking for a VPS dashboard to be installed, we'll use the other later thread here to share further updates: https://helionet.org/index/topic/63317-krydos-vps-gui/

All HelioHost 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. 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. You can read more about response timescales here: https://wiki.helionet.org/hosting/repair-times When we helped you figure out the card payment, we did so in our spare time. You're welcome, by the way, since our advice seems to have worked and you managed to sort out the card payment for a VPS. It's generally considered impolite to be impatient when people are spending their free time to help. I can only speak for myself but the requests that are more fun for me to spend my spare time on are the ones where the user has been polite and patient (saying please and thank you can get a person pretty far in life) instead of bumping a thread demanding updates. This is not like a paid job where I have to deal with any kind of rudeness a customer throws my way: if I see someone has been rude and impatient, or made duplicate threads for the same request, I am free to move on to a different person to help, since it's more fun and interesting for me to donate my time to help people who appreciate it. Although there is no set ETA for requests, we do generally try to reply within 24 hours, but real-life priorities can impact things. There is no daily schedule set for when any of us login and process requests. I presume you want Hestia installed for WordPress (this would have been a good detail to include in your original request), and when Krydos has some free time to install that for you, he will do that and reply in this thread. If you absolutely cannot wait another second and need Hestia installed onto your VPS right now, you could do it yourself using Hestia's installation guide here: https://hestiacp.com/docs/introduction/getting-started.html Once Hestia is installed, you can install WordPress using the tutorial guide in our Wiki here: https://wiki.helionet.org/tutorials/vps/wordpress-hestia