Krydos

It looks like mysql on Johnny restarted itself right around the exact time that you posted this thread. It didn't crash it doesn't look like. During a restart there can be a little downtime. If you want better mysql uptime and stability I recommend transferring your account to Tommy. Mysql on Tommy hasn't restarted in 20 days, and I think I manually restarted it anyways.

Deployed. http://hkaldane.heliohost.org/Website/

There you go http://esp-diego.mg/

Maybe try deleting the whole thing and installing it again instead of upgrading? I just installed phpmyadmin on Tommy and didn't get any errors, but I didn't have an old version to try updating.

Alright! Create a folder in public_html called flask /home/username/public_html/flask/ In that folder create a .htaccess file: /home/username/public_html/flask/.htaccess RewriteEngine On RewriteBase / RewriteRule ^(media/.*)$ - [L] RewriteRule ^(admin_media/.*)$ - [L] RewriteRule ^(flask\.wsgi/.*)$ - [L] RewriteRule ^(.*)$ flask/flask.wsgi/$1 [QSA,PT,L] Create a file named flask.wsgi import os, sys # edit your username below sys.path.append("/home/username/public_html/flask"); sys.path.insert(0, os.path.dirname(__file__)) from myapp import app as application # make the secret code a little better application.secret_key = 'secret' Create a python script named myapp.py import sys from flask import Flask, __version__ app = Flask(__name__) application = app @app.route("/") def hello(): return """ HelioHost rules!<br><br> <a href="/flask/python/version/">Python version</a><br> <a href="/flask/flask/version/">Flask version</a> """ @app.route("/python/version/") def p_version(): return "Python version %s" % sys.version @app.route("/flask/version/") def f_version(): return "Flask version %s" % __version__ if __name__ == "__main__": app.run() Here is the working example: https://krydos.heliohost.org/flask/ This will only work on Tommy at the moment. Feel free to play around with it and let me know if you have any issues. If everything is working I'll see about writing up a wiki and making a news post about HelioHost now supporting flask.

That looks pretty close to what I use.

There you go http://quickpaydayloansrjnsh.com/

Just use .htaccess. Even I don't really have access to virtualhosts. Cpanel gets very angry at me when I mess with httpd.conf.

Thanks a lot! I'm sure this post will help a lot of people.

You have to select the database first otherwise it tells you "No database selected".

To import a .sql file go to https://ricky.heliohost.org:2083/frontend/paper_lantern/sql/PhpMyAdmin.html Select the database, and click import.

You choose the Johnny server which is our experimental server. This means he can be rather unstable quite a lot of the time because of high load. When Johnny is experiencing high load adding a domain can sometimes break or fail halfway through. Our stable production servers, Tommy and Ricky, don't experience these kinds of problems.

...this one should be pretty self explanatory... The table settings doesn't exist: mysql> use exploit_database; Database changed mysql> show tables; Empty set (0.00 sec) Do you have a .sql file you meant to import perhaps?

The postgresql user cthieme_admin should now be able to remotely access the postgresql database cthieme_tales from any IP.

You didn't add permissions for that account on that database.

Deployed. http://llou21.heliohost.org/roadangel/

It looks like the load might be tapering off a bit. Try resetting your password now.

Your account is located on Johnny which is our experimental server which means that it can experience high load quite frequently. Looking at the server monitor http://heliohost.grd.net.pl/monitor/ you can see that Johnny has been having some pretty high load lately. Keep an eye on the image below because logging in might time out or fail if the load is above 10-15: Our stable servers, Ricky and Tommy, don't experience these high load spikes so uptime is a lot higher.

I checked the change password log, and it looks like the failure reason was high load. Your account is located on Johnny which is our experimental server which means that it can experience high load quite frequently. Looking at the server monitor http://heliohost.grd.net.pl/monitor/ you can see that Johnny has been having some pretty high load while you were trying to change your password. Keep an eye on the image below, and logging in or changing your password might time out or fail if the load is above 10-15: Our stable servers, Ricky and Tommy, don't experience these high load spikes so uptime is a lot higher.

$myhost = "localhost"; $myuser = "exploit_user"; $mypass = "whateveryourpasswordis"; $mydb = "exploit_db"; You create your database at https://ricky.heliohost.org:2083/frontend/paper_lantern/sql/index.htmlYou create your database user, and password on that same page. You add permissions for that user to your database on that same page too.

Here's why you were blocked: # lfd: (cpanel) Failed cPanel login from x.x.x.x (AU/Australia/x-x-x-x.static.tpgi.com.au): 5 in the last 3600 secs - Fri May 26 04:57:52 2017 Make sure you're logging in with the right password. Sometimes people get the wrong password saved in their FTP client or something and it just keeps trying to log in with the wrong password over and over. Your block has been removed.

Deployed. http://sh4.heliohost.org/TestWeb/

You should now be able to remotely access the postgresql database rverah_captum with the postgresql user rverah_admin from any IP.

I made some changes to the deploy script. Now if your filename already starts with your username and an underscore it doesn't append another username and underscore to the front. So if your file is blog.war then it becomes xitix_blog.war. If your file is xitix_blog.war it stays xitix_blog.war. That should solve a lot of your path/session issues I believe. Deployed. http://xitix.heliohost.org/xitix_blog/

If you log in at https://www.heliohost.org/login/ and then click the top cpanel button you will log in with https. If you click the bottom cpanel button labeled "insecure" it will log you in with http. The reason we provide insecure logins is because our secure logins are on port 2083 which a lot of companies and schools block random ports like that. If the secure login doesn't work for you then you still have an option to log in on port 80 with the bottom button.