wolstech

Cron again. There's a section in cpanel for crons. I recommend that you check them and assuming you only have 1 job, make sure it's not set to run more often than once every 12 hours. One of your programs probably created a cron set for a few minutes or something. A lot of software will do it when it's installed, and some do not tell you.

Your account was suspended for running too many cron jobs. To help keep load low, we limit accounts to two (2) cron executions in a 24 hour period. This means that, if you only have a single job, it can run no more frequently than once every 12 hours, with two jobs, they can each only run once a day, and so on. Your account has been unsuspended. To add to this for your specific case, there are a lot of programs in Softaculous that create crons during installation. Because we limit the number of crons per day, we recommend that when installing programs from Softaculous, you should disable the cron installation and create it manually so you can keep your account within the limit.

Glad to see you got it working Let us know if you need anything else.

This should be closer to correct, though I didn't test it and there may be syntax errors. Your issues were both the SQL syntax described above, and also your IF statement was wrong. mysqli::query() doesn't return a boolean TRUE when you run a SELECT, it returns a mysqli_result object instead. Your IF was explicitly looking for a Boolean true, but since the function doesn't return true when a SELECT succeeds, the else section always runs (there's no database error, hence why $db->error was empty). The quick way to check if a mysqli::query() was successful is to check if the returned value is empty(). Boolean TRUE (the result of an INSERT, UPDATE, etc.), mysqli_result objects (the result of SELECT), etc. are considered to be non-empty. Boolean false from a failed query is always considered empty. <?php $db = new mysqli("localhost", "root", "", "default_db"); if ($db->connect_error) { die("Connection error"); } else { $sql = "SELECT * FROM users WHERE `nick` = '$u'"; $result = $db->query($sql); if (!empty($result)) //Check that it's not empty. Non-empty queries are successful. { $data = $result->fetch_array(MYSQLI_ASSOC); echo $data['email']; } else { echo "Query error: " . $db->error; } } ?>

SELECT * FROM 'users' WHERE 'nick' = '$u' Should be: SELECT * FROM users WHERE `nick` = '$u' You used the wrong type of quotes. You need the ` symbol (the one to the left of the number 1, above the tab key), not the ' (apostrophe). around the field names. If you want something around the table names, you should use these there too, though the code will work without anything around the table name.

You're indeed suspended too many cron jobs. The limit is 2 per day. Unsuspended.

It's already suspended for the second time. Escalating so Krydos can check on the file causing this.

Your account was suspended for causing high server 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. If you still see the suspended page, please clear your cache.

A 503 Service Unavailable is indeed because you didn't request ASP.NET. Escalating to have this installed for you.

I bought a .com back in 2014 when i lost that .tk, so I have a domain...was on a road trip at the time and seeing it needed to be fixed asap, i had to buy it, set it up, and reconfigure a whole boatload of things using only an iPad and Bluetooth keyboard on free wifi at hotels and coffee shops...I still hate freenom for that. Do I actually qualify for the free domain promo? I was under the impression that being an admin meant I didn't (kind of like how employees of a company holding a contest can't enter). Because if I can, I have almost 10 years worth sitting there and I easily make 400 posts a year.

They cancelled a domain of mine back in 2014 for no reason...not surprising. Took me 2 years of constantly trying to reach them to find out why it wouldn't let me re-register it. They fixed that, then banned my account the same day for abuse despite having zero domains registered (and of course, were of no help when I asked why, just pointed to an FAQ saying what I already knew). Did get the domain back eventually...2.5 years later (lost in June 2014, got it back Dec 2016). Needed it since I have PCs across the country with software that expected to find my site there. Once they connected again, updates immediately got shipped to reconfigure them to my .com. I hate Freenom.

I'm not sure. It should work assuming the cert is installed correctly. Escalating.

It means your SSL is incorrectly or incompletely configured. Mine shows the same random site since I don't use SSL: https://www.raxsoft.com Our system currently shows that random website when a domain is not associated with an account, or when you visit a non-SSL domain over SSL...it's a bug we've had since Tommy was built and is related to the fact we currently don't have things like queued pages.

It's been renamed to bfwebext2. I'll rename it back once you register successfully.

That account failed to create. The cause of failure is: You'll need to sign up again. Also be aware you cannot reuse the username bfwebext unless you have me rename your forum account first.

The username for that account is alljoe. It has a gmail.com email address associated with it. If you need your password changed, go here: https://tommy.heliohost.org:2083/ and pick the reset password option.

Not without deleting your account, asking us to rename your forum account, signing up again when registration opens, then asking us to rename your forum account back.

That's because your nameservers are still incorrect. http://bybyron.net/php/tools/dns_records.php?domain=Java1to3.com&rec=NS A correct domain looks like: http://bybyron.net/php/tools/dns_records.php?domain=raxsoft.com&rec=NS

That looks like the behavior I'm used to. Thanks

The reason I disagree with errors being off is that its a lot more confusing this way, especially for new users. Every other host I've used has errors on by default, whereas we produce a meaningless 500 error, and most won't know to look in the log/turn on the errors. Also, Stevie and old Johnny were both set to show errors by default. I didn't even realize they were off until I spent 45 minutes figuring out a 500 error...and discovered a missing semicolon caused it. I had expected the error to show up since I never disable them in my scripts.

@Krydos, why do we have error_reporting turned off?I've always wondered the same thing. The errors do log in the error_log, but don't show up on screen by default (and if they're fatal, you get a 500 error, which is useless). I've seen others asking about this too...only for the response to be "what's in the error_log?" Our old servers used to show the errors (E_WARNING and higher) on the screen by default and log them to the error_log, unless you specifically turned off showing them with an error_reporting(0); in which case they went in the log only. Can we get the old behavior back? It's much less confusing than the current settings.

Your code is broken. It will never work because the headers were already sent. You cannot have ANY html, blank lines (outside of Php block) or other output before session_start(). Once something sends output to the browser, it won't work. In your case, you need to delete the doctype line or move it so its sent by an echo statement after the session_start call. The headers are sent when that line is processed, then php tries a head cookie for the session and fails. You just aren't seeing the "headers already sent by" error because we have error_reporting turned off.

I'm not sure if there's a problem or not. Krydos is the one who would be able to check. Applications that use session IDs seem to work fine for me and everyone else here though, and I can see that my session IDs in the system I run don't change unless I do something where it should do so (such as logging out). I'd imagine there'd be a lot more complaints if this were broken. /tmp is writable on Tommy (script showing an is_writable("/tmp")...http://rax2.heliohost.org/temp/tmp.php). It's worth noting that on our servers, Apache runs as nobody, but PHP scripts run as the user who owns the script. We already support it, but you need to acquire and install a certificate for your domains. There's a guide on the wiki for using Let's Encrypt/ZeroSSL for a free one, but you need to get a new one every 90 days. You can get a paid certificate from a CA if you want one that lasts longer. We don't sell certificates. SSL can be set up from https://tommy.heliohost.org:2083/frontend/paper_lantern/ssl/index.html

Yes. Any time you add a domain or add SSL to a domain, we have to add the ASP.NET to the new domain (or to the SSL for the domain) individually.

That would do it. Try renaming your .htaccess so it won't redirect, then accessing your site over plain HTTP...it'll probably work. I'm pretty sure it has to be installed for the secure and insecure version of your domain individually, so he probably needs to redo it for the SSL version of your domain.