Krydos

Mixed Content: The page at 'https://atoz.ml/tools/source.php' was loaded over HTTPS, but requested an insecure stylesheet 'http://atoz.ml/assets/css/styles.css'. This request has been blocked; the content must be served over HTTPS. source.php:1 Mixed Content: The page at 'https://atoz.ml/tools/source.php' was loaded over HTTPS, but requested an insecure favicon 'http://atoz.ml/assets/images/favicons/favicon.png'. This request has been blocked; the content must be served over HTTPS. source.php:1 Mixed Content: The page at 'https://atoz.ml/tools/source.php' was loaded over HTTPS, but requested an insecure stylesheet 'http://atoz.ml/assets/css/styles.css'. This request has been blocked; the content must be served over HTTPS. You need to update your code to use https instead of http. Example: <link href="http://atoz.ml/assets/css/styles.css" rel="stylesheet"/>

Done. You should now be able to log in and your website should be working again.

We just got a great new source for our wikipedia article! https://www.hostingadvice.com/blog/heliohost-provides-free-hosting-to-a-tight-knit-community/ This is exactly the sort of "independent reliable published secondary sources" that wikipedia is looking for.

What is the link to the page?

That account was actually on Tommy. I checked the log files and it was deleted, presumably by you, sometime between 2018-07-18 and today.

Please post the following information: Your cPanel usernameYour main domainThe server that you are onThe version of python

Post the version of python you're using, and the module you need and an admin can install it for you.

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

Closing due to inactivity.

There you go https://krydos.heliohost.org/72/phpinfo.php

Your file has dos line endings, which usually means you created the file in windows and then uploaded it. You need to use an editor that understands and can write linux line endings before you upload it, or more easily just create the file through cpanel and copy/paste the code in.

Closing due to inactivity.

Yeah, I was out of town for a while so I was only taking care of emergencies. Can you link to the google page insight report? I think it would be beneficial for sites hosted on our servers to be able to achieve 100%.

Do you want to use 7.0, 7.1, or 7.2 instead?

On hold pending the outcome of https://www.helionet.org/index/topic/34289-why-was-my-account-suspended/

Your username is actually lemonion, but I found it. There you go http://sanjiaopants.com/test.aspx

Most of your load was coming from /home/ioixd/public_html/script.cgi Let us know when you're ready to fix (or delete) that file and your account can be unsuspended.

Changing your DNS doesn't affect your account at all. It just may make your domain inaccessible, but you'll still be able to login at https://www.heliohost.org/login/ If you give us a more specific example of what DNS settings you're changing and why we could help you further.

What is your username or main domain? Sorry I didn't ask last time, but I assumed your username was gvrp. Your forum email address doesn't match a hosting account either.

The script that flags accounts as inactive malfunctioned.

Which version of php are you using?

This is how I do asynchronous php processes which doesn't require anything extra to be installed: $mh = curl_multi_init(); for ($i = 0; $i < $counter; $i++) { $ch[$i] = curl_init(); curl_setopt($ch[$i], CURLOPT_URL, "https://krydos.heliohost.org/script.php?c=".$codes[$i]); curl_setopt($ch[$i], CURLOPT_RETURNTRANSFER, true); curl_multi_add_handle($mh, $ch[$i]); } $running = null; do { curl_multi_exec($mh, $running); } while ($running); for ($i = 0; $i < $counter; $i++) { curl_multi_remove_handle($mh, $ch[$i]); } curl_multi_close($mh);

Is it working now?

This account was reported to me by google as being a harmful site. So it could have been malware, viruses, phishing, social engineering, etc. Looking at his files it might be that someone gained access to upload files onto his account which may have been later deleted prior to the suspension. Google doesn't provide support of any sort so there is no one to ask what the issue was, but from years of experience this would have been the first time a google report like this was a false positive. Since the domain was suspended the google dangerous site warning has been removed, and there is no way to see what file(s) or page(s) originally created the warning in the first place. I'm willing to unsuspend the site if the user wants another try, but if google reports this domain as harmful again it will just be suspended again.

Remote access enabled.