Krydos

Did you try resetting your password at https://www.heliohost.org/reset/ or at https://johnny.heliohost.org:2083/resetpass?start=1 ?

The postgresql user fluctus_Flctus should now be able to access the database fluctus_myDb remotely from any IP. Let us know if you still can't connect or have any other issues.

Do you want access from any IP or more securely from just one IP?

Is this instead of your existing port 21715 to 158.69.57.87 or do you need both?

Glype, and other web proxies, are not illegal on our servers. In fact (without getting too political) the admins at Heliohost strongly encourage the use of proxies, and encryption, and vpns, and tor, and anything else you can use to keep your data transfers on the internet secure. These techniques also reduce the chances of someone (or some government) spying on your communications. The problem is glype and other proxies can cause a LOT of load sometimes, and the server will have no choice but to automatically suspend the account that is causing the abnormally high load in order to return full performance to the thousands of other accounts which share your server. But you can hack glype and other proxy scripts by editing the code to cut out automatically if the server load becomes to high. This should greatly reduce or completely alleviate the chances of your account getting a high load suspension. For glype you can edit index.php and browse.php and add this to the top: $load_array = explode(" ", file_get_contents("/proc/loadavg")); $load = $load_array[0]; if ($load > 10) { echo "ERROR: Load too high."; exit; } What this does is looks at the average load of the server over the past minute, and if it is greater than 10 the proxy will just show the error message instead of continuing to raise the server load. The server won't actually start suspending any accounts until you cause the load to exceed 15, but 10 is safer. It *IS* still possible to get suspended for high load even with these edits, because the browse.php script especially can run for quite a while and if the load gets too high while the script is already running you could still get suspended, but it should be a lot less likely. The size of the webpages you're browsing with your web proxy, and the speed of your internet connection is what your suspension chance depends on. By the way, if you do end of getting suspended anyways please don't panic. Just make a post at http://www.helionet.org/index/forum/81-suspended-and-queued-accounts/ or get in contact with us some other way and we'll be happy to help you get it sorted out.

Is it working now?

Can you link to a page that is throwing a 500 error?

Try this: Go to https://johnny.heliohost.org:2083/frontend/paper_lantern/sql/index.htmlScroll down to add new user.Enter a username (eg: kxk06010_user1), password, confirm password, and click create user.Repeat step 3 twice more to create kxk06010_user2, and kxk06010_user3, etc.Scroll down to add user to database.Select the kxk06010_user1, select the database kxk06010_autopartstore, and click add.Check the appropriate permissions required, and click make changes.Click go back.Repeat steps 5-8 to grant access to kxk06010_user2, and kxk06010_user3 as well.Check to see if all three of you can connect to the database at once after following the above procedure. Let us know if have any questions or issues.

You should be able to have four persistent connections open at once the way it is already. I see two connections to your account from the same IP. Are you saying that each of your three team members needs to have two connections open at once?

Go to https://johnny.heliohost.org:2083/frontend/paper_lantern/softaculous/index.live.phpLog in with your cPanel username/password.In the top left corner there is a search box. Type phpmyadmin, and click the resulting link.Click install now.Scroll down and click install.Wait for the installation to complete.Click the link to go to http://barcodenetbar.com/myadmin/Log in with your cpanel username and password.If you did everything correctly you should now see your databases in the left navigation pane. Let us know if you need more help.

Yes, you could host less files, or compress them to reduce space.

That seems like a terribly inefficient way to store files, but the combination of all of your files plus your databases cannot exceed 1000mb.

Finally, you explain your actual reason. Disk space is not an approved reason to create multiple accounts. We recommend hosting large video files, etc on an external service like dropbox if it is too much for your one account.

I'm sorry, but I really don't understand why you need two accounts when you can have as many websites as you want on one account. Let us know if you think of a way to explain it. Plus it would be a lot more convenient for you to just need to log in to one account to manage both websites instead of having to log in and out all the time. Your friend can certainly create his own account if he wants, but if you log in to both accounts you'll run the risk of them both getting suspended.

Why do you need two accounts then? You can host as many domains on one account as you want so just create an addon domain for his site.

This account caused some considerable downtime on Tommy around 2200 UTC http://heliohost.grd.net.pl/monitor/archive/?2017-04-19

@javier83 since we only allow one account per person it flagged our system as rather odd when 19 accounts were created from the same location within minutes of each other. Please recommend to your teacher or anyone else who might seem like they're creating more than one account to let us know in advance.

You can host as many domains as you want on your one existing account.

That Bob guy is a nut!

We've had some issues with the cpanel phpmyadmin running slow, and that could be what is causing the 500 errors. You could also try installing phpmyadmin through softaculous and import your database through that.

Wasn't the cl58 thing just a prettier version of http://wiki.helionet.org/Heliohost_FAQ ?

Try downloading the backup for the Stevie account cl58. It should have the data there. I would actually prefer to have it recreated on the wiki though rather than a hosted account in case the hosted account goes inactive, or the server crashes or something.

Weird that it requires admin permissions to edit. I wonder if Xaav had it locked down purposefully so random users can't edit the terms of service. That would make sense I guess.

How about now?

Can you edit them now?