wolstech

Great to see it's working for you Please let us know if you need anything else.

Krydos can add this for you.

I'm assuming in the SELECT you remembered to actually replace "dbo" with the real database name? I was able to run the function as below through PhpMyAdmin and got a response from the function: SELECT `DATABASE_NAME_HERE`.`random_text_answer`(); The user kanvull_main is assigned to the database, so while I can't test using that user easily, I see no reason it wouldn't work provided the database name is correct in the SELECT statement.

Closing as duplicate of https://www.helionet.org/index/topic/54871-sql-priviledges-issue/

Comment the Options +ExecCGI line out in the .htaccess file and see if it works. The Options directive isn't supported on Plesk yet (though Krydos does plan to fix that at some point I believe).

Please check the email address associated with your account for an email containing a link to change your password.

Try logging in at https://johnny.heliohost.org/ instead. If that doesn't work, let me know and I'll email a password reset link to you for the hosting account.

Changed. It may take up to 2 hours to work.

What do you want the domain changed to? Since that's your main domain, it has to be changed to something else to replace it (an account cannot be domainless). Do you just want it to be amarks.helioho.st?

I assume you mean Johnny since that's where your account actually is. The account is not suspended or anything. Do you want your password reset?

Email sent. Please check your email for a link to reset the password.

You're correct in that it goes in httpdocs. Your mistake was that you reused the existing index.html instead of deleting it and replacing with a fresh one. The default Plesk index.html that comes on a new account contains this script line: <script src="https://assets.plesk.com/static/default-website-content/public/default-website-index.js"></script> Which draws the plesk default page in the body of the page, ignoring whatever's actually in the file. When you want to replace the content, you either need to replace the file entirely, or delete that line out of the default file then edit the rest of it. Most people just delete the default index.html file entirely because they want to use a PHP script instead (index.php). I removed that line from the file for you and your page is working

I just checked...you used an email that's on a domain hosted on your account. Unless you're using external email service, you'll never get the move invite. Krydos will need to fix that first (he'll probably verify the account by having you create a file on it or something). In the future, please do not set the contact email address to a mailbox on a domain attached to the hosting account. If something happens and you can no longer receive email at that mailbox, you won't be able to receive emails to get your account back.

Please check your PMs.

What domain do you want the account to have? (Note that due to the DNS integration issues, Lily accounts require a domain with external DNS, they currently don't support using our own DNS so a free subdomain isn't an option). The easiest solution would be a freenom domain and cloudflare. EDIT: Nevermind, apparently I can create a subdomain for you. It'll be http://lily.dawid8.helioho.st/ once I figure out why it's showing as suspended. I'll send a PM when its ready.

Krydos can resend this for you.

It will likely be last, but yes. Lily will be a challenge to get Plesk working on since there are tons of projects running on Lily using weird custom stuff that is not compatible with it. Lily will likely lose some of its capability to run various things when it finally gets Plesk, though it will obviously be easier to use. For now, Lily is still available for users if they ask, but it works the same as it did on cpanel for the moment. You need a separate account on a Linux box, and Lily has no control panel.

Solved on discord. 6.3GB in error_logs...

Payment confirmed and space added. Escalating to Krydos because I'm not sure if I need to change the value in the accounts database or if that step does it on its own since I manually changed the account's subscription to the 2000MB plan in plesk.

Extra space is not free (it's $5 for 1000MB). Please post the transaction ID for the payment to have the space added.

Before we do anything you need to fix the severe disk space overuse on your account. You have a 1000MB account but it currently has 6816MB used, which is more than even our maximum shared hosting plan allows (5000MB, which costs $20, it's $5 per 1000MB). Please let us know what to delete (and if you'd like to get more space so you can delete less, please send the money via Paypal and post the transaction ID so we can add the space to your account). Escalating to Krydos since if I remember right you can't delete the files yourself. There's also several domains that aren't hosted with us on your account. Do you plan to host these here? appwebbrowser.com (not hosted by us) comprarappandroid.com (not hosted by us) appstursoft.es (not hosted by us) buyandroidapp.com (not hosted by us) If you want to keep everything you currently have, you'll need to buy a VPS.

Also just a heads up that your account's contact email looks like its set to an address hosted on the account. We don't recommend doing this as you won't be able to receive things like password resets or various service notices this way (if you forgot your password, you won't be able to check the email to get the reset link...).

Fixed. it was because you had the option for wildcard certificate enabled (we don't support wildcard certificates at the moment due to lack of DNS integration). I turned that option off and reissued it...it succeeded. It may take up to 2 hours for the new cert to take effect.

I can't get into Plesk to look at this at the moment due to the server being too slow. We'll take a look at this later once performance improves.

It's probably server load. I can't even load webpages from the server at the moment, and it looks like we were down overnight for an hour or so as well for an unknown reason (guessing either HE issue or DDoS again). That said, the server is able to reach api.telegram.org (ping from Tommy2 to that API came back with round trips averaging 139ms), so it's likely that the server is just too slow to actually process these GETs without timing out. I would suggest trying again later once performance improves.