wolstech

Not sure if this can be done or not. Escalating.

Glad to hear you got it working Feel free to let us know if you need anything else.

We would have to upgrade/rebuild php (and some sites say apache too), which we don't have any immediate plans to do on our existing servers. Our new server (which we have no timeframe for putting online at the moment) will eventually have whatever version comes with php 5.6 and whatever cpanel version we install, so it'll probably be recent. I recommend looking for a program that doesn't require it.

The standard is for the registrar to not require this. Sometimes you can ask the registrar's support to set the name servers for you (let them know that the host requires it before you can add the domain to the nameservers). The workaround for making these annoying registrars work with our service is to temporarily make the domain in question the main domain on your heliohost account temporarily (use this script). Palmsoft.heliohost.org will be replaced with dota-iq.de (and palmsoft.heliohost.org will stop working). Once you do this, change the name servers at the registrar and let everything start working. After that, change the main domain back to palmsoft.heliohost.org and let that start working again. Finally, add dota-iq.de as an addon or parked domain in cPanel so both are associated with your account. The other alternative is to transfer the domain to a normal registrar.

To move to Stevie, back up your data then delete your account here: www.heliohost.org/home/support/scripts/delete After that, wait 24 hours, then sign up again. The original copyright infringement issue seems to be fixed. [solved]

The mp3 files as well as any other links to illegal music on your site. You cannot offer free music downloads since you do not own the rights to the songs.

You were suspended for copyright infringement. You have 24 hours to remove all infringing material from your site, starting at the time if this post. If the content is not removed within 24 hours, you will be resuspended.

It can take a few days sometimes. Please be patient.

We'll see what Krydos says. We frown upon doing this though for security reasons. @Krydos: His account is aion on Johnny. He doesn't operate the server he's trying to monitor, so setting the game server to use existing ports is not possible.

We don't generally open ports for users. Our recommended solution is to reconfigure your game server to use a port we allow (all standard web ports, 2082, 2096, 8080 are permitted). There's one or two others as well if you're on Stevie.

You can do this easily. In cpanel, go to Remote MySql and add the IP address of the remote server that will be connecting to us. If you dont want to filter by IP address, a % sign will allow anything with the right username and password to connect. On your remote server, configure your script to use Stevie.heliohost.org or Johnny.heliohost.org as the host name (use the one for the server you're on). Username and password will be one of the database users you've set up under MySQL databases in cPanel.

You're welcome

Delete your account here: http://heliohost.org/home/support/scripts/delete Wait 24 hours, then sign up on Stevie. Domains on Stevie usually set up within 24 hours of registering, and the uptime is much better (around 99%).

Delete the users and recreate them. Then reassign them to your databases.

You're supposed to use NS records pointed to ns1.heliohost.org and ns2.heliohost.org. Once you do that, everything else will configure itself. Using an A record will cause a lot of functionality to not work without extra manual configuration on your main domain, and is not supported at all on addon/parked domains.

Johnny accounts can take up to a week for the domain to start working.

The headers already sent error is because setcookie() is just like the header() function. You can't use it once output has been sent. In your case, that output is being sent by whatever is on line 13 of db.php (the output is probably an error of some sort since DB classes don't usually produce screen output unless they're not working properly). The session_destroy() error is because you didn't start your session. You have to initialize it using session_start() before you can destroy it.

You were suspended for high server load, and when I unsuspended you, you were immediately suspended for inactivity. Your account has been unsuspended and renewed.

It should show in cPanel on the left side. I tried to look it up for you, but your account's domain isn't currently hosted with us so I can't.

That query won't find the user if the password is wrong. I generally do two queries, one to find the username, then one to check the password. That way I can tell if the user doesn't exist or if their password is just wrong. Other than that, the issue may be with the num_rows being on the end. What class is $db an instance of? In all the examples I've seen, the normal mysqli class doesn't let you put num_rows on the end like that. I usually see something like: $somevariable = $db->num_rows; though if($db->num_rows > 0) { /* Do Something */ } might be better for your use.

Do not bump posts. We work from the bottom up, so bumping puts you last in line. Moved to customer service.

Some things to look at: ($err !== false ? '<div class="error">'.$err.'</div>' : null); This is likely why it's broken. You need to use an IF statement. The ? : format requires PHP 5.4, which is not available on Stevie (which has 5.3.8). You will need to go through your code and rewrite these as IF statements. The conditional should also be != not !==. I personally would use !empty($err) instead. if(empty($uname) || empty($pass) || empty($uname) && empty($pass)) $err .= $t['er_login']; No need for the "empty($uname) && empty($pass)" part in these IF statements. As soon as one of them is empty, it's true, and the other one doesn't matter. md5(input($_POST['pass'])); Use SHA1. You also should salt your passwords.

The start of line and end of line are not required. Also, it's easier to check for the presence of bad characters as opposed to making sure they're all good. <?php $nick = "TEST33%"; if (!empty($nick) && preg_match("/([^a-zA-Z\d_-])/", $nick)) { echo "Invalid characters"; } else { echo " It's good. "; } /* Produces output: Invalid Characters */ Change the first line to a valid name and it will produce "It's good" instead.

If you want to only allow a single - or _ symbol as the input, use an IF statement instead. There is no "range" for symbols in a regexp, and you'll probably have to escape a bunch of them with a \ since some are modifiers in regexps. Regexps really are most useful when doing complex searches/pattern matching or when you need to accept large ranges like a-z or 0-9, as opposed to a few allowed characters. An IF like this would be easier if a single - or _ should be the only thing allowed: <?php if ($input = "_" || $input = "-") { //Do something } else { //Error message } ?>

It means your regular expression is incorrect. Can you post that line of code so I can see the expression in question?