wolstech

You need to wait 2 hours after installing it before it will work. Also, the certificate you're using doesn't fully cover the domain. It needs to cover both the bare domain lioncita.com and the www subdomain for full coverage. Considering you're on Ricky, my recommendation is to just delete whatever certificates you've installed and let autossl run. The server will get you a proper certificate on its own assuming validation passes. The process can take up to 24 hours. Make sure you don't have a forced ssl redirect on your site, as this can break autossl unless an exception is added for the .well-known folder. There's no need to manually install a certificate on Ricky (or Tommy). Only Johnny users have to provide their own certificate.

Usually it means your code is broken and wouldn't start. Krydos can get the logs for you so you can figure out what happened.

Quota for account life2 has been increased. Thank you for the donation.

It's related to how you have the software for your website configured. The software is likely configured to expect the .in domain and no folder in the path, so using the heliohost.org subdomain and having the subfolder in the path breaks it. It's quite common for a site to not work correctly when accessed like this. Simply access it as it's intended and you're good. You might want to toss an index file in the root of public html that redirects to the correct domain, even if only so the directory listing isn't visible.

Please clear your cache. SSL on that domain works fine for me. As for that link, yeah, we upgraded the wiki and all the documentation links broke.

Unarchived.

This account has been moved to Tommy. Thank you for the donation If you see a queued page or 404 error, please clear your cache. In some cases, it may take a few hours for DNS to fully update. It might also take a few hours before AutoSSL will get certificates for SSL.

Done. Thank you for the donation If you see a queued page or 404 error, please clear your cache and flush the DNS resolver on your computer. In some cases, it may take a few hours for your site to be visible since the IP address has changed.

Moving now

Moving now

It depends which one he's using. AngularJS looks like a plain old JavaScript library to me: https://angularjs.org/ There's also plain Angular, which is newer and uses node.js: https://angular.io/guide/setup-local

Krydos might be able to do this.

There's no need to change the main domain until you're ready to move your real domain to us. For now, just use http://life.heliohost.org/stroke/ to see your website until everything is working. Your new copy of your site should be at that location, however the software is broken (500 error). Check to make sure the permissions are set to 644 on the files in the ~/public_html/stroke/ folder, make sure the database is configured correctly, and rename the .htaccess file to anything that's not .htaccess so its ignored. That should help clear up the 500 error.

You can just use life.heliohost.org if you want. I just used that domain as an example. It doesn't matter terribly much since it's not the final domain, what matters is that it resolves publicly, which (anything).heliohost.org will do. I didn't look at your account beforehand and assumed your real domain (the .in domain) was your main domain which won't work until you change the name servers.

It has a phishing site on it that the hacker put there, so yes it's hacked. WP itself is massively insecure and must be kept updated at all times. Also, many "free" Wordpress themes from questionable sites are free because they have a backdoor in them. The hacker then uses the backdoor to set up phishing, send spam, or host malware on your account, all of which make the criminals tons of money off the unsuspecting public when it works correctly. The best solution is to not use WP at all. The second best solution is to keep everything up to date, use as few themes and extensions as possible, and and avoid using extensions and themes from random websites.

Unarchived. It may take up to 2 hours to work.

You already have another active account. Users are only allowed one account at a time, so in order to unarchive this, you'll need to delete postfre2 first.

These aren't exact instructions, but should give you an idea: Remove the line from the hosts file, this is not supported on our service.Change the main domain to something that ends in .heliohost.org, so strokesupport.heliohost.org would work.Move the contents of the stroke folder directly into public_html.Wait 2 hours.Clear browser cache.Modify the appropriate mysql values to configure WP to use the domain strokesupport.heliohost.org (google will explain this process).Access your site at (if you use the above example): http://strokesupport.heliohost.org/Perform any changes you wish to make to the site.When you're ready to move the domain: Modify the appropriate mysql values to configure WP to use the domain strokesupport.inChange main domain to strokesupport.inWait 2 hours.Set name servers to ns1.heliohost.org and ns2.heliohost.orgWait for DNS propagationClear browser and DNS cache. As above though, we highly recommend not using WP. If you're interested in just tossing out the site and building a new one: Remove the line from the hosts file, this is not supported on our service.Change the main domain to something that ends in .heliohost.org, so strokesupport.heliohost.org would work.Delete the stroke folder.Wait 2 hours.Access your site at (if you use the above example): http://strokesupport.heliohost.org/Build your new site in public_html or create a folder for it if desired (keep in mind if you use a folder, you'll need to set up a redirect in public_html or add the folder name to the end of the URL (e.g. strokesupport.heliohost.org/stroke/ ) every time.

Krydos has to do this for you...

Unarchived.

To get this working in the meantime for testing, go here and change your main domain to the domain you're putting in your host file: http://heliohost.org/classic/support/scripts/domain After that, wait 2 hours, then clear your browser cache and try again. Also, for what it's worth, WordPress is the one program we really love to hate on around here, and will always recommend that people not use. It's poorly written and very insecure by design. As a result, it's a leading cause of performance issues, load suspensions, and even accidental bans (usually when it gets hacked...which is more often than we'd like...with the result generally being a phishing site getting set up). You'll probably need to be on Tommy for decent performance.

Using the IP address of the server with the host file is not supported. You might be able to get limited functionality by setting your domain as the account's main domain, waiting 2 hours, then try using it that way, but most functionality will not work in this configuration. For the service to perform properly, you need to actually use a real domain and point it to our name servers (ns1.heliohost.org and ns2.heliohost.org) at the registrar.

There are two ways an account gets fully deleted: someone deleted it, or it came due for archive and was suspended for a reason other than inactivity (suspended accounts won't archive, they just delete, this is done so we don't archive phishing and other abusive accounts). Either way, that account does not exist, so you'll need to sign up again.

You'd have to toss it out and start over. That's the one downside. Most people we make this recommendation to are newcomers, so they haven't built anything yet.

The best solution to WordPress problems is to not use WordPress. Just about any other CMS is better. Luigi explained why above.