Jump to content

Krydos

Chief Executive Officer
  • Posts

    24,851
  • Joined

  • Last visited

  • Days Won

    885

Everything posted by Krydos

  1. Well, like I said in the other thread that you read, express doesn't like being in a subdirectory. So I edited your application manager, and instead of having it in the /riddleadventure/ subdirectory I moved to to / and it works now https://express.jax.heliohost.us/homepage/home
  2. In mysql it is common practice to have a user with the same name as a database, but in postgresql it isn't allowed. Please provide a user that doesn't have the same name as an existing database.
  3. My personal test vps has been running for over a year. During the last 12 months I've had about 140 minutes of downtime. There were two scheduled maintenance during that time that were probably about an hour each, but they were both announced several days in advance, and then another 20 minutes of random stuff like me rebooting my own VPS. That's 99.97% uptime for the whole year. A lot of users don't have as good of uptime because they do silly things like install a gui on a headless vps and end up crashing the server with a memory leak and stuff like that. Things that are perfectly avoidable if you know what you're doing like Wolstech says. Your uptime mileage will vary depending on how many mistakes you make. Don't be too scared though. Vps are a great opportunity to learn if you're willing to do some google searching for command line instructions. No matter how many mistakes you make you can always always just give up and say "wipe it clean!" and I'll reinstall the os for you and you can start over with a brand new fresh operating system again. It's not a big deal at all to reinstall the os, and I don't mind giving people pointers or instructions if they get stuck. You or I can probably google up a guide for you to do whatever you're trying to do and then you can just follow the instructions. If you want to try one out for 3 or 4 days just let me know and I'll spin up a basic 2 GB memory, 2 cpu, and 50 GB hard drive vps for you to try out for free. Then if you want to keep learning after you've tried it for a few days you can pay $4 to keep the vps you have for a month or you can upgrade to a faster machine and go from there.
  4. I got the bitcoin payment, and your vps credentials have been emailed to you.
  5. Remote access enabled. Unfortunately cPanel does not provide remote postgresql. I think postgresql is sort of an afterthought for cPanel because the version that they provide is pretty ancient too. I may write a remote postgresql plugin myself some day, but there are a lot of things that have higher priority.
  6. Remote access enabled.
  7. Yes, you can do 12 months up front through bitcoin for a 10% discount. So 2 GB memory, 2 cpus, and 50 GB hard drive would be $43.20 for a year. Go ahead and submit the form at https://www.heliohost.org/vps/ and then close it when it gets to the payment part. Then let me know here that you made the transaction and I'll get you all set up.
  8. Unarchived.
  9. Remote access enabled.
  10. You're on Tommy now. I have also increased your storage to 2000 MB, and you don't need to log in to cpanel to keep your account active until 2021-06-17. Let us know if there is anything else we can help you with. Thank you so much for your donation!
  11. Remote access enabled. You also win the award for longest database name and user name, which makes the nice neat columns in my config file all messed up. Haha. Oh well. Rip readability.
  12. I think you're confusing and combining guides. The discord bot guide is more applicable to what you're trying to do I think. https://wiki.helionet.org/tutorials/discord-bot This guide is for starting and stopping a bot that runs more or less constantly. You'll still want to use python cgi to start and stop your bot, but instead of a python script for the bot you'll be running a node script. This is a passenger node.js guide. https://wiki.helionet.org/tutorials/node.js This guide is for setting up a node.js website through passenger. The way passenger works is when someone requests your page passenger starts up the node app and the visitors gets to interact with the website. Then after the website visitor goes away passenger stops the node app to save system resources. This obviously won't work well for a bot because you don't want your bot to only be online for 5 minutes everytime someone visits your website.
  13. Literally all I did was log in to your account and click the button to enable your node app in the application manager, and now it works. http://bot.cmh.heliohost.org/ Something you may not be aware of is this Source: https://wiki.helionet.org/tutorials/node.js
  14. Your VPS had a process with a memory leak of some sort. It filled all available memory and filled all the swap too, and was maxed out on cpu usage and hard drive usage. The console was completely unresponsive so I did a hard power reset and it seems to have booted up ok now. You might be able to figure out what process went nuts and used up all your memory by looking through the system logs.
  15. Posted on discord:
  16. There you go https://krydos2.heliohost.org/73/phpinfo.php
  17. There you go https://krydos2.heliohost.org/cgi-bin/modules37.py
  18. Remote access enabled.
  19. Remote access enabled.
  20. We have a lot of younger users so we can only allow up to pg13 not pg8000. https://krydos.heliohost.org/cgi-bin/modules37.py
  21. Remote access enabled.
  22. Remote access enabled.
  23. It was like 3am last night when I got done working on Johnny and I forgot to re-enable some of my stability scripts. What you see there is what Johnny's performance would be with stock cpanel and apache settings without any of my code involved. As soon as I re-enabled my code it settled down to normal again. It wasn't a complete loss though because letting Johnny go wild like that allowed me to analyze some of what causes so much instability and I made some adjustments to my code which should help Johnny, and maybe even Tommy, be more stable in the future.
  24. Here is the output of your bot: MySQL has been connected! [ RowDataPacket { guildID: '700047xxxxx0608151', setting: '.', value: null, createdAt: 2021-03-28T20:31:06.000Z, updatedAt: 2021-03-28T20:31:06.000Z }, RowDataPacket { guildID: '775927xxxxx5018378', setting: '.', value: null, createdAt: 2021-03-28T20:50:39.000Z, updatedAt: 2021-03-28T20:50:39.000Z } ] Aesir-Wolf-Pack#0694 is online! I edited out some of the guildID in case that's private. Not sure. Anyways, since your bot starts just fine, it's up to you from there to log errors yourself from inside the bot's code. Don't rely on console.log(), and definitely don't rely on python. The python just starts the node code, and then disconnects from it to let it run on its own. Just write the logs to a file. Log file permissions can be tricky sometimes for non-linux people. The way I would do it is create an empty file that has write permissions on it and then have the bot append to that. If you have the bot try to create it's own files then you need to worry about directory permissions too, but if the file is already created it's less to figure out.
×
×
  • Create New...