Piotr GRD

I start to be mad for my service provider. Previous IP I have had for almost two years, the last one for two weeks and it has been change again. I hope new one will last "little" longer. That's why my service hasn't working correctly for last ~12 hours. I think that being on your whitelist isn't really needed, but if you wish to put my new IP - currently used for this post - on it, then thank you in advance.

Hello So far so good, but last time there were some problems, so now I ask you in advance. Unfortunatelly, two days ago my IP has been change again, like a year ago. This is the reason why there was no results displayed on my monitoring page. Please, @HelioHost admins, put my new IP adress - which is the same that I use now here on the forum - on the whitelist on your servers. Thank you. Last time, my monitor was banned without whitelist. Now it's not, but who knows. // Piotr

TZ works for older versions of PHP, in newer versions date.timezone. In my PHP scripts I have: putenv("TZ=UTC"); // enough for older PHP versions date_default_timezone_set('UTC'); // required for newer PHP versionsI set it inside of my scripts as I use two or more timezones at once (for displaying two time graphs). In .htaccess, If I'm right, it will looks like: php_value date.timezone "UTC"

Hi I'm sure you have your own warnings about such things, but in next two weeks or so there may be a problem with disk space in /home1 on Tommy. Some action will be required. /home on Johnny is less predictable (by looking at its 100 days history), so it may (or may not) need some attention, too.

With "so long scripts" you would have a problem even on a paid shared webhosts, maybe not every time, but quite often. Make it short and incremental, it's not hard if you're familiar with coding. For external cronjobs you can even use some free services. A good reliable example that I use is Cronjob.de - it works very well with no problems for many years for me, you just need to login once every 8 weeks to keep the free version running.

"White bar" doesn't mean "down", but "no info". ; ) Thank you and I'm sorry. As I wrote it in the email - this is unfortunatelly the result of my procrastination, I'm loosing my personal war with it in last few years. My old monitoring script - started in 2009 - require some small modification to *properly* check the SSL connections, otherwise it reports false (longer than in reality) connection times (the way it handles the "handshake" OR the way it verify the certificates has something to do with it). The required modification is small, however because of mentioned procrastination it takes me weeks already to do it and may take even more. I will try, but I can not guarantee any timeframe. The Heliohost main page is also served through SSL, but in this case I've "temporarily" switched to check the /classic/ version of it, still through normal HTTP, until the required update of my script. Thank you and I'm sorry for any inconvenience.

I, personally, don't need a backup from Ricky, but to check if it works I've visited the link and... And I've got email with link to the Stevie's backup. The one from December. Possibly there is some issue when the username and email used on Ricky is the same that has been used previously on Stevie. For me this is not a problem, but you may want to check if other users won't be affected with it.

Thank you. : ) I've deleted false results of my monitoring for last few days. And from now on everything should work fine. Until Stevie will ban me in the future. ; )

[bump] Hi. It seems that my IP - the same I'm using now - has been banned on the re-opened Johnny "v3.0" server again. Could someone, please, put it on a whitelist, so my monitoring will work again?

Did you try to renew the account with "account renewal" tool? In the menu on HelioHost main page it's Support > Scripts > Renew.

OK. Monitoring of server "Tommy" has been added. In the mean time - a week ago - I've also modified the way FTP access is monitored: now my monitor tries to actually log in and get the list of files. This way the results are more realistic. Previously only connection was tested without checking if it's possible to actually do anything with the files.

Eddie has started to be monitored automatically as soon as you've moved Heliohost main page and Helionet forums (to be strict: monitored is Cody, which is on Eddie). For Tommy I've started to check the HTTP access few days ago, though it's not displayed on my page, yet. I'll enable it fully as soon* as you'll let me create test account on it. * this may take 2-3 days, depends on my spare time and inclination

Thank you very much, Byron. I've turned everything back on on my side, works for 14 hours already, so should be fine. Thank you and sorry for any troubles.

Hi and thank you. : ) At December 28th my monitoring has stopped for ~28 hours and started working again at December 29th, however from a different IP address. And after few hours unfortunatelly it has been banned on both - Stevie and Johnny - HelioHost servers. I've noticed this after... two days (because for first few hours it was fine I thought it will be fine all the time and didn't check it earlier), but I didn't want to bother anyone during the long new year weekend. However if you've already posted about this... I need to ask one of the @HelioHost admins to UNban my new IP address - which is the same which I use now here on the forum - and maybe even put it on the whitelist. Thank you. : ) My "monitor" (and "server time") won't start automatically, I will have to turn it on again. "Disk space" and "DNS checker" still works from different server.

If so, then I'm surprised that after so many years there is still no any blacklist which would contain "ns1", "ns2", maybe also "smtp", "pop3" etc. kind of subdomains, any that could potentially cause the problems.

I've just spot that there is a small problem with the DNS entries for ns1.heliohost.org. The glue record says that ns1 is on 65.19.143.3 and ns1 itself says the same, but (since Monday, October 5th, I guess) ns2 for some reason says that ns1 is on 64.62.211.131. 65.19.143.3 works fine and do answer for the DNS queries, but 64.62.211.131 do not. I think you should fix the entry for ns1 on ns2. It looks like the problem from the past with various entries being not synchronised, but maybe that's just single error and other entries are fine, I didn't check any.

"REFUSED" is what I and anyone have from ns2 when asking for heliohost.org or www.heliohost.org - just like for any UNexisting domain/subdomain. And from ns1 there is simply no any records returned except "NS" (no A, MX etc.) Oh! And while there are no records for ns1 and ns2, either (except of the "glue records" on root DNS servers) then sometimes even ns1./ns2.heliohost.org can not be found and some tools/browsers don't know where to send the DNS query. For now I've "hard-coded" the IPs of ns1/ns2 in my "DNS Checker" tool and I've added the "rcode" in the reply. I didn't ever play with BIND so I won't help you much, unfortunatelly. Zone file looks OK for me, but I can't help with entries in the configuration files. If you think you've done everything correctly... did you restart BIND after doing all these changes? (Sometimes most obvious thing is forgotten.)

I doubt it. But you can use your "hosts" file (where it is depends on what system you use, ie. windows/system32/drivers/etc/) and put in it the following entries: 64.62.211.132 heliohost.org 64.62.211.132 www.heliohost.org When you'll find out that everything is back to normal - remove this from "hosts" (do not delete the file itself, just the entries inside).

You can use your "hosts" file (where it is depends on what system you use, ie. windows/system32/drivers/etc/) and put in it the following entries: 64.62.211.132 heliohost.org 64.62.211.132 www.heliohost.org When you'll find out that everything is back to normal - remove this from "hosts" (do not delete the file itself, just the entries inside).

At the beginning that was more than just DNS problem. If you were able to forget the DNS (using the "hosts" file for example) then there was no main page but just error stated about the problem with MySQL and 403 error for various other URLs. At the moment main page seems to work fine again. Except the DNS issue which seems to be the last thing to be fixed.

Not a week. ; ) It started at early Friday (for Asia and Europe timezones) or late Thursday (for America timezones). http://heliohost.grd.net.pl/monitor/archive/?2015-07-10

Your account is on the server "Johnny" which is in general less stable and was unavailable at the time of your post. More about the issue you can read here: http://www.helionet.org/index/topic/17837-johnny-down-again/ http://www.helionet.org/index/topic/17840-johnny-online/ You can also follow up the accessibility of the servers here: http://heliohost.grd.net.pl/monitor/

Make sure you do visit /frontend/x3/index.phpcp URL of the main page in cPanel, only this one will prolong the validity of your account. The /frontend/x3/index.html URL will not.

Then add what Gourlaykid wrote you in the .htaccess file. To see this file - either if you use cPanel file manager or any FTP client - you have to enable visibility of the hidden files - what Shinryuu wrote you about.

This may (or may not) be the general problem with "Johnny" server, on which your account seems to be located. It is highly unstable. You may view the situation of it ie. on my monitor (link in the signature).