Krydos

I've considered doing the same thing. There doesn't seem to be any documentation anywhere for what would work and what isn't allowed. $25 would cover max storage, and a transfer to Tommy and 5 months of inactivity immunity. Yes, we're aware. As a free hosting provider we get a lot of abuse. Phishing and spam and whatnot try to use our service all the time since we don't require a credit card. Criminals don't want to pay and have their personal information known obviously. We suspend the abuse reports we get as quick as we can, but something along those lines seems to have upset Facebook. Since Facebook basically doesn't have any customer support (unless you pay a lot on advertising) there isn't a lot we can do. Each person that tries to post heliohost.org on Facebook and reports it as a false positive might help. If we get enough reports like that they may remove the ban. We've got some plans to help prevent it from happening again in the future if they ever unban us.

If you start a url with a / it means start at the webroot, which is /home/mabass/public_html/ for that domain. If you run your app on a subdomain instead of a subdirectory you might get the results you're expecting. For instance if you created a subdomain called flask.mabass.heliohost.org then the webroot would be /home/mabass/public_html/flask/ and if you used a url that started with a / it would start at the webroot which seems to be what you're expecting. Also /static/adx_abctrainer/img/ is an absolute url path since it starts with a /. A relative path would start with a . (period) .. (two periods) or a directory name.

Works for me <?php echo session_save_path()."<br>"; ini_set("session.save_path", "/home/krydos/tmp"); echo session_save_path(); https://krydos.heliohost.org/session_change.php

Remote access enabled.

Well, you can set the session path to whatever you want with ini_set('session.save_path', $path);

666 is better unless you need to execute the file for some reason. 6 = read/write, 7 = read/write/execute. Directories generally need execute permissions, but unless the file is cgi or a command line script it doesn't need execute. Try changing the directory that the files are in to 777 though.

Wonky forums. I wonder why it included a space and another word? Usually if you post a link and then a space it only makes the url until the first space. I should have clicked the link to make sure it worked.

Did you set read permissions for other on that file? You can right click on the file in cpanel file explorer or use ftp to change permissions. Filezilla calls other public permissions for instance.

Yeah, no problem. Thanks for being so understanding. Sorry about having to suspend you. When the server performance gets too bad it automatically suspends whoever is causing the most load to try to get the whole server performance back within acceptable levels. You happened to be causing the most load at the time. If you need any help transferring your site to a VPS just let us know. EDIT: Oh, also we're running a VPS sale that doesn't show up yet on that page. You get 1 GB of memory free with any VPS purchase. So if you select 1 GB you get 2 GB for the same price.

Your account was suspended because Wordpress is causing too much load. I have unsuspended your account, but please try to limit the load you put on our servers as it slows down not only your site, but the sites of all other HelioHost users sharing your server. This is really common for Wordpress. It can cause massive amounts of load even if you're hardly getting any traffic to your site. Wordpress is also incredibly insecure and very easy to hack. We see Wordpress accounts get hacked all the time and usually the hacker sets up a phishing site on your domain. We strongly recommend using any software other than Wordpress. If you insist on using Wordpress you might want to consider purchasing a VPS instead. VPS hosting gives you an entire virtual server to yourself, including no load limits, a dedicated IP address, and full root access. Wordpress sites load relatively slowly on our shared hosting, but they will be much faster on a VPS.

Unsuspended.

Your account was suspended because our systems detected that you might have more than one account. We understand that no one ever reads our terms, but as a reminder, our Terms of Service state that each user is allowed to have only one account. The reason we have to enforce this rule is because our servers are already overloaded the way it is, and it wouldn't be fair to everyone that is turned away each day for you to have more than one when so many others have none. One common reason people create more than one account is to get around our storage limit of 1000 MB. Did you know that we will give you another 1000 MB of storage for each $5 USD donation you make up to 5000 MB total? If you'd like to increase the storage of your account just make a donation and then let us know your transaction ID and username. Another common reason people create more than one account is to host more than one website. Did you know that you can host as many websites on your one account as you want? Unlike a lot of free hosts we offer unlimited alias domains, unlimited addon domains, and unlimited subdomains. If you need any help adding another website to your account just let us know. Another common reason people create more than one account is to try out several servers at once, or to transfer a website between accounts on different servers. Did you know that an admin can move your account for you for as little as a $1 USD donation? This will save you the trouble of signing up again, and deleting your account, etc. Sometimes our systems flags you as possibly having more than one account when you share a computer with family, friends, coworkers, other students, etc. If this is your situation we apologize for the suspension, and we'll be happy to unsuspend all of the involved accounts after you provide proof that each of the accounts belong to a different person.

Unsuspended.

Unsuspended.

Remote access enabled.

There you go https://krydos.heliohost.org/cgi-bin/modules37.py

You can register .de domains with our namecheap affiliate link. For instance http://heliohost.org/partners/namecheap/krydos.de It looks like .de domains are currently $6.88 per year, and namecheap is guaranteed to work with our nameservers because I've bought several domains from them and hosted them here.

Login at https://www.heliohost.org/login/ and then click Change Main Domain. On the next page enter your username in all lowercase, your email won't work on this form, and the main domain you want to change to. After you submit your new main domain you can check if it worked by going to cpanel and checking the right column information box. It should show your new main domain within a few minutes. Your new domain could show queued for up to 2 hours after changing while the server gets it set up.

You can set it as your main domain and it should work.

Not really. Most of the log files are full of information from all of the users on the server, so we can't provide direct access due to the possibility that the logs contain private information from another user. There is the error log button in cpanel that you may not have seen yet. Sometimes it contains useful information, but most of the time an admin can get a more detailed error message. Cron jobs can usually do a pretty good job of emailing you the errors, but you can only use them twice a day so that limits the usefulness. If you want us to try to get you a better error message just post the URL to the flask app. Probably. Most of the time in a production environment you want potentially malicious visitors to your site to not see the error messages, because they could use them against you to find vulnerabilities in your code. PHP ships with error messages disabled by default for this reason, and it wouldn't surprise me if flask was the same way. Make a post in customer service, and include your username, server, and python version that you're using. You can just reply to this thread if you want rather than making a new post. Not a big deal. Wow, you're right. That semicolon has probably been there for 4 years or more. It works with it there and it works without it there so erroneous might be too strong of a word since it doesn't cause an error. I would agree with the word unneeded though. I edited the wiki. Thanks for pointing that out.

It seems like more and more registrar's are doing this lately. It's a circular dependency. Cpanel requires the nameservers to be set before you can add the domain, and the registrar requires the domain to be added to cpanel before they will let you set the nameservers. The industry standard for the last 25 years or so is to set the nameservers at the registrar first and then add the domain to httpd.conf which is what cpanel does when you alias or addon a domain. It makes 100 times more sense to do it this way, because the nameserver check that cpanel does prevents people from doing dumb things like trying to add google.com as an addon domain. The best option is to contact your registrar and tell them their system is broken and they need to fix it, but obviously that rarely works. A workaround is you can still use your domain from a broken registrar as your main domain, but then you can only have one such domain on your account. Some registrar you can trick by changing your main to the broken domain, and then getting them to set the nameservers correctly and then change your main domain back and add it as an alias or an addon domain quickly before they notice. Sometimes it works and other times it doesn't.

Autossl can take up to 24 hours after you add a domain to start working. If you've added the domain less than 24 hours ago you just need to be patient. If you added the domain more than 24 hours ago and autossl still isn't working let us know and we can take a look. I checked your domain, and apparently in the 8 minutes since you made your post ssl has started working. You can see the details of your autossl certificate at https://www.sslshopper.com/ssl-checker.html#hostname=plantgreenpg.com Try adding this to your .htaccess: <IfModule mod_gzip.c> RewriteRule ^(.*)$ $1 [NS,E=no-gzip:1,E=dont-vary:1] </IfModule> Memory usage and disk usage are two different things. Memory gets used when someone visits your site and a php script like index.php runs. Disk space gets used up when you upload files to your account like images, etc. The reason your memory is sometimes at 100 is because wordpress is terrible software. If you insist on using it for some reason I recommend trying this plugin https://www.simplystatic.co/ It will speed up your site, reduce your load, and help prevent your site from being hacked.

I guess my phrasing is a little confusing. What might be more accurate way to explain it is your account basically goes into donor mode for 2 months from the date of your donation which means it doesn't need cpanel logins to update your last login date. 2020-12-10 is when your account goes back into free mode, and when that happens you have 30 days before your account gets flagged as inactive. So yes, you're right, if you didn't log in at all your account would go inactive on 2021-01-09, which is 30 days from 2020-12-10. Maybe I should change the way I phrase it.

Unblocked. It was for failed IMAP logins, so make sure your credentials are saved properly in your mail clients.

Unblocked. It was for failed SFTP logins, so make sure you have your credentials saved correctly in your SFTP client.