wolstech

Unblocked.

Unblocked.

Unblocked.

The suspension is for too many emails, which isn't surprising. You are more than welcome to send such emails, but there's a limit of 50 per day to help keep our servers from getting blacklisted. If you'd like a limit increase, please post an example email and how many you expect to send per day. Normally I'd also ask for email address source and unsubscribe info, but your use doesn't email outside users so is not relevant. Unsuspended.

It's banned for phishing. Why do you have a fake bank website on your account if you are not trying to steal information? There's zero legitimate uses for such a website except maybe a development or test platform, and if that's the case, it should have warnings on it advising users that it's for demonstration only/not a real bank. Please create a new account and don't host that here again.

It's archived but the archive is missing. Krydos usually can somehow restore these. I don't see the file anywhere on either server...

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

Unarchiving...

Shebang line is wrong. Perl is here: /usr/bin/perl

What's the shebang line in the CGI file? Also, make sure your file has unix line endings. Windows line endings will cause these errors.

The folder had the wrong owner (was owned by nobody for some reason). Your domain is working now, and I can see the files in file manager now as well http://dopplerdave.info/

That account is now created

The domain tommygun.heliohost.org has been cleaned up. Invite sent. Please check your email for the invite to complete creation of the account. If it fails again, please let me know and I'll have Krydos manually scrub the domain. The killdns script has had issues clearing out domains on a few accounts...

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

Unarchiving...

Please check your PMs.

I'll assume he deleted it because no account with that domain exists.

That’s weird... Let’s see what Krydos says. Changing an IP should not cause that error. If it weren’t configured for remote access, it’d be an access denied error, so it’s not that...

I’ll set this up when I’m at a computer later today. You’ll receive a PM with information once set up.

This is usually caused by badly-written code that doesn’t close its connections when it’s done with them. I assume you wrote the program yourself? If so, be sure your code is closing the database connections when you’re finished with them. Many times I find code that opens a new connection for every query, never closes them, and fails when it hits the connection limit. You should either open, query, close every time, or open at the start of the script, reuse the single connection for every query, and close it at the end.

A Whois response and an actual dns response are two separate things. They can say whatever they want on the Whois, but unless dns actually answers with the NS records, it won’t work. Your registrar is probably leaving themselves as authoritative and improperly delegating the domain. Contact them and ask that our NS be made authoritative for the domain and their NS be removed entirely. If they say they can’t, then you’ll need to find a new registrar.

That account is working. http://ubitech.heliohost.org/ Please sign in here: https://tommy.heliohost.org:2083/ instead of using our website. The account record is just missing from one of our systems, so our website won't work for you for the time being. I'll fix that when I'm near a computer.

For number 1, if you mean change the whatever.heliohost.org after you signup, then yes. You can use the main domain change script to do that. As for number 2, no, at least not in your own, A normal account can only have one heliohost.org subdomain, and it always points to public_html. That said, an admin can create additional ones pointed to other folders if you request them, there's just no user interface for doing it yourself. If you mean you want to create sub.whatever.heliohost.org, use the subdomains page to do that.

This is a common issue around here, and it's always fixed in the Java code. 99% of the issues are related to not naming the war file with the username_ on it before you deploy it. Other than that, I know people have had issues with the context path before (the way our system works causes it to guess wrong on what this is). I would start by rebuilding your war, naming the output file tujiorg_tujiorg.war. Then upload and deploy that file. That fixes most people's issues with this. If that doesn't help, you'll need to check your code to ensure you're using relative links. You don't want the code to include the domain name when generating links (because it can and will get the domain name wrong, resulting in links to localhost...). If I remember right there's also a way to force the context path by setting an attribute in one of the XML files, but I don't know Java much at all and might be mistaken.

Unblocked.