Krydos

It looks like all you need to do now is set your nigelbarksfield.co.uk nameservers to ns1.heliohost.org and ns2.heliohost.org and your domain will be hosted. Your account has existed and been ready to go since 2017-02-14.

The username restoree, and the domain zen.cu.cc are already available to create your account.

Did you not receive your invite? Yes, of course you can host your domain on Tommy.

Your account was suspended for inactivity, because you haven't logged into your account in the last 30 days. To reactivate your account, please visit http://www.heliohost.org/renew. To prevent this from happening in the future please remember to visit https://heliohost.org/ to log into your account at least once every 30 days. If you are still seeing the Account Suspended page after renewing your account, please clear your cache.

Thanks for reporting this error. Obviously it was a new one that we hadn't seen before. The cpanel account creation script can behave rather bizarre sometimes. Anyways, since you reported it I managed to track down the bug that caused your account to not create. I requeued your account for you and it created successfully this time http://hippo.heliohost.org/ You'll probably need to reset your password https://www.heliohost.org/reset/ before you'll be able to log in though. Let us know if you need help with anything else.

The file causing the load on your site is /home/pokecake/public_html/index.php Both of the load spikes today http://heliohost.grd.net.pl/monitor/archive/?2017-03-01 at about 1530 UTC and again at about 1745 UTC were caused entirely by your account. Since I've unsuspended your account a few minutes ago it hasn't done anything crazy yet, but it will be suspended again if the load spikes continue.

There you go http://bfwebext.heliohost.org/test.aspx

I had a similar experience with my krydos.tk domain. I've never really hosted anything there. It's just said "Blank." like that for like six years now, but out of nowhere they yanked it out of my control and put a bunch of like porn spam ads and stuff on whomever might type in my domain. When I logged in to the control panel it said that my domain was too active for a free domain or something, and they needed to charge me $20 USD a year to keep it. Eventually they gave up trying to scam me out of money because I just ignored them, and (unlike wolstech) I was able to just edit all the references to krydos.tk there were in the world and change them all to krydos.heliohost.org. Then when they were done trying to extort me I registered krydos.tk for free again a few months later. THEN! (as if that wasn't enough already.) They flagged my whole freenom account as suspicious or a hacker or a bot or something. They never would tell me what the problem was exactly, and said I could never have my account back. Ok... So I created a new account and registered krydos.tk on the new one. It's just all really bizarre. Not worth the effort. Also, I've apparently earned myself 26.5 years of free domains. Yay!

There is no SSL certificate installed on your account. You can install it by selecting your domain, copying the certificate, the private key, and the chain file to https://tommy.heliohost.org:2083/frontend/paper_lantern/ssl/install.html and then click install certificate. If you wish you can PM me those three text blocks and I can install it for you. I never check my PMs though so make sure you post in this thread if you do decide to PM me so I can know to check my PM box. This tutorial is for installing a free Let's Encrypt certificate but it may help you too http://wiki.helionet.org/Installing_an_SSL_Certificate_on_Tommy_with_ZeroSSL

Awesome! Just let me know your wiki username, and I'll get you promoted.

You can change your own url with this script http://www.heliohost.org/classic/support/scripts/domain

If you tell us the actual domain we could check the settings for you and verify that they are correct.

display_errors = On for all versions of php on Tommy now. Here is an example file where the line is missing a semicolon http://krydos.heliohost.org/error.php How does that look? I opened the file with vim, and it says the encoding type along the bottom of the screen. It caught my eye because when a file has standard linux encoding it doesn't show anything there. This is actually a really common reason for cgi executables to cause 500 errors, but it rarely makes a difference with php scripts. As you could see the php still executed, but threw header already sent errors. To fix the encoding I just copied the code from the broken file, deleted the broken file, created a new file with the same name in vim and pasted the code back in. I think your real question isn't how did I do it, but rather how can you do it though so it doesn't happen again in the future right? I would recommend creating the file through cpanel file manager and then copy/pasting the code in if you think you might be having encoding issues. root@tommy [/home/hypo/public_html]# file -i * cgi-bin: inode/directory; charset=binary count: application/octet-stream css: inode/directory; charset=binary cus.txt: text/plain; charset=us-ascii error_log: text/plain; charset=us-ascii images: inode/directory; charset=binary indexgood.php: text/x-php; charset=us-ascii index.php: text/x-php; charset=us-ascii js: inode/directory; charset=binary listenerold.php: text/x-php; charset=us-ascii listener.php: text/x-php; charset=us-ascii paypal_success.php: text/html; charset=us-ascii resp.txt: text/plain; charset=us-ascii I'm not sure because I already deleted the broken file, but I believe it was octet-stream just like your count file.

Changed back.

It works now http://hypo.heliohost.org/ The problem was your file encoding was screwed up, and php kept reporting that the headers had already been sent due to the file encoding being wrong for linux.

Your username was already in use on these forums. Since I renamed your forum account the username maicol07 is now available to create a new account.

Can't you just change the error reporting level in the script if you need it? I've always just looked in the error_log file myself. The settings that we have now are just the default settings that cPanel installs PHP with.

How did you install Joomla? Softaculous? From source?

The username is the same as your forum username, and the email address is d******e@yahoo.co.uk

Tommy uses the same nameservers (ns1.heliohost.org and ns2.heliohost.org) as Stevie did so you probably won't need to change anything at all. Just add them to your new account and they should start working. There is a backup at https://www.heliohost.org/backup/ for you, but it's only 180k so I don't know how much might be in there for you. Let us know if you need help accessing it.

Set the nameservers of the domain to ns1.heliohost.org and ns2.heliohost.org and try adding the domain again.

Thanks! Looks good. We're actually going to get Stevie running again possibly as early as Monday. We'll see how it goes.

I made a php script with your code and it gives me the same session ID on Tommy over and over even without https: <?php session_start(); echo session_id(); http://krydos.heliohost.org/session/ Perhaps something is going on with your browser? Incognito mode? What happens when you try a different browser?

Yeah, no problem. We all would appreciate it if you could create a wiki account at http://wiki.helionet.org/ and create a tutorial for people to do what you have just done. This would be especially useful for people if you use windows on your home pc since most people use that os. I find it makes more sense to people from the point of view of another user such as yourself. You could use http://wiki.helionet.org/Java_Servlet http://wiki.helionet.org/Installing_an_SSL_Certificate_on_Tommy_with_ZeroSSL or http://wiki.helionet.org/Running_Auto_Backups as templates.

Oh yeah, one other thing. The command django-admin startproject command creates your settings.py file with ALLOWED_HOSTS = [] Django on Tommy will report an error unless you specify your domain or use a wildcard there. ALLOWED_HOSTS = ['*'] Specifying an exact domain will be more secure, but for the future people who may read this the * will work for all of your websites.