wolstech

It is, I'm just not at a computer with an ssh client at the moment to restore it...I should be able to restore in a little while once I get to my pc.

FileZilla has a recursive permissions set option if you use that client. Right click the *folder containing the files*, then pick file permissions. Specify the 644, and pick "apply to files only" to recursively change the files without affecting the directories. Then repeat for directories only to make those 755. You can also use unencrypted ftp to upload the whole structure and it'd be 644 by default and not need fixing. The 664 issue is specific to SFTP.

Did you change the permissions on the folder where the logs are being stored? Tomcat doesn't run as your user, so it doesn't have permission to save stuff in your home folder unless you grant "other users" write permissions. Try making that log folder's permissions 756 instead of 750.

Any PHP file will produce that error if its permissions are not 644, even if the file is completely empty. All PHP files inside public_html need to be 644. Folders inside of public_html should be 755. The public_html folder itself should be left at its default (750). When you upload files over SFTP, they default to 664, note the center 6. Change that to 644 and it'll work.

Did you change the file permissions to 644?

Yeah, bots need to be careful on our service. While they're not outright banned, certain types are. https://wiki.helionet.org/Terms Botnets (both parts, the control server and the bot) fall under #1. This is actually one of the big reasons why ioncube is not supported anymore. Most botnet sellers use it to protect their scripts, so by not supporting it, most botnets can't even run here (the other reason for ioncube's ban was frequent and repeated piracy of WHMCS, a paid data management system). Facebook/instagram likebots, and similar scripts have their own bullet (#5), which basically bans any social media script that's abusive to or against the TOS of the service they automate. Facebook and Instagram both prohibit buying/selling likes or follows or using bots to unfairly obtain them, so those bots are all prohibited. We do allow chat bots though. These are typically just for entertainment or to distribute canned responses to people seeking information, so they're generally not harmful and are rarely if ever banned by the service on which they operate. Some services like Discord are intentionally designed for bot support.

Postgres may just be broken then. Let's have Krydos take a look. Also what does this bot do anyway?

Unblocked. It was for failed SFTP logins, so you probably need to check the password in your FTP client.

Gone.

Looking at the error log shows Postgres errors. Did you change php versions by chance? The errors in question are undefined function errors for the pg_connect() function, which means the Postgres module isn’t loaded in php for some reason.

It's caused by cloudflare. CF breaks a significant number of features on our service because it replaces our dns servers, and our systems can only update our own dns servers when you do things like add domains. You need to either remove cloudflare, or manually add a CNAME record to the dns zone on cloudflare's site. Name it sie-cuh, point it to armsis.tk

Do you mean you can't add the domain, or the option is missing? If the option is missing, it's because it's called Aliases now.

CPU and RAM limits are not increasable.

It's not that we won't help, we just have no idea since we run Apache and have never used nginx...

Yeah, they can end up that way on tommy. It's to do with going inactive and renewing yourself.

FTP and cloudflare are not compatible with each other. Remove cloudflare and ftp through your domain name will work. Alternately, use Johnny.heliohost.org as the host name.

That account cannot be restored because it was deleted for disk space. A Tommy invitation has been sent to the address on file so you can create a new account.

Lets see what Krydos says about this.

Rename your .htaccess file to something else so its ignored and try again.

Sent.

That RDA page is actually my account We changed the shared IP on Johnny during the recent rebuild, and the old Johnny shared IP became a dedicated IP on my account. Use johnny.heliohost.org as the host name or change the A record for ftp.van51.ga to 65.19.141.67 and it will work.

All of the email on our servers will appear to originate from the shared IP (which resolves to <servername>.heliohost.org) unless you have a dedicated IP. The antiabuse headers cannot be removed to my knowledge. Also, please be advised that mail from our shared IPs is not accepted by Microsoft or Yahoo due to a history of abuse. A dedicated IP is required to send to these addresses. AOL will accept our mail, but their spam filters are report happy, so make sure your mail doesn't look like spam or you'll get suspended for spam. Gmail will generally accept the mail but can sometimes require a "Not spam" the first time you receive one to get them to go to the inbox.

It has to be manually requested for every domain you need it on. It doesn't work because you didn't request it for that domain (we install it on the main domain by default). Krydos can set this up for you.

Do you have the transaction ID from last week?

There is an ongoing issue the past few days, where renewals on tommy accounts are not unsuspending the website. Our other root admin Krydos is going to look at your account as an example so we can identify and correct this issue. The issue seems to affect most users on tommy who've renewed in the past few days.