Piotr GRD

Quote: "You are user number 10 of 50 allowed." Good that simple restart did help. IF. If this is the bug that I'm relating to, then it appears usually when server is slow and/or some problems (even temporary, for a milisecond) appear exactly when someone is connecting and/or disconnecting. It's quite rare situation, even very rare, but obviously as Stevie is quite often slow - such bug (if it's the case in here) may appear more often than somewhere else. It's related to Pure-FTPd, as I didn't notice such situation on servers with different FTP software installed and I do monitor dosens of servers. I don't know exactly how it works and why the bug happend, however as the end user for over a year on many servers trying to connect every 2 minutes 24/7 I have such experience. It also may affect a single user on the limit of maximum allowed simultaneous connections per IP.

A friend of mine did use fsockopen, so could get all the data sent by the server to the client. Obviously all the FTP commands have to be specified correctly and sent to the server, too, using this method, so you need to know enough this protocol. A little more simple to use is cURL, but in such situation it's return only "This doesn't seem like a nice ftp-server response" for me, not the real server responce. For those who interested - my monitoring shows orange (no valid responce) for FTP in such case. Red for time-out or offline. http://grd.net.pl/heliohost/monitor/ edit: By the way - did you try to reset / turn off and on again the FTP server? Because I know of existence not that much known bug in Pure-FTPd that can cause such situation. It makes that really already unexisting connections are still considered as existing and counted to the limit. So there can be reported 50, while there is really no 50 of them. But it may be not the case in here, of course. edit2: "421" is the FTP reply code. Error message is "50 users ...". It's not 42150 open connections, just 50.

What I'm pointing is that that on old - Stevie - nameserver is still old A record for heliohost.org, on new - Charlie - nameserver is new A record already. And couple of hours ago from some location - like ie. Germany, Netherlands, California (USA) (such locations I did check) - still old (Stevie) nameserver has been queried while asking ns1/ns2.heliohost.org for the records for heliohost.org and www subdomain of it. But that's a small thing, of course, just couple of hours. ; ) I would say that it has usually such TTL that admin wants it. ; ) Ie. I use 1 hour, but if I have plan to change IP, I try to set it temporarily for 5 minutes or so, for propagation being as short as possible.

Small tip for future such steps: you could make the DNS propagation delay for the whole world much shorter with setting new IP for A records for heliohost.org on old nameserver(s) (on Stevie), too. At the moment it's too late, though, everyone's systems should use new (Charlie) ns1/ns2.heliohost.org. But couple of hours ago from some locations still old nameservers has been queried. Without changing entries on old nameservers it takes ~24 hours for everyone to access new location (if I'm right), with changing entries on old nameservers (or switching location of nameservers 1 more day before) it could take only 4 hours (with current TTLs). Just a small thing, couple of hours difference doesn't mean much. ; ) When you'll move helionet forums, though, to avoid some people posting on old, some on new location, you can set TTL for being shorter than 4 hours. At least 4 hours before changing IP itself for A record, of course, for such step having any effect. After changing IP TTL can be set for being longer again. Forgive me if you're aware of all these things and you just don't bother much for the DNS propagation being couple of hours faster or slower.

@ eSPiYa If you didn't notice - previous messages in this topic about ASP.NET being enabled are from March 2010. However recently - November 2010 - support for ASP.NET has been disabled. Read more in here: http://www.helionet.org/index/index.php?s=...ost&p=55937

Hellllooooo!..... Is anyone here?!...... Heelllooooooo!... ;D Sorry, I just had to post that. ;D HelioHost nameservers does not work for 16 hours already so no anyone can be here at the moment. I think I am the only visitor. Greetings for everyone.

Yes, it looks like. Related topic about: http://www.helionet.org/index/index.php?showtopic=7578 As the alternative you can switch (with the proper plugin) Wordpress to use some external SMTP server (even your own GMail account or whatever else service) for sending out emails instead of using native PHP mail() function and HelioHost as mail server during the time when such problems exists.

By using "search" on the forum (function which very often saves a time) I found this post: http://www.helionet.org/index/index.php?s=...ost&p=55234

Remember that there is also another alternative - if HelioHost efforts for being unblocked will fail - to use different service for email. You can configure your DNS records to use HelioHost for your website and some other chosen service for your email (ie. Google Apps or whatever else). I don't know if you can manage your MX records on HelioHost nameservers (cPanel does have such option, but might be blocked or not) but in a case you can not you can always use different namservers and configure everything on it. If you do need help with DNS configuration - after you'll decide for such step and choose a service to handle your email - I'm ready to help.

So its not possible to upload to www through ftp? (...) "www" is just - to make it simple - some kind of "alias", other name for the "public_html" folder. If you're using Windows on your computer then most similar thing will be "shortcut". Different way to access the same directory, but only through cPanel's file manager, while through FTP you see only real directory "public_html". (...) When the server is down can my site still be seen? Well... only if you got it in the cache of your browser. No. As for the license problem - is this related to the script you are trying to install?... Maybe your script needs license to be bought for being functional?

Well... I can only confirm your observations with these statistics: HelioHost Server Monitor, archive for 2010-10-20 Such problems are present for shorter or longer periods of time almost every day, following the link you can browse the results from 2010-09-26 up to today.

Just to confirm that there was quite a lot of problems, not all day, but... Turning off gzip compression may decrease CPU load - which is not the problem according to what djbob wrote - but will increase bandwidth usage. Let someone else say which would be better in here in current situation.

Check the dates in that section of the forum - first post is dated 22nd July 2008 and last post is dated 6th October 2008. So that's all over 2 years old topics. I wasn't in here at that time, I can only guess, but my assumption is: - there was some server No 1, not owned but rented; - "Stevie" has been set (own server); - on request some of the accounts has been moved in there and also new accounts were set on new server, too; - with the time being all accounts has been moved into "Stevie" and there was no old rented server anymore; - at 2010 there is another server "Charlie", not online at all, yet.

After seeing "Site Uptime" topic in this section of the forum I am posting this topic in the same place. Update as of 8/14/25, This monitor is no longer used. for new status updates please check out the new monitoring website at https://status.heliohost.org Hello everyone I would like to announce to all of you the new service that I've recently created: HelioHost Server Monitor - http://grd.net.pl/heliohost/monitor/ Bookmark or add to favourites to not forget. On this page you can check the availability of HelioHost.org servers (currently the only one server) and the time of responce just now, during last 24 hours (on main page) and through all the days when monitoring was running (by navigating in archives menu). The server is monitored every 2 minutes and almost 24/7. Monitored is access to the server through HTTP on port 80, through FTP on port 21 and access to the cPanel login page on port 2082. Additionally also availability of the HelioHost.org main page, HelioNet.org support forum and HelioHost nameservers. Apart of checking if the server is online/offline, counted is also time from the start of request to the end of receiving the valid answer from the server. Results of the monitoring are also updated every 2 minutes and displayed in human friendly graphic form, quite easily understandable (I hope). At the moment of this post HelioHost main page and support forum and nameservers are hosted on the same physical server with users accounts, so if you'll see that these pages are slow, inaccessible or return invalid responce (ie. error 500), then your own websites/scripts hosted here may (or may not) behave in the same way at the same time. If you have any questions, comments or concerns regarding my server monitor - you can feel free to post in this topic or through email that is available in the footer of my page with monitoring results. I hope that the service will be useful for everyone. Piotr GRD 2010-10-04