wolstech

Considering this domain now points to 000 and they've also already banned him, I'm going to assume it is indeed for phishing.

Yep. Load again...please try to fix it quickly. Things running in a tight or infinite loop are a common source of this, so depending on how your code is written, it's completely possible that caused it. Unsuspended.

The common internet ports are open outbound: 21,25,80,443,8080, as well as cpanel ports (2082 and 2083). Others are by request only with good reason given. We need the port and the IP of the remote server you'll be connecting to. We do not allow custom daemons, so inbound ports cannot be opened.

The account was automatically suspended because we have reason to believe it was intended to be used for phishing or other illegal activity. Can you explain why your domain is extremely close to that of a large bank?

cPanel does not support changing the main domain's document root. It must always point to public_html.

Unsuspended.

It was suspended for having too many SFTP connections open. I've never seen that in my career here. Please try to limit the number of connections you open at once to something reasonable (less than 5 is probably good). Most clients have a setting for number of concurrent connections you can adjust to control this. Unsuspended.

As flaze said, check the trash if you used the file manager. If you used something like ftp though, it's just gone. We don't keep backups of active user accounts, so we have no way to un-delete files.

Max execution time is too low most likely...

Did it sit there for 30 seconds then fail? If so, the execution time is probably too low to run it. Krydos might have some additional ideas about this.

Mine did that on Lily as well...it got to 90% on mine, spit out an error, but was successful after refreshing. I think that one is actually a bug. It's kind of an ironic error because a code of 0 in most PC programs is "success". That error is basically readable as "Error: Success". Check the file dates and times. I believe March 9 is the date my files had after the update. The system works fine.

Unblocked. Failed SFTP logins...make sure you use only your cpanel username and password to log into SFTP. If you create additional FTP accounts, they need to use plain FTP on port 21.

That account is working, but the software installed on it is not. Please clear your cache to get rid of the queued page. The privacy warning is normal since Johnny accounts don't come with SSL certificates (Ricky and Tommy include SSL certificates). You can install a certificate from a source like ZeroSSL (and wait a few hours for it to take effect once you do), or just not use SSL. The 500 error is due to broken software on your end that you'll need to fix or remove. The most common cause of a 500 error is permissions (make sure files are 644, they tend to upload as 664 if you use SFTP), or invalid .htaccess files.

We don't allow users to modify these values themselves. Assuming you're on tommy, I know we don't do more than 128M on the memory limit and 60 for the execution time. If they're lower than this for any given version of php, they can be raised to that level. Max permitted values for Johnny and Ricky may be less. The upload sizes can be increased if need be. Considering you listed these 4 specifically, let me guess, joomla update? If so, that's a known issue with running joomla here. The only server that can update that successfully at the moment is our windows server Lily.

Owncloud definitely runs here (have seen others using it), and Nextcloud should run according on its documentation. Softaculous is very sensitive to server load. I would either try installing again when load is a bit lower, or try installing it manually (since our servers are already configured, you should be able to set PHP version to 7.3 (if it's not already), create a database, upload the files into a folder of your choice and visit it in your browser to start installation).

Our servers do not meet the requirements for that application (specifically, we intentionally disabled ioncube due to a history of it being used to run botnets and pirated software). You'll need to find something else to use or purchase a VPS.

You're missing the point of AutoSSL. You don't need CloudFlare, ZeroSSL, or anything else. You don't need to install any certificates or anything. The server does all of that for you in the background. In fact, your site actually has valid certificates already. As soon as Apache restarts (usually takes up to 2 hours), SSL will work with no further effort needed on your part except possibly clearing your cache

Krydos needs to turn php fileinfo on for you. http://krydos2.heliohost.org/72/phpinfo.php

The site is now showing for me. I just turned the AutoSSL back on since you apparently excluded for it for some reason. Your domain should have working SSL within the next hour or so. Your mistake was turning off AutoSSL to begin with. Even if you use CF, you need to leave AutoSSL enabled if you want to use the "Full SSL" or "Full SSL Strict" options on CloudFlare. Only "Flexible SSL" or "None" will work if you disable AutoSSL. Also, please keep in mind that the certificates will not renew properly if you use CloudFlare, so you'll need to remove CF (or at least put it in developer mode so it doesn't try to cache the response file) every 90 days and manually run AutoSSL to make them renew. Log for the AutoSSL run for “ocbwnl”: Monday, April 6, 2020 12:47:15 PM GMT-0400 (cPanel (powered by Sectigo)) 12:47:15 PM AutoSSL’s configured provider is “cPanel (powered by Sectigo)”. This AutoSSL provider does not poll for certificate availability immediately after a certificate request submission. Instead, it submits certificate requests then periodically polls the cPanel Store for each requested certificate and installs it after a successful retrieval. The system will record all requests, retrievals, and installations for the current AutoSSL run in this log. Analyzing “ocbwnl”’s domains … 12:47:15 PM Analyzing “admin.php.omroepcomeback.ml” … 12:47:15 PM ERROR TLS Status: Defective ERROR Defect: NO_SSL: No SSL certificate is installed. 12:47:15 PM Analyzing “backup.websites.omroepcomeback.ml” … 12:47:15 PM ERROR TLS Status: Defective ERROR Defect: NO_SSL: No SSL certificate is installed. 12:47:15 PM Analyzing “chat.omroepcomeback.ml” … 12:47:15 PM ERROR TLS Status: Defective ERROR Defect: NO_SSL: No SSL certificate is installed. 12:47:15 PM Analyzing “conferenties.omroepcomeback.ml” … 12:47:15 PM ERROR TLS Status: Defective ERROR Defect: NO_SSL: No SSL certificate is installed. 12:47:15 PM Analyzing “drive.omroepcomeback.ml” … 12:47:15 PM ERROR TLS Status: Defective ERROR Defect: NO_SSL: No SSL certificate is installed. 12:47:15 PM Analyzing “omroepcomeback.ml” … 12:47:15 PM ERROR TLS Status: Defective ERROR Defect: NO_SSL: No SSL certificate is installed. 12:47:15 PM Analyzing “privacy.policy.generator.omroepcomeback.ml” … 12:47:15 PM ERROR TLS Status: Defective ERROR Defect: NO_SSL: No SSL certificate is installed. 12:47:15 PM Analyzing “sharenotes.omroepcomeback.ml” … 12:47:15 PM ERROR TLS Status: Defective ERROR Defect: NO_SSL: No SSL certificate is installed. 12:47:15 PM Analyzing “team.omroepcomeback.ml” … 12:47:15 PM ERROR TLS Status: Defective ERROR Defect: NO_SSL: No SSL certificate is installed. 12:47:15 PM Analyzing “video.omroepcomeback.ml” … 12:47:15 PM ERROR TLS Status: Defective ERROR Defect: NO_SSL: No SSL certificate is installed. 12:47:15 PM Analyzing “web.sql.omroepcomeback.ml” … 12:47:15 PM ERROR TLS Status: Defective ERROR Defect: NO_SSL: No SSL certificate is installed. 12:47:15 PM Analyzing “wiki.omroepcomeback.ml” … 12:47:15 PM ERROR TLS Status: Defective ERROR Defect: NO_SSL: No SSL certificate is installed. 12:47:15 PM Attempting to ensure the existence of necessary CAA records … 12:47:16 PM No CAA records were created. 12:47:16 PM Verifying “cPanel (powered by Sectigo)”’s authorization on domains via DNS CAA records … 12:47:17 PM “cPanel (powered by Sectigo)” is authorized to issue certificates for all domains. 12:47:17 PM Performing HTTP DCV (Domain Control Validation) on 28 domains … 12:47:17 PM Local HTTP DCV OK: omroepcomeback.ml Local HTTP DCV OK: www.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: chat.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: mail.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: team.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: wiki.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: drive.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: video.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: cpanel.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: webdisk.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: webmail.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: sharenotes.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: conferenties.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: web.sql.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: www.chat.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: www.team.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: www.wiki.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: admin.php.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: www.drive.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: www.video.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: www.sharenotes.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: backup.websites.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: www.conferenties.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: www.web.sql.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: www.admin.php.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: www.backup.websites.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: privacy.policy.generator.omroepcomeback.ml (via omroepcomeback.ml) Local HTTP DCV OK: www.privacy.policy.generator.omroepcomeback.ml (via omroepcomeback.ml) 12:47:17 PM No local DNS DCV is necessary. 12:47:17 PM Processing “ocbwnl”’s local DCV results … 12:47:17 PM Analyzing “admin.php.omroepcomeback.ml”’s DCV results … 12:47:17 PM AutoSSL will request a new certificate. 12:47:17 PM Analyzing “backup.websites.omroepcomeback.ml”’s DCV results … 12:47:17 PM AutoSSL will request a new certificate. 12:47:17 PM Analyzing “chat.omroepcomeback.ml”’s DCV results … 12:47:17 PM AutoSSL will request a new certificate. 12:47:17 PM Analyzing “conferenties.omroepcomeback.ml”’s DCV results … 12:47:17 PM AutoSSL will request a new certificate. 12:47:17 PM Analyzing “drive.omroepcomeback.ml”’s DCV results … 12:47:17 PM AutoSSL will request a new certificate. 12:47:17 PM Analyzing “omroepcomeback.ml”’s DCV results … 12:47:17 PM AutoSSL will request a new certificate. 12:47:17 PM Analyzing “privacy.policy.generator.omroepcomeback.ml”’s DCV results … 12:47:17 PM AutoSSL will request a new certificate. 12:47:17 PM Analyzing “sharenotes.omroepcomeback.ml”’s DCV results … 12:47:17 PM AutoSSL will request a new certificate. 12:47:17 PM Analyzing “team.omroepcomeback.ml”’s DCV results … 12:47:17 PM AutoSSL will request a new certificate. 12:47:17 PM Analyzing “video.omroepcomeback.ml”’s DCV results … 12:47:17 PM AutoSSL will request a new certificate. 12:47:17 PM Analyzing “web.sql.omroepcomeback.ml”’s DCV results … 12:47:17 PM AutoSSL will request a new certificate. 12:47:17 PM Analyzing “wiki.omroepcomeback.ml”’s DCV results … 12:47:17 PM AutoSSL will request a new certificate. 12:47:17 PM The system will attempt to renew the SSL certificates for the websites (admin.php.omroepcomeback.ml: admin.php.omroepcomeback.ml www.admin.php.omroepcomeback.ml), (backup.websites.omroepcomeback.ml: backup.websites.omroepcomeback.ml www.backup.websites.omroepcomeback.ml), (chat.omroepcomeback.ml: chat.omroepcomeback.ml www.chat.omroepcomeback.ml), (conferenties.omroepcomeback.ml: conferenties.omroepcomeback.ml www.conferenties.omroepcomeback.ml), (drive.omroepcomeback.ml: drive.omroepcomeback.ml www.drive.omroepcomeback.ml), (omroepcomeback.ml: omroepcomeback.ml www.omroepcomeback.ml mail.omroepcomeback.ml webmail.omroepcomeback.ml cpanel.omroepcomeback.ml webdisk.omroepcomeback.ml), (privacy.policy.generator.omroepcomeback.ml: privacy.policy.generator.omroepcomeback.ml www.privacy.policy.generator.omroepcomeback.ml), (sharenotes.omroepcomeback.ml: sharenotes.omroepcomeback.ml www.sharenotes.omroepcomeback.ml), (team.omroepcomeback.ml: team.omroepcomeback.ml www.team.omroepcomeback.ml), (video.omroepcomeback.ml: video.omroepcomeback.ml www.video.omroepcomeback.ml), (web.sql.omroepcomeback.ml: web.sql.omroepcomeback.ml www.web.sql.omroepcomeback.ml), and (wiki.omroepcomeback.ml: wiki.omroepcomeback.ml www.wiki.omroepcomeback.ml). 12:47:19 PM The cPanel Store received “chat.omroepcomeback.ml”’s certificate order. (Order Item ID: 882886053) The system will periodically poll the cPanel Store for the issued certificate and then install it after a successful retrieval. 12:47:20 PM The cPanel Store received “omroepcomeback.ml”’s certificate order. (Order Item ID: 882886065) The system will periodically poll the cPanel Store for the issued certificate and then install it after a successful retrieval. 12:47:22 PM The cPanel Store received “drive.omroepcomeback.ml”’s certificate order. (Order Item ID: 882886081) The system will periodically poll the cPanel Store for the issued certificate and then install it after a successful retrieval. 12:47:23 PM The cPanel Store received “video.omroepcomeback.ml”’s certificate order. (Order Item ID: 882886097) The system will periodically poll the cPanel Store for the issued certificate and then install it after a successful retrieval. 12:47:25 PM The cPanel Store received “backup.websites.omroepcomeback.ml”’s certificate order. (Order Item ID: 882886109) The system will periodically poll the cPanel Store for the issued certificate and then install it after a successful retrieval. 12:47:26 PM The cPanel Store received “web.sql.omroepcomeback.ml”’s certificate order. (Order Item ID: 882886125) The system will periodically poll the cPanel Store for the issued certificate and then install it after a successful retrieval. 12:47:27 PM The cPanel Store received “admin.php.omroepcomeback.ml”’s certificate order. (Order Item ID: 882886133) The system will periodically poll the cPanel Store for the issued certificate and then install it after a successful retrieval. 12:47:28 PM The cPanel Store received “wiki.omroepcomeback.ml”’s certificate order. (Order Item ID: 882886149) The system will periodically poll the cPanel Store for the issued certificate and then install it after a successful retrieval. 12:47:29 PM The cPanel Store received “privacy.policy.generator.omroepcomeback.ml”’s certificate order. (Order Item ID: 882886161) The system will periodically poll the cPanel Store for the issued certificate and then install it after a successful retrieval. 12:47:31 PM The cPanel Store received “team.omroepcomeback.ml”’s certificate order. (Order Item ID: 882886181) The system will periodically poll the cPanel Store for the issued certificate and then install it after a successful retrieval. 12:47:32 PM The cPanel Store received “sharenotes.omroepcomeback.ml”’s certificate order. (Order Item ID: 882886185) The system will periodically poll the cPanel Store for the issued certificate and then install it after a successful retrieval. 12:47:33 PM The cPanel Store received “conferenties.omroepcomeback.ml”’s certificate order. (Order Item ID: 882886201) The system will periodically poll the cPanel Store for the issued certificate and then install it after a successful retrieval. The system has completed “ocbwnl”’s AutoSSL check.

What version of PHP are you using?

The DNS change hasn't propagated and is still resolving to CF. Lets give it some time to see if it updates. Your account looks good on our end, but the AutoSSL won't get a certificate until the domain resolves properly, and we can't do anything else until the domain works anyway.

This looks like DNS propagation failure, probably on Freenom's part (they're notorious for system issues). I can't even resolve your domain from my PC (i get an NXDOMAIN on a general query through Comcast DNS, and "No response from server" if I query HelioHost directly). Most major DNS servers are returning either NXDOMAIN or CloudFlare as your name servers. This tool shows your DNS is correct: https://bybyron.net/php/tools/dns_records.php?domain=tarkeshwarpatil.tk&rec=ALL So it's not on our end. Until the DNS propagates (if it ever does...we've been having lots of weird issues with DNS not propagating in the past few weeks), most things won't even know that site exists.

First things first...he's still in violation of the TOS for two accounts. He needs to also delete his Johnny account nteeuwen before we go further. An individual person can only have one account. Second, remove CF and change your name servers to ours. We cannot provide support for any account using CloudFlare because it hides the DNS settings we need to see, and it also has known incompatibilities with our service, SSL being one of them. It can be made to work, but it requires jumping through hoops, and the first step is getting the account to work without it.

Unblocked. It can take up to 10 minutes to be effective.

Sent.