wolstech

Unblocked. Same as before. Please remove any password protected folders you have.

Since we're able to confirm your identity based on your email address and post IP address matching those on the account in question, yes we can remove your 2FA for you. Two factor authentication has been removed from your account.

That account is not suspended for inactivity. It’s banned because it got hacked and used for illegal activity. An invite for a new account will be sent to you shortly.

Unblocked. It was for failed web page logins, which usually indicates a problem with a password protected directory.

You're actually using it all: 0M ./cgi-bin 0M ./.well-known 376M ./rapidenglish.me 206M ./lessons 243M ./fandco.io 0M ./legacy 0M ./floydandco.co 0M ./floydandassociates.net 0M ./floydandassociates.co 823M . 125M (mysql and files outside of public_html)Your sites need to be cleaned up or you need to purchase more space. As is typical, we highly recommend not using WordPress. It's notoriously bloated, buggy, and insecure. Most of your space is being eaten up by WP installations that need some heavy cleaning, or preferably rebuilt in some other program.

This is not supported. You would need your own VPS with root access in order to modify Apache in this manner. https://heliohost.org/vps/

Unblocked. Please check your mail client settings so this doesn't happen again.

Krydos would be the one to figure this out. Sometimes the system provides a filename but it didn’t this time. It may not even be the proxy that did it considering you have other things on your account too.

SSL will take up to 48 hours to start working from the time I ran it...so that's expected.

His domain is working properly, but his SSL certificate is no good. I manually ran AutoSSL for him to fix that. He needs to clear his cache to remove the queued page.

The bars represent your average load over the time period listed. A brief spike is all that's needed to get suspended, especially if the server is busy. The higher those bars are, the easier it is to get suspended, but a low number doesn't mean it's impossible to get suspended. A proxy that's not being used causes no load. Same goes for any other program. The moment you use it, it goes from producing 0 load to producing a substantial amount of load, and if that load happens to be more than everyone else and/or slows the server down, you're at the top of the list for suspension. Since the bars on that page are an average, they're more representative of your continuous load, and won't properly reflect load spikes. As a result, excessive load from proxies, WP sites that suddenly get hit by bots, sites that ended up linked on reddit, etc. won't show anywhere until you're already suspended.

As soon as I saw him say proxy I asked myself how long it was going to take for that to happen...turns out it already did. Actually getting the proxy to work will make that issue worse too. Proxies and video converters are top "don't bother" things here. They're all way too heavy for our servers. Wordpress is the runner up in this category.

The only other way to avoid the monthly renewal is donation. Unfortunately, just having the account present on the server increases load from things memory use for DNS entries and CPU cycles used by Apache restarting and loading an account's vhosts, even if it has zero actual usage, so we have to clean up unused accounts regularly to keep the server from falling over. A large number of accounts created on our service are never used beyond perhaps an initial login. In addition, many of our users use their account non-conventionally (e.g. some use their account for specific features only, use as a database server is a common example). We usually ask for recurring donations to do so ($1 per month), but if you really don't want to, we'd be willing to accept a single larger donation for multiple months up front. Donating will also make you eligible to be moved to Tommy, which has significantly better performance than Ricky. If you decide to donate, please let us know the transaction information so we can set up your inactivity immunity.

We do heavily discourage its use. It's junk software with tons of security holes, performance issues, and plenty of infected extensions available for it...the issue is so bad that literally every other CMS out there is better. We usually recommend Joomla as a result. It's probably the second most used, and has tons of content and extensions available. Yes it can be hacked or get malware too, but it's nowhere near as prevalent as WP's issues. WordPress is our leading cause of hacked accounts and malware, as well as unintentional spam and phishing bans, hence our position on it. Some hosts have no longer allow it for these reasons alone, or have dedicated WP Hosting offerings and servers to help mitigate the risks. That said, it's not banned and if you're willing to deal with the possible issues and consequences that can arise from its use, more power to you. We aren't going to suspend you for installing it, but if it acts up and slows down our servers, or it gets hacked and used for illegal activity, don't expect your account to stay online.

Whatever internet connection you use normally is either blocked by us, or doesn't allow traffic on port 2083. I would need the public IP of the connection that doesn't work in order to check if it's on our end. Blocking port 2083 is quite common on school and work networks, and there's not really a good solution for it other than either convincing them to unblock it, or using a VPN.

Try a different internet connection like a cell phone or public WiFi. A blank page or timeout error usually indicates an IP ban, though I don’t see you in the block list...

You can't, that file is way too big to be uploaded through the web interface. We've increased the limits upon request before, but 48mb is quite ridiculous for a form upload. I'll move this to see if Krydos can do it, but I doubt we'd make the limit that large for a variety of reasons. My suggestion is to upload it via ftp and install it manually.

I just manually scheduled an Apache restart on Tommy, it should restart shortly. (Tommy Apache doesn't restart on its own at the moment because we disabled that feature due to load). It's been nearly a full day since the last restart, so it was due. The new Tommy account from last nights free registration was also waiting... Once that happens, you should be able to access the domain, and within 24 hours after it starts working, AutoSSL should issue a certificate for it provided you don't have a forced redirect in place. After the cert installs, Apache will need to restart a second time to get it all working.

That meta tag will cause an infinite loop. The PHP method is what I use. It's a nice choice because it lets you still access other files on the server over plain http if necessary without adding a bunch of exceptions for them, but the average joe visiting your site will still be given an https connection.

Cloudflare and AutoSSL cannot coexist on our servers, so you may find yourself manually installing certificates if you use CF. Tommy is fast enough that you really don't need it anyway to be honest. It won't make much of a difference anyway unless you have lots of big pictures or something on them. It won't even help the speed of dynamic pages (php, etc.) because the scripts have to run every time they're visited. CF is more useful for Ricky and Johnny where the servers are painfully slow even for static content. Also, when troubleshooting this sort of thing, it's best to forget about forcing https entirely and just get the site to accept the connection. Rename the htaccess and get everything else working first.

Seems to have resolved itself, now reporting 80% full.

@sohamb03: Doing that will break AutoSSL because it won't be able to renew when the cert expires. It either needs an exception added for .well-known, or he add a redirect in index.php instead of using .htaccess.

Looks like Tommy's /tmp is full...lots of applications throwing No Space Left on Device when trying to save into it at the moment. If anyone has applications that are suddenly throwing unexplained 500 errors, especially during file uploads or database operations, this is the likely cause. The errors will correct once the space has been freed.

Yep. Apache has to restart before SSL will function after the certificate has been installed.

This comes from the linux / Windows divide. In Linux, upper and lowercase are considered different (TableName != tablename != Tablename), whereas in Windows, its practice to ignore case entirely (TableName == Tablename == tablename). Filenames and such are the same way. You built an app for a linux server using the Windows conventions from the sound of it. Tables are actually stored as files, so they follow the file system convention. The columns inside follow suit. See this: https://stackoverflow.com/questions/2009005/are-column-and-table-name-case-sensitive-in-mysql Sadly it's time to edit everything for consistency. I had to do the same with my first ever program as well. Any linux based host you use will have a similar requirement.