wolstech

Tommy2 has been retired and is no longer available. Your account was moved to the new Tommy on September 25, and should be accessible at tommy.heliohost.org instead. Several emails as well as news announcements were made regarding these moves. Note that any data added to tommy2 after September 25 was not migrated as it is a one time migration, and it is expected that you read the relevant announcements and no longer use the old server after the move is completed. Postgres remote access also does not migrate between servers. Since the information for a Postgres remote access request is already included in the post, I'll simply escalate this for you to have it set back up.

Krydos may be able to get it for you but since the server it was on has already been retired there are no guarantees that this data is recoverable. Escalating.

I believe FTP will change alongside Plesk if you reset it through our website (https://heliohost.org/reset/). If you do it through Plesk, Plesk and FTP change separately. Is this not working for you on the new server? The forum password is not synchronized to anything by design and must be changed through the forum.

The database orz_orz exists in your account on tommy and was transferred on 2024-09-25 20:56:23. I'm not sure how this database is used, but please be sure you're watching for email updates regarding accounts being moved. When you receive such an email, if you are using things such as remote database connections or external DNS, it is your responsibility to update DNS entries and IP addresses to reflect the new information provided so things are directed to the correct server.

I'll turn the mail service back on and we'll see how it goes. If it happens again, you're going to need to find another solution. Mail service has been restored for your account.

Data on tommy2 does not sync to tommy continuously. It was a one-time move, and should've moved when the account did. Is there something specific that didn't transfer?

In Plesk, the "subscription" (your allocation of resources) is named after your main domain. All domains a user has share the same subscription in our system. As a result, any of those domains could be sending the messages and they will still show as your main domain since the mail is allocated to the subscription named after your main domain. I'm looking at the mail queue, and you're receiving a ton of spam to mail@hcdirven, which is then forwarding and making it look like you're sending spam. Mail forwarding is a surefire way to get blocked for sending too many emails. Catch-all forward is even worse because literally every email to your domain forwards even if they don't know the mailbox address. I'd be willing to bet those 9 mailboxes forwarded to a dummy gmail account aren't helping things here either. All of these forwarders need to go. Do you want me to remove all of your mail forwarders and reactivate your mail service (mail will deliver to the mailbox on Plesk, be aware you may run out of disk space if you're receiving tons of mail)? Or would you prefer to disable inbound mail so all mail sent to your domains rejects instead (it kind of looks like the forwarders were meant to do that anyway...)?

Limit of zero on your subscription means that you’ve lost your right to send email because you sent too many. If it says you tried to send 3000+ emails, that’s why. Something on your account is attempting to spew email. Common causes are a script like a contact form being abused by bots, an email address with a forwarder that’s receiving tons of email (forwarded mail counts as sent mail), or a mailbox with a compromised password. I can try to research it a bit more when I’m at a computer later.

I'll have Krydos check your account since accounts moved early in the recent migration were affected by a bug that specifically broke SFTP.

Added. They can take 2 hours to work. In the future, please post these requests over in Customer Service, the Contact Helionet forum is meant for issues with your forum account, not for hosting support.

Whatever you're running was using too much memory. Please reduce your resource usage. If this happens again, you'll be asked to provide more information on how you will stop causing so much load. Unsuspended. It may take a few minutes to start working.

Localhost is best practice for anything running on the server accessing the database. It always works and requires no special permissions. Using tommy.heliohost.org as the SQL hostname for code that's running on Tommy itself is not something we'd generally support (we just say use localhost). If you really want to do that for some reason, you might be able to get that working by adding Tommy's IP to the remote access IP list (or setting it to any host).

We've had issues with those in the past...the main issue I recall is that the CF origin certs are not publicly trusted. They're basically self-signed certificates. I haven't messed with these in a while though. Can you put the pem and the key (if its separate) in your home folder (outside of your web root so it's not public!) so I can take a look when I get minute? We usually just tell people to generate an LE cert with the proxy turned off instead, then turn it on. Non-strict SSL ("SSL Full") is the supported and recommended setting on CF for our service. It should work with an LE certificate installed on our end. "SSL Full (Strict)" might work, but tends to be incompatible because it blocks the connection when the certificate is invalid. Plesk, Lets Encrypt, and our custom logic all expect to be able to call your website via its domain and still reach it in these scenarios. It will keep LE's certificates from renewing (especially if the current one is expired), and can result in your domain being disabled for not being hosted here if it lasts long enough... "Flexible SSL" should be avoided because it is insecure.

FTP wasn't set up on Tommy to support connections via IPv6. The suggestion to use the IP was to force an IPv4 connection, which was known to work, instead of letting your OS decide (based on your pictures it was picking v6). The issue with FTP over IPv6 was fixed earlier today, which is why your original settings now work. please let us know if you need anything else.

Domain added. It can take up to 2 hours to start working.

For the database issues, it sounds like you’re logging into the old server. The domain for the server changed when your account moved, you need to remove the 2 from the URL. It’s now just tommy.heliohost.org. Do not use tommy2.heliohost.org for anything (database, Plesk, etc.) or you will either lose data or see stale data. For Plesk, you should be logging in at https://heliohost.org/login/ anyway. Logging in that way will always get you to the right server even if your account exists on two different ones due to a move and avoid the stale data issue. Both old and new servers use Apache behind nginx. If you want, you can turn Apache off in Plesk and use pure nginx.

Account casjay has been moved to Tommy, upgraded to 6000MB since chmweb had it. The domains from chmweb have been merged into casjay, and the account chmweb has been removed. The domains should work within the next 2 hours. When the move and merge finishes, you should get an email explaining how to configure DNS for the csj.lol domain if you're still using it (the casjay domain will just work on its own since its a free subdomain). Please let us know if you need anything else or if something doesn't work right for you.

You can't install it yourself. The other root admin Krydos has to do this for you.

Ok. You'll likely receive an email about casjay moving to Tommy in a little while. Once casjay moves to Tommy, I'll merge chmweb's domain into it then get rid of chmweb. The result should be casjay on Tommy with both domains hosted on casjay.

Resent.

Do you want this as a subdomain of the domain you already have (a07956.a0795683865.helioho.st), or do you want this to stand alone as a07956.helioho.st?

Should be fixed for you. Give it a little while to propagate and for SSL to set up and you should be good.

It's because your domains are redirecting to use www subdomains. Accounts lose their www subdomain when they get moved due to a known issue, so your domains are redirecting to a nonexistent subdomain and showing errors. I'll fix it shortly for you.

Krydos can cancel this for you.

Can you try entering 65.19.154.90 as the host name instead of tommy.heliohost.org? That will force ipv4. If that doesn't work, can you try another device, and another network connection, such as a cell phone hotspot? Beyond that, I'm not sure what else could be causing this. If the above, don't help, let me know and we can see if Krydos has any other ideas...