Jump to content

yashrs

Moderators
  • Posts

    1,065
  • Joined

  • Last visited

  • Days Won

    54

Posts posted by yashrs

  1. Hi - I did not understand your exact issue. You should be able to login using the VPS credentials that you entered during the signup. Please describe the issue in more detail for us to understand and address it

  2. The DNS entry has been setup => vps67.heliohost.us now points to your VPS IP.

    59 minutes ago, ballagyr said:

    If I put this "HestiaCP", will this task be easier and optimized?

    Yup it can automate Lets Encrypt certificates as well. But as you already have setup Apache and Let's Encrypt, it should be good to go!

    Regarding pointing another domain to your VPS, just create an A record on the domain (say abcd.com) by going to their domain control panel (like GoDaddy) to 65.19.191.150. Then you'll need to add a VirtualHost in Apache corresponding to that domain.

  3. Hi @ballagyrm, We will add an A record to vps67.heliohost.us soon, it was a miss from my end - that's why it is not responding to ping. We usually add the A record before sending the VPS email itself.

    Regarding hosting, the VPS comes with only a fresh OS installed. To use, Apacha/Nginx you will have to install them manually and configure them or you can use a free control panel software like HestiaCP on your VPS.

  4. @robev - It should be working now.


    Apache and PHP FPM services weren't working. Restarting those services fixed it.

    Before

    # v-list-sys-services
    NAME          STATE    CPU  MEM  UPTIME
    ----          -----    ---  ---  ------
    apache2       stopped  0    0    0
    php7.4-fpm    stopped  0    0    0
    nginx         running  0    10   226
    bind9         running  0    77   227
    exim4         running  0    5    220
    dovecot       running  0    0    227
    spamassassin  stopped  0    0    0
    mariadb       running  0    385  227
    vsftpd        running  0    0    226
    cron          running  0    0    226
    ssh           running  0    2    226
    iptables      running  0    0    0
    fail2ban      running  0.4  137  226

    After: 

    # service apache2 start
    # service php7.4-fpm start
    # v-list-sys-services
    
    NAME          STATE    CPU  MEM  UPTIME
    ----          -----    ---  ---  ------
    apache2       running  0    445  0
    php7.4-fpm    running  1.8  8    0
    nginx         running  0    10   228
    bind9         running  0    77   228
    exim4         running  0    5    222
    dovecot       running  0    0    229
    spamassassin  stopped  0    0    0
    mariadb       running  0    385  228
    vsftpd        running  0    0    227
    cron          running  0    0    227
    ssh           running  0    2    227
    iptables      running  0    0    0
    fail2ban      running  0.4  137  227

     

  5. @jnorden - The system didn't respond to ssh nor to ping during our initial tests. So, we reset the password first. After resetting and logging in, we tried viewing the ufw settings, and they looked fine to us. After checking again, it seems to just have started working on its own after that. We have sent the new password to you via email. Let us know if you have any other questions.

    5 hours ago, jnorden said:

    Also, does the data center and/or vmware provide any  outside firewall?  To protect, eg, against ddos attacks?

    Not by default. You could use Cloudflare or similar services to protect against it.

    • Like 1
  6. We don't allow exec and shell_exec for security reasons. However, if you have only one or two commands to run, you could use the cron jobs to run that. Please do note that there's a limit of 2 cron jobs per day. 

    If your application requires it for continuous use then I am afraid it wouldn't work.

    • Thanks 1
×
×
  • Create New...