Krydos

I don't understand how the previous servlet can be still in there considering my deployment script deletes the .war file from webapps and then waits for Tomcat to fully unload the servlet. Then the script shuts down Tomcat and waits until all of the Tomcat processes are completely unloaded from memory. Then it restarts Tomcat and deploys the new .war file. Anyways, I manually deleted your .war from webapps, and waited until Tomcat unloaded and deleted the directory. Then I manually shutdown tomcat completely, and waited for it to fully exit from memory. Then I deleted your directory in the work directory. Let me know once you're ready to deploy the new version again. You could also consider changing the name of the .war file in case it's your browser that is caching the old pages.

Yes, the problem still exists on Johnny. We recommend Tommy if you want a bug-free high-uptime server.

Ricky is down for repairs and signups are currently closed. You can choose Johnny or Tommy right now. We plan on buying some new hardware for Ricky and installing it in August at the latest. We'll get him back online after that.

Check out https://github.com/goldfire/howler.js/issues/513 You're not the only one having this issue with howler.js.

There you go: https://albertnis.com/test.aspx

Deployed. http://citisnet.heliohost.org/citisnetsql3/

Are you using MyISAM tables (which is the default, but doesn't support foreign keys) or InnoDB tables?

Fair enough. Your account is now located on Tommy. The server transfer scripts are pretty new so let us know if you encounter any bugs. Thanks again for your nice looking images.

That account is already queued for deletion. All of the account creations and account deletions are load balanced. The lower the load the quicker they happen. The higher the load the slower they happen. Johnny has had exceptionally high load today so he's a bit backed up and taking a little longer than usual to delete accounts. Once he gets around to deleting your old account you would have been able to add that domain to your new account. I have manually removed the domain friendinger.ml from your Johnny account. Can you add it to your new account now?

A new invite has been sent to you. Let us know if you have any other issues. The domain you picked was already in use by another account so it can't be removed for you to use. Generally the javascript will let you know if a domain is already in use, but it's possible with Johnny's current high load that it timed out and let you use it anyways.

For anyone who searches and finds this thread the issue is the server that was chosen. Johnny is our experimental server which means that it can be rather unstable sometimes. The past 12 hours have had especially high load which resulted in slow loading times. For users who want faster load times and better uptime we suggest you pick a production server instead. We highly recommend Tommy.

Yep, your .htaccess file is in the right spot, and looks good now. The next problem I found is in your dispatch.wsgi file. It doesn't have the correct path. It should look like this sys.path.append("/home/saikosns/public_html/ComicPub") Since your running your django app in a subdirectory you need to specify that subdirectory in the path in order for it to find its modules.

Enabled.

The deployed version matches the version sitting in your home directory. Maybe try uploading it again?

It's possible you have a .htaccess file causing your browser to want to download the files instead of display them. You can check if .htaccess is causing this by renaming it to .htaccess-old or something.

Deployed. http://citisnet.heliohost.org/citisnetsql3/ In order to deploy a .war for someone you currently need root access to the server. That's true on Johnny. If it's a new .war or the filename has changed it can take several hours to deploy, but if it's the same filename but an updated file it takes only a few minutes. Tommy takes a few minutes for the same filename or different. Not yet. We are planning on allowing self-deployed .war files in the future though. It's pretty high priority on our future features development schedule. We understand it's slow and frustrating to wait for an admin to deploy the file for you. That should be fixed soon.

As it explains on the cron job page, you are only allowed to run two cron jobs per day. That means you can run one cron job every 12 hours, or two cron jobs every 24 hours. For instance on June 23rd you ran more than two cron jobs so all of your cron jobs were deleted. Internal cron jobs are limited to two per day, but external cron jobs can be run as often as every five minutes. Let us know if you need help setting up an external cronjob.

You can delete your account yourself with http://www.heliohost.org/classic/support/scripts/delete and no we don't delete accounts without proof of ownership because otherwise someone could just request any random account to be deleted.

Your IP was blocked for guessing the wrong password too many times while trying to log in to cpanel. I have removed the block for you. Are you able to log in now?

Remote postgresql access is not enabled by default. You can request remote access by posting the postgresql username, database, and IP(s).

Set your DNS to ns1.heliohost.org and ns2.heliohost.org

Apache restarts itself quite frequently. You don't need to worry about that part.

Thanks! Those look great.

It is a little confusing. The .htaccess should go in /home/saikosns/public_html/ComicPub/.htaccess and it should look like this: RewriteEngine On RewriteBase / RewriteRule ^(media/.*)$ - [L] RewriteRule ^(admin_media/.*)$ - [L] RewriteRule ^(ComicPub/dispatch\.wsgi/.*)$ - [L] RewriteRule ^(.*)$ ComicPub/ComicPub/dispatch.wsgi/$1 [QSA,PT,L]Does that work?

Usually the best way to troubleshoot a site is to try to decipher the error messages and track down the problem. Just going on memory here I did a little googling for you and I think this might help https://stackoverflow.com/questions/35351134/mod-mono-asp-mvc4-error-system-security-securityexception-couldnt-impersonat It suggests commenting out the compiler entries from Web.config Since your site is no longer throwing the exception I may not have googled for the right thing. If my memory is wrong and that isn't the error you're getting let me know and I'll try helping some more.