wolstech

Is there a reason you need so many connections? Most users who see this error are seeing it because their code doesn't properly close connections when it's done using them. Our limit is I believe 4 concurrent connections per user.

CNAME setup should work on free CF accounts just fine. It must be done through cPanel though since it uses our nameservers instead of theirs. You won't even see mention of it on their website. I don't know much about it though since I use full zones myself (much more powerful and flexible if you don't mind the nameserver dance to add domains). To set up both domains on CF, you just treat them as if they weren't related. CF doesn't know they're on the same account or how they're added, and couldn't care less if it did. It just needs to know they're both hosted here. Set the addon domain to our servers and add it so it works (you've done this). Now go back to CF's website, and set up CF just like you did for the main domain. Create a zone for it, copy the DNS settings, then change the addon domain's name servers.

This support request is being escalated to our root admin.

We're looking into the cause still, but no need to worry about it. The two outages are believed to be related though. The first outage was due to data center power outage caused by a direct lightning strike. The second outage was the server crashing because it ran out of memory (we don't know why, but corruption from the improper shutdown is a likely cause).

Yeah, I prefer the CF website too. Just figured I'd mention it since some users like it for the "CNAME Setup" it offers (which lets you have CloudFlare without messing with changing nameservers). The CNAME Setup option is completely incompatible with the CF website though, and in fact actually bars you from using the CF website if you pick it (it just says you must manage through cPanel).

We have CloudFlare in cPanel now too, so you don't even need to log into CloudFlare separately if you don't want to. If you use the cPanel plugin for CloudFlare, the "Full zone setup" option is functionally the same as doing it manually through CloudFlare.

That account is not suspended. If you see a suspended page, please clear your cache.

Unblocked.

Your account was suspended for inactivity, because you haven't logged into your account in the last 30 days. To reactivate your account, please visit http://www.heliohost.org/renew. To prevent this from happening in the future please remember to visit https://heliohost.org/ to log into your account at least once every 30 days. If you are still seeing the Account Suspended page after renewing your account, please clear your cache.

65.19.143.6 is the shared IP. Important ports are: Port 21 FTPPort 25 SMTPPort 80 HTTPPort 443 HTTPSPort 2083 cPanelPort 2096 Webmail.

Seems to have had a clean start too. I don't see the typical load spike that comes with rebooting a server, but then Tommy also isn't overloaded to begin with, so it's possible it passed faster than the monitor could catch it.

Tommy is down. He quit sometime around 3AM EDT for some reason. Follow https://www.helionet.org/index/topic/29691-tommy-down/?view=getnewpost for updates.

You can't log in because Tommy is down. https://www.helionet.org/index/topic/29691-tommy-down/

Seeing this the first major Tommy outage I can remember, I'd just wait to have it fixed. By the time you could have a Ricky account running, Tommy will likely be fixed. Krydos is the root admin who maintains the servers.

I think that pretty much explains how useful this program is when run here...the program relies heavily on exec() to actually perform SVN operations since PHP doesn't have any native SVN extension/commands. Since we don't allow exec() here, the software simply won't work to any meaningful capacity.

It's not...why do you think that?

We should wait for Krydos to fix it. It's probably going to be something simple, such as corruption from that power outage Monday night (lightning strike caused our Monday night outage), or abuse of some form that caused him to freeze or crash. If the hardware had died, this forum would be down too. It lives on the same physical server.

Looks like tommy died a few hours ago (~3AM EDT). Escalating.

That would be due to our repairs after the outage. HE's data center got struck by lightning last night and caused a power outage, which corrupted a bunch of stuff because the servers weren't shut down properly. I know a password database had to be restored, though I don't know if that applied to Tommy. If so, that's why your password un-changed after the outage. Just go ahead and change it again.

Thinking of it now, I've only ever tested against localhost for those, so quite possible. I figured 8080 would work since it's a common secondary port for Apache, but I hadn't tried that one myself.

You can actually skip the .htaccess entirely and set these through cPanel: https://tommy.heliohost.org:2083/frontend/paper_lantern/err/index.html

Please use a common port such as 21, 25, 80, 443, 2082, 2083, and possibly 8080 for your outbound socket connections. We do not allow inbound custom ports at all.

Good to see the password reset fixed it for you. Marking solved,

Unblocked. It was blocked for failed imap logins, which means something is likely checking email using the wrong password.

Phishing accounts cannot be unsuspended. Please create a new account.