Jump to content

Krydos

Chief Executive Officer
  • Posts

    24,202
  • Joined

  • Last visited

  • Days Won

    855

Everything posted by Krydos

  1. According to https://forum.vestacp.com/viewtopic.php?t=12995 it looks like your server just needs a reboot to make exim start working right again. Want me to do that for you?
  2. Thank you for making this a post rather than a PM. I always forget to check my PMs, and I've never even attempted to provide support through PMs before you. I'm not ignoring you, I've just been really busy lately with work and real life. You say you're worried about making HelioHost look bad with all of your VPS issues, but there are a couple things here. First, HelioHost has always been completely open and transparent about our strengths AND our weaknesses. Most businesses try to hide everything behind ticket systems where no one can see anyone else's problems. The main problem with that is it increases the workload for the staff because they have to deal with the same problems over and over, where on a forums like we have here anyone can search for their issue and see how other resolved it in the past. Not only does this make things easier for our staff, but it also gives new volunteers a chance to help out, and become promoted to admin themselves. We recently promoted Flazepe for this exact thing. He helped out a lot without asking anything in return, and we gave him a promotion so he can help out even more. Even I was just a regular user looking for customer support a long time ago. I liked the concept that I just outlined, and started helping out myself. Maybe Flazepe will have my job some day. Who knows? Anyways, my point is if someone else has this same sort of VPS issue in the future they can read this thread to see things to try. Second, you're not making HelioHost VPS look bad because you're the only person, out of about 20 right now, that is having these sorts of load issues. It's much more likely it's a software issue than it is any kind of "hardware" issue that would indicate HelioVPS are poor quality. Don't worry about making us look bad by posting publicly. In your screenshots it looks like vesta is still doing updates on its own, which is odd because I unchecked the box for auto-updates, and it appears to still be disabled. You can see it called v-update-sys-rrd. We discussed this before you even bought the VPS. You asked basically, "How will we know if my VPS needs more memory?" This here, exactly what is happening with the load spikes, is what lack of memory looks like. My offer stands: I'll give you double memory for a week for free. If the load spikes get better or go away completely you can make the decision to continue paying for the extra memory after that. I really think this is the best solution. I'm checking on your mail issues now. I'll edit/post again when I have information.
  3. @robev, have you tried removing the domain, and re-adding it yet? If so please let me know and I'll take a look at it.
  4. That's just a shell script to install https://github.com/tpruvot/cpuminer-multi @wolstech, will that mine turtle?
  5. It's working for me https://stockdiv.com/Stockdiv/Stockdiv
  6. I'm glad it's working for you now.
  7. Remote access enabled.
  8. Rather than letting tomcat create the file you could try creating an empty file yourself that tomcat has permissions to write to.
  9. They actually didn't stop; they're just that far behind on everyone else. The way they work is they process whoever is the furthest behind next. I ran logs on your account manually. That puts your account at the bottom of the list to have logs run next, and the server was trying to get caught up on the thousands of other accounts first before running logs on your account again. I once again ran logs manually on your account.
  10. Thanks. Fixed again.
  11. I replied on the PM. Sorry, you're the only person in the last 10 years that I've tried to provide support through PMs. As long as you don't mind some of your log files and stuff being public it would be easier for me to provide support through regular forum posts. Also you get the benefit of Wolstech or someone else chiming in with possibly useful information.
  12. One of the users who was having SFTP issues disabled his firewall and it started working. The odd thing was the firewall would let port 1342 work on the portquiz site, but would block port 1342 when filezilla tried to use it. Regular FTP on port 21 wasn't working for him either. It's possible these people all use that same firewall, and there was a recent change in the software.
  13. Try reading from the file now.
  14. Ricky SFTP works just fine for me. Make sure your settings look like this
  15. His second try was for FTPS which we don't support. We support SFTP and FTP, but not FTPS. First go to http://portquiz.net:1342/ and tell us what you see on that page. If it fails to connect that means your port 1342 is blocked by your firewall or your ISP. If you see "You have reached this page on port 1342" then the next step is to make your SFTP settings in Filezilla look like this
  16. Since your code sample has all of the useful information edited out I looked around on your account. I don't even see a select statement in the beta directory. Are you selecting from the table test like you posted or tea which actually exists?
  17. 5/24 at least.
  18. There you go https://fjmduran.heliohost.org/test.jsp and https://fjmduran.heliohost.org/TestHelioHost/
  19. Are you saying "Thank you!" that solved the issue or "Thank you!" for trying to help, but it's still not working?
  20. Pgsql for Tommy's php 7.2 has been installed https://krydos.heliohost.org/72/phpinfo.php
  21. Did you give $dbUsername select access on the database $dbName?
  22. I'm not seeing any nameservers set for that domain https://bybyron.net/php/tools/dns_records.php?domain=sweetshug.ga&rec=NS Maybe log in to freenom and check your settings there again. Keep in mind that freenom is really slow at updating their stuff sometimes.
  23. Remote access enabled.
  24. Unfortunately a 500 error is the best you're going to get for most python scripts. In your particular case you're using an incorrect shebang. If you want to use python3.6 use #!/usr/bin/python3.6
×
×
  • Create New...