-
Posts
17,334 -
Joined
-
Last visited
-
Days Won
639
Everything posted by wolstech
-
Domain added. It can take up to 2 hours to finish setting up. Please make sure DNS is configured using our name servers (ns1.heliohost.org and ns2.heliohost.org), or for external DNS by adding A and AAAA records pointed to the IPs shown in Plesk. It currently shows as not being hosted here.
-
[Solved] Why my account is suspended?
wolstech replied to benitezrepolles's topic in Suspended and Queued Accounts
Unsuspended. It may take a few minutes to work again. -
You'll need a VPS for docker. Not sure about Deno, but even if it were available, the load limits would like get you suspended repeatedly if it's anything like nodejs in terms of resource use.
-
That's normal if you haven't installed an ssl certificate. You can fix it by telling plesk to get you a free certificate from let's encrypt, and then waiting two hours for it to take effect.
-
Changed. Give it 2 hours to take effect then try again.
-
Deleted. Also, in the future, it is possible to request your account be reset without making another one manually. Creating a second one to do this is unnecessary and may actually subject you to suspension for having more than one account.
- 1 reply
-
- 1
-
Account has been reset. Please check your email for a link to create a new account. You pick a domain during that process. If you need a copy of your old account's files, they're available from https://heliohost.org/backup/
-
Please work with Krydos on this in your original topic: https://helionet.org/index/topic/60365-krydos-nixos-as-bare-os/
-
[Solved] Account suspended due to high load
wolstech replied to feedora's topic in Suspended and Queued Accounts
The only logs really available are those in Plesk. I was kind of confused when I saw this account causing tons of load a few days ago, as I couldn't find any obvious source for it. An FTP connection shouldn't cause much in terms of load, though perhaps its the fact its every 10 minutes that's an issue. It was for the memory limit being exceeded, which FTP uses basically none of. For now I'll just unsuspend you. If this load continues, we can have Krydos investigate it for you. Unsuspended. It may take a few minutes to work. You can watch your load here: https://heliohost.org/dashboard/load/ -
[Solved] change added domain to become MAIN DOMAIN
wolstech replied to websys's topic in Escalated Requests
The DNS zone is corrupt on the name servers. It has no zone file but also claims to exist and be owned by nobody. Escalating to Krydos. ---- Technical stuff: No errors thrown yesterday during the removal of the domain or DNS. The subsequent main domain change through the admin tools also worked fine without error but it looks like the DNS zone didn't set back up correctly and broke instead. This is what I see when trying to check the zone file on the server. No zone file found, but also can't add it or remove it. root@brody [/var/named]# ls -l | grep cleosai.site root@brody [/var/named]# whmapi1 adddns ip=65.19.141.67 domain=cleosai.site --- metadata: command: adddns reason: Sorry, the domain cleosai.site is owned by another user (nobody) result: 0 version: 1 root@brody [/var/named]# /scripts/killdns cleosai.site Unable to remove zone: “cleosai.site” on brody. Unable to remove zone: “cleosai.site” on cody. -
It looks more like your domain didn't set up correctly because of the domain you picked. Do you mind if I change the domain to just mingrkli.helioho.st instead? I'm hoping that will fix it, and if not we can just reset the account for you and let you sign up again.
-
Those functions specifically are only applicable to Plesk when it's installed on windows server. Ours is running on Linux. We've also turned off some of the functionality like adding domains since it doesn't integrate with some of our backend systems at this time. This functionality will be added back at some unknown point in the future if we can get it to integrate.
- 1 reply
-
- 1
-
[Solved] change added domain to become MAIN DOMAIN
wolstech replied to websys's topic in Escalated Requests
Domain removed and readded as main domain. It will take up to 2 hours for everything to work again. -
[Solved] change added domain to become MAIN DOMAIN
wolstech replied to websys's topic in Escalated Requests
In order to do this, we have to remove it and re-add it. Note that this will also cause the content to change as the main domain will use ~/httpdocs instead of ~/cleosai.site as the document root. Is this OK? -
Domain added.
- 3 replies
-
- main domain change
- domain
-
(and 1 more)
Tagged with:
-
It is technically still a thing, but nobody has qualified in years. Most of the support these days is on discord, and discord traffic doesn't qualify. It's kind of a relic of days gone by at this point. Also useless posts (filler, nonsense, a post with only a smiley, etc.) don't count, nor does spam or other removed posts. Last I checked I think the entire "other discussions" forum was also excluded. Note that we may manually count the posts when approving you to verify the posts have not been deleted and are of sufficient quality.
-
We were a post to host service back when we first started in the middle 00s. There used to be a point system. I don't really know the details though, it went away before I really started, and I've been here since 2012 (technically 2009 if you include my first account that I abandoned after a few months). I have no idea which of the testimonials you're talking about, because those are random and change each time you reload the page. I know there are some really old ones from when we first opened though still circulating in there... when I loaded, I saw one referencing Stevie...a server we haven't offered in years (Tommy was his replacement).
-
Added.
-
Yes, it was for exceeding the memory limit.
-
Added. Please make sure you configure DNS, the domain is currently showing as not hosted by us. The domain may take up to 2 hours to work.
-
Krydos can answer this for sure, but I wouldn't be surprised if the answer is "not supported" since it would require he install this manually if you wanted to use an OS that's not listed.
-
Kind of. We didn't have as many users on the servers (especially Tommy) at the time, and I believe we also had a user recently who asked for some astronomical number of domains. Since every domain added slows the server down, it's not fair for a few users with a ton of domains to impact everyone else, so we added a limit. The same performance impact associated with domains is also why domains that are added but not actually hosted here now disable themselves after a while. Disabled domains have no performance impact.
-
They're limited primarily because every domain added to a server decreases the performance of apache and makes it take longer to restart.
-
<Placeholder> <Name> $SERVER$ </Name> <Content> /home/site/dbs </Content> </Placeholder> This path is wrong. Looking at where the file is currently, the path should be /home/srboylan.com/dna-tree.srboylan.com/dbs I edited the path in includes.php and it looks like its trying to work now. I can't test further because I can't log into it. I also commented out an invalid die() statement from the top of router.php that was responsible for the "unexpected variable $router_debug" message (the error was due to a missing semicolon).
-
Changed.