wolstech

Email received here: https://helionet.org/index/topic/63163-hh336493-cance-vps67/?do=getNewComment

It’s already set to be invisible to guests…only logged in users can see that forum.

Your account jenfull3 was already unsuspended. The website on that account gebu8f.com is working for me. If you're still seeing a suspended page, please clear your cache.

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/

Krydos can do this for you.

If you want to use CF, then you need to create A and AAAA records pointed to the server IPs in cloudflare. The IPs for your account can be seen in Plesk or are also shown in the output of the testing I did above.

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.

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

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?

Unsuspended.

Related link: https://helionet.org/index/topic/63113-solved-access-to-account/

It’s possible to do it when you issue the manually. The issue is that the automatic renewal tool doesn’t let you exclude the domain itself. You can issue a certificate manually every 90 days with just the webmail selected and that will be just fine.

@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?

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):

Node only works if you proxy it through Apache using Passenger, so it will always be on 80 or 443. You won't be able to access port 3000 externally. This tutorial app uses passenger to run Node: https://wiki.helionet.org/tutorials/node.js We don't allow custom inbound ports. This behavior is by design and cannot be changed.

Added. It can take up to 2 hours to function. Please make sure DNS is configured to point to our name servers or to the IP addresses shown in Plesk.

Your account has been reset without a backup as requested. You'll receive an email in the next few minutes with a link to create a new account.

You just need prize.radio added to your account as an alias... Domain added. Make sure the IP points to the IP shown in Plesk, then give it 2 hours and it should show the same content as award-radio.helioho.st.

Krydos will need to look at it. I’m not sure why this function wouldn’t work… it looks like mysqldump failed to run for some reason?

Do you want me to delete the files from nodejs on your account to free up space? I noticed its disabled, and there's 421MB just in node packages wasting space.

Krydos will likely need to check the firewall to resolve this as DmC described. Escalating.

Send me a PM and I’ll pass it along to him in a staff channel.

The issues you described are known side effects of the repair and are things you have to fix yourself. Try the guides linked in this news post.

The Tommy server is currently undergoing maintenance due to an issue encountered late last night. Your account will finish creating once the server is working again. We expect the maintenance to be completed and your account to create within the next hour or so.

The website login and database server are working again. Apache isn't working properly yet though. Still showing a config error in the backend of Plesk, and because of the issues the scheduled 2 hour restarts (and all other maintenance functions like account creates and inactivity suspensions) are stopped, so changes are not going into effect.