KazVee

Please let us know the full domain name you want added, including the top-level domain (TLD). If you're using HelioHost's domains, please specify if you want 'helioho.st' or 'heliohost.us', and if you've purchased a custom domain, please include the final .com, .net, etc. Once we have this information we can add the domain for you. You can read more information here about what details need to be provided when requesting a domain to be added: https://wiki.helionet.org/Addon_Domains

Our Morty server already has a more recent database version that supports Drupal 11.1.1, so if you need to use 11 immediately, you could consider signing up for an account there. The database versions on Tommy (donor server) and Johnny (free server) will likely be upgraded as well, however there are no ETAs for when this may happen. All staff are volunteers so features/fixes/etc. are done in order of highest priority/most benefit for the largest number of users, when we find spare time around other life obligations. If you want to use Drupal on Tommy or Johnny, you can choose a lower version of it (I think the next one down worked for me when I tested it a while back) and it will work with the lower DB version available on those servers.

I'm very sorry for your loss. I believe the email is retained so if the person changes their mind, they can recreate their account without needing to wait for the signup timeslots on Johnny or paying again for an account on Tommy. It was a feature introduced to help users recreate their accounts without needing admin intervention while we recovered from a Johnny server crash that was kept as a feature users found helpful in case they had second thoughts about deleting and wanted to come back. I guess you are suggesting that along with the questions asking the user that they're sure they want to delete their account, another checkbox or something is added so they can confirm that they 1) want their email removed from the system, and 2) confirm that they understand this means they'd need to start over from scratch (by waiting for Johnny to open, donating for Tommy, etc.) if they ever change their mind and want to come back? I have no idea the effort/difficulty of building something like this, but it sounds like a helpful feature for folks who are 100% certain they won't ever want a quick way to recreate an account, or who understand that if they do change their mind, they'd have to start over as if they had never had an account with us before. I've shared your idea in the staff channel, thank you for the suggestion. 🙂

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: 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.

Krydos can help you with this, so I've escalated this request for his attention.

This support request is being escalated to our root admins who can help get all these accounts set up for your students. 🙂

Of course. I've reset your account as requested. You should receive an email shortly so you can take the next steps to recreate it. In retrospect, we could have done it in a different order: In cases where you want a domain change and an account reset, during the account recreation process you would have the chance to choose a new username and/or a new domain so you could have changed domain that way. It makes no real difference this time since it's all been done within a very short timeframe. But for example if you had waited the 2 hours for the new domain to take full effect and only after that time asked for the reset, once you recreate the account there's a second 2 hour max wait time for the account to be recreated. By doing the reset first and then changing the domain as part of the account recreation, there's only the 1 x 2hr waiting period. Just in case this helps you for next time (or for anyone else searching the forum). 🙂

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: 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. 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

I've made those changes for you. Please note that it may take up to 2 hours for the 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 domains are removed, since the folder for the domain inside Plesk is deleted. I made a full account backup for you before I removed the 'wordpress' domain in case you need any files from it. 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 escalated this for the attention of Krydos since it's a VPS issue so he'll be able to have a look for you.

The reset feature will wipe your account so you can start fresh. If you might think you need any old files first, we recommend making a backup before doing a reset. After you ask for an account reset, you'll receive an email with a link to restart your account. You'll have 7 days to use that link, and if you don't use the link within 7 days, you'll need to signup for a brand new account. While you are restarting your account, you will be asked to enter the domain you want. If you want a different one this time, and it's available, it will be added to your account instead. Just to make sure you are aware: You are allowed up to 10 domains/subdomains on your account, so you don't necessarily need to delete the one on there now unless you really want to. We could just add another one for you, if you prefer. If this is something you'd want, a reset won't be needed, just let us know the domain/subdomain you want added.

Yes it is. We even have a Node.js tutorial guide to help you build a quick example project: https://wiki.helionet.org/Node.js Node apps can be demanding on server resources, so we recommend you keep an eye on the load your account is causing here: https://heliohost.org/dashboard/load/

Oh I see, sorry for my confusion. I have escalated this thread now so a root admin can delete your forum account Bartek2004 for you. They'll post an update in this thread once it's been done.

The best way to get the tata2676 forum account deleted is to login with that username and make a post asking for us to delete it for you. Then you can update the email address on your Bartek2004 forum account to match the one on your hosting account.

I have cancelled the first invite (sent to the email address with the . in it) and reissued the invite to the email address attached to forum username tata2676. Please check your email and use the new invite to recreate the account, and it should let you reclaim your old username.

Try using the same email address but without any . or + before the @ part. Email address kaz.vee@allmyemails.com would be seen as a different email address than kazvee@allmyemails.com.

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?