Krydos

They must not have liked the two news articles that have been written about us recently. The next time someone writes another news article we'll try again I suppose.

Done. You should now be able to log in and your website should be working again.

Once you've added the domain to cpanel you're welcome to change your nameservers to whatever else you'd like though. This is the way we recommend people set up cloudflare.

Your account was archived because you haven't logged in for quite a while. We have a limited amount of space on our servers, and occasionally we have to remove the unused accounts to make space for new users. To prevent your account from becoming archived again please remember to log in at https://www.heliohost.org/login/ at least once every 30 days. Unarchiving...

Thanks for trying!

The directory would need to be 777. Directories have to be executable. 755 is a standard directory, and public_html is special and gets 750. /home/cridus10/ is also special and actually has 711 permissions. All of the directory permissions I've listed are executable though.

It looks like there are some plugins that would maybe do that https://plugins.roundcube.net/search/?tags=calendar Keep in mind you won't be able to install a plugins on the cpanel version of roundcube, but you can install roundcube into your public_html directory and then install plugins there.

Cpu usage = Unlimited on all three servers. If your account starts to cause significant performance degradation or downtime for the other accounts due to overusing the cpu it will be suspended to keep the other accounts online. Memory usage = Unlimited on all three servers. If your account starts to cause significant performance degradation or downtime for the other accounts due to overusing memory it will be suspended to keep the other accounts online. Bandwidth = Unlimited on all three servers. We have multiple accounts that regularly transfer around 100 GB per week each. You probably don't need to worry about bandwidth. Download/Upload speed = I tested it on all three servers, and the lowest I got was 9 MB/s, the highest I got was 31.6 MB/s. It will depend a lot on server load and how much bandwidth other accounts are using. The answer to this question is always Tommy. However free daily signups on Tommy generally fill in 5-10 seconds. So your best bet if you want a Tommy account is to make a donation of $1.00 USD or more to get an invite. Ricky is next best, and Johnny is out worst, slowest, and lowest uptime server. The only reason I can think of where you wouldn't pick Tommy is if you wanted to use Django or Flask with python 2.7 instead of python 3.6. There are very few people which that applies to though.

Create the log file manually, and then make sure the file is writable by other. 777 is a little bit of overkill, but it'll get the job done. If you want the application to be able to create the file itself you'll need to set the permissions on the directory the log is going to be written in to 777 or so. Obviously you can't change the permissions on /home/cridus10/, but you could create a directory like /home/cridus10/javalogs/ and give tomcat the permissions to write to that directory.

Opened.

Nope, I just deleted it as soon as I found the problem, and suspended your account that caused the issue. Off the top of my head I sort of recall it being roughly 50 files totaling a little over a gigabyte of space.

To be completely honest, there are literally gigabytes of logs and they are all a jumble of like 40 different deployed .wars and most of the lines in the log files don't even state which .war they originated from, etc. etc. You're much better off writing your own log files to your own home directory or testing this on your home pc because there's not a lot I can do for you even if I wanted to. That said I found one severe error that MAY belong to your application. I don't even know for sure. I PM'd it to you even though there is a chance it may be private information from someone else's .war. In the future if you can be a little more specific or give me some string to search for maybe.

Done. You should now be able to log in and your website should start working within 2 hours.

Your account was archived because you haven't logged in for quite a while. We have a limited amount of space on our servers, and occasionally we have to remove the unused accounts to make space for new users. To prevent your account from becoming archived again please remember to log in at https://www.heliohost.org/login/ at least once every 30 days. Unarchiving...

Is it working now?

Done. You should now be able to log in and your website should start working within 2 hours.

Your account was archived because you haven't logged in for quite a while. We have a limited amount of space on our servers, and occasionally we have to remove the unused accounts to make space for new users. To prevent your account from becoming archived again please remember to log in at https://www.heliohost.org/login/ at least once every 30 days. Unarchiving...

I'm not sure what you mean by java8. Tommy runs Tomcat 9.0 on Java 1.8. Johnny runs Tomcat 8.5 on Java 1.8. Eventually Johnny will be upgraded to Tomcat 9.0 as well though. EDIT: It looks like you probably mean Java 1.8 not Tomcat 8.0 like I was thinking https://www.quora.com/Do-Java-1-8-and-Java-8-refer-to-the-same-thing

Unblocked. It was because you tried to log in to cpanel with the wrong username and/or password too many times. If you login at https://www.heliohost.org/login/ this won't happen again.

Chart has been installed on Tommy's perl.

It looks like it's working again now. Having one nameserver down generally isn't going to affect the uptime of anyone's website, as long as at least one nameserver is up. The reason for two or more nameservers is to have 100% uptime of a least one of them being up. Having a nameserver down just means that the working nameserver is going to have to work twice as hard to answer all the requests. One of the nameservers going down won't make your site redirect to an old server, unless there is some caching issue going on and you just recently changed to our nameservers. The old wrong cached value should expire on it's own within a day or so. Usually less.

Closing due to inactivity.

Unarchived. Your username had to be changed to nazabal2.

Do you mean Tk::Chart (1.22)

Deployed.