Jump to content

wolstech

Chief Risk Officer
  • Posts

    17,347
  • Joined

  • Last visited

  • Days Won

    640

Posts posted by wolstech

  1. For MySQL you can enable it yourself in Plesk (it's done by editing the database user, there's an option near the bottom for remote access).

    It's only postgres that needs an admin to do it.

  2. The only difference in the two is the payment model, the actual hosting service is the same.

    As with all things around here, there's no timeline for when will be releasing a subscription version of Morty since we're all volunteers and don't know when it will be finished.

  3. The prepay you put money in the account up front and the money is used as you go.

    The regular (subscription) Morty has a recurring charge to your paypal account at the end of each month to pay the bill instead of paying us up front and using the credit over time. This plan isn't available yet.

  4. 2 hours ago, gebu8f said:

    I would like to ask what is the billing principle of Morty Plan? I saw this paragraph "On Morty, you'll be charged for overages at the rate of $0.0005 per gigabyte of memory, and $0.005 per 1k CPU up to a maximum of $25 per month depending on how much load your website uses."

    That's pretty much it. The more you use the more you pay. Right now, Morty is only offered as a prepaid plan. You add money to the account up front, and the cost of the services are deducted each month as you use it. The first 10k CPU and 100GB RAM each day are included in the base rate of $1/month, so if you never go above 10k CPU or 100GB RAM on any day during a month, your account will only cost $1 for that month. The overage rates above apply for usage in excess of those limits.

    If the account runs out of money, it moves itself back to Tommy (and if it's overusing, gets suspended for high load).

    Load is calculated the same way it is in Tommy and Johnny, sampled every 60 seconds and summed up over a 24 hour period. You can view your load here: https://heliohost.org/dashboard/load/

  5. I see an internal server error for the scripts on your account, not a 503. The test.py works fine. What are you trying to execute?

    Also, keep in mind for Python that the script must have a shebang line, must use unix line endings and, at minimum, must be coded to emit a content type header in order for it to not throw an error. The errors in your logs are "End of output before headers", which suggests the code is either not coded to send headers, or is crashing before it can do so (though there's often other errors shown if that's the case...). Your files are also missing their shebang lines.

  6. Invision manages its own robots.txt, and there doesn't appear to be an option to exclude a single forum without using the custom config option instead of the IPB recommended. I'd do that, but I'm not sure if custom rules replace the default ones or just be added to them. That said, Google can't index email support anyway because it cannot sign in, and just gets an access denied error if it tries to go in there. Preventing search indexing of that forum is the main reason it's hidden.

    Also, even if I set up custom robots rules in IPB, I'm not even sure the robots.txt even does anything in our environment since IPB puts it in /index/ instead of in the domain root: https://helionet.org/index/robots.txt

    • Like 1
  7. Your load is due to using Wordpress. This is probably the number one cause of load suspensions on the free plans here at HelioHost.  Please see this: https://wiki.helionet.org/misc/wordpress

    If you're unable to fix the load (or don't want to worry about fixing the load), you can also switch to Morty instead to prevent your site from being suspended. Morty is not free, but has no load restrictions or activity requirements. It charges you a monthly fee starting at $1, and the price just increases when resources are overused instead of suspending you. If you want to do that, simply log into https://heliohost.org/dashboard/ and select the option to move your account.

    This was the load chart for your account. The period of no load between 2000 and 0900 is the time you were suspended. You can view your own load here: https://heliohost.org/dashboard/load/

    image.png.4c58d6c068425605c3ee718e09c003b2.png

  8. Yeah we have to turn off the automatic renewals for the domain on our side. Just removing the cert won't work because it will simply try to reissue it.

    I've turned off the automatic certificate renewals for the domain activescaffold.eu, and installed a webmail-only certificate for you. When the 90 days is up, simply reissue the cert manually and select only the webmail option.

  9. The DNS is set up on our end, but your domain is configured to use Cloudflare, so our DNS doesn't do anything anyway. If you intended to use our DNS, you need to remove CF and change the name servers to ns1.helioghost.org and ns2.heliohost.org.

    nslookup muj.my ns1.heliohost.org
    Server:  UnKnown
    Address:  65.19.143.3
    
    Name:    muj.my
    Addresses:  2001:470:1:1ee::1002
              65.19.154.90
    nslookup muj.my ns2.heliohost.org
    Server:  UnKnown
    Address:  64.62.211.133
    
    Name:    muj.my
    Addresses:  2001:470:1:1ee::1002
              65.19.154.90

     

  10. In Plesk the email addresses are linked to the domain they're created under, so you cannot create email addresses @mail.gebu8f.com if you only have gebu8f.com set up. Also, the subdomains mail and webmail are reserved by the system, so they cannot be set up as subdomains without breaking things.

    We could set up a different sub for email though. Do you want me to set up something like email.gebu8f.com instead? 

  11. @MoneyBroz He specifically said he hosts the domain elsewhere intentionally. He's only using us for email and a single subdomain called demo.

    This error is because Plesk doesn't support hosting a domain only for its webmail. The entire domain has to be hosted here for the auto-SSL to work properly. It will sort of work as you've seen, but it is going to constantly produce errors. The only way to stop these error emails is to disable the automatic SSL certificate installation entirely.

    There is no option to tell Plesk "issue only a webmail cert" since its not a supported scenario. Do you want me to turn this function off for your domain?

     

  12. Please try this guide to correct the issue: https://wiki.helionet.org/common-errors/phpmyadmin-mariadb-access-denied I assume the database in question is demon666_world since its empty, so I'd suggest resetting the password for the associated user account demon666_phpuser.

    A lot of these broke last week. This problem occurred as a result of the incident covered in this news article (specifically your problem is Known Issue #2): 

     

×
×
  • Create New...