All Activity

Your logs are mostly 503 errors, which is due to an ongoing issue involving high volumes of traffic against our webmail service. We're working on mitigating that now. Note that this is different from 502 bad gateway, which is normal when Apache is restarting on the server. That happens approximately every 2 hours and usually lasts 5-10 minutes on Johnny. It's faster on Tommy, and currently doesn't happen at all on Morty due to newer hardware and having so few users and domains on Morty. Static pages will always be fastest because there's no server side scripting, and will typically not be affected by 503 errors. InfinityFree's service is faster for a few reasons: They have a massive for-profit corporate parent company (iFastnet) with huge amounts of money and can afford millions in server costs, so servers aren't crowded. We're a tiny nonprofit with an operating budget of <$10k/year that owns our equipment and has no corporate parent. We can't easily afford more servers. Infinity Free is artificially crippled. Those restrictions tend to mean people don't stick around for very long, and they can't run larger applications if they do. Our free Johnny service and the one-time-donation Tommy plans aren't. To give you an idea, 96% of our shared hosting users are free users, or are one-time donors who donated as little as $1 for lifetime service.

The funny thing is that if I do not have loaded the web page, the default page always loads at first without any delay, but if I upload my web page, many times it takes up to 20 seconds to load and many others directly gives error and no problem of the uploaded page, because when he decides to charge, he does it correctly. I know it’s a free service, but for example Infinityfree is also free and doesn’t have those problems.

Sure. Account reflux has been unsuspended. It may take a few minutes to work again. The other account can just be abandoned. It will delete itself in time since it's suspended. If you'd like to request it be deleted, please post from its matching forum account and we can do that.

I received a system notification about multiple accounts created on the Tommy server. I actually ended up creating two accounts, but I stopped using the primary one after I created this secondary account. I'd like to make this account (username: “reflux”) functional and deactivate the other one, is that possible?

WSGI control access has been enabled on the domain tripleespress0.helioho.st. To restart your Flask app and load new code changes in simply edit /home/tripleespress0.helioho.st/httpdocs/subscriberInfo/flask.wsgi. Adding a blank line, removing a blank line, adding a space, or removing a space are examples of editing the file. As long as the last modified timestamp changes it will clear the server cache. Let us know if you run into any issues.

You can use https://webmail.(yourdomain.com) or you can use external software such as Mozilla Thunderbird.

This support request is being escalated to our root admins.

Could you grant me WSGI Control Access for the following: - username: tripleespress0 - server name: Johnny - domain name: tripleespress0.helioho.st Thanks, Angel

Yes

Hi Team, I have been searching for a solution for the below problem appearing in the logs. I have a flask setup and I am calling the api from another domain using javascript. Very often, I get the below error and I wanted to know if there is a known cause and solution: Please let me know if you need more information. Thanks and regards, Yashveen

It doesn't look like you have a hosting account. Would you like your forum account deleted?

Hello, It seems i cannot acces my mailbox. I am probably doing something wrong. I did read the documentation and searched for some tutorials online. How can i acces the mailbox? Maybe i have some setting wrong? Thank you!

Please delete my account. Thank you

oh I see, I get it now. thanks for that insight @wolstech!!

I have uploaded via FTP all the web page that I designed in php and I have created the database. When I access from the internet to the page takes too long or even does not get to load giving error 502 bad gateway nginx. What’s the problem?

Morty Apache restarts take between 4 to 9 seconds over the last month, so it would be impossible to see a 504 error because the restart needs to take more than 30 to 60 seconds seconds for it to actually timeout. During a 9 second Apache restart the page would just spin for an extra couple seconds during loading, and then display the website without any error. Nobody is ever even going to notice that, and it would be indistinguishable from your internet lagging slightly. Right now Morty has 608 virtualhosts so we would likely need to triple or quadruple that number in order for a 504 error to be possible. 503 error on a PHP script is likely the PHP script running for too long and getting killed. Perhaps try benchmarking your PHP scripts and see how long they are running for. Your load looks fine so we could increase your PHP timeout if you need, but it might not be necessary if you can optimize your code to not have to run for so long.

The discord/dmarc/dkim/atproto ones have names, so you need to actually ask for, for example, _atproto.tenkyuu.dev to see it. The file you posted is only the domain itself (i.e. records with no name or with the name of the domain). The root domain shows the same thing as your file: https://dnschecker.org/all-dns-records-of-domain.php?query=tenkyuu.dev&rtype=ALL&dns=google For the named ones, they do appear if you specify their names. For example, the _atproto and _discord ones: https://dnschecker.org/all-dns-records-of-domain.php?query=_atproto.tenkyuu.dev&rtype=ALL&dns=google and https://dnschecker.org/all-dns-records-of-domain.php?query=_discord.tenkyuu.dev&rtype=ALL&dns=google This is the expected behavior for the records provided.

502 is related to Apache restarting and is normal. Should occur approximately every 2 hours and usually lasts 5-10 minutes. If you're unable to tolerate this, you would need to move to Morty, where the Apache restarts currently take under a minute. Note that on Morty, you'll get a 504 instead of a 502 during an Apache restart. 504 on Tommy can happen if your script takes too long. It basically means nginx timed out waiting for Apache to return content, which is usually caused by your website's code taking too long and not finishing. This can be caused by many things, including high server load or badly written code. 503 Service Unavailable is an unusual error to get on Tommy though, and I do see a few instances of that in your logs. I'm not sure what would cause this error specifically. Perhaps Krydos would know?

Hi ! I noticed numerous 502 - 503 - 504 errors on Tommy since several days. Any idea ?

Hi @wolstech, I just rechecked my DNS records recently using the DNS lookup by dnschecker.org. I'm curious why I haven't seen a lot of records I want to change? You can check the txt file attached that I got from that site. tenkyuu.dev-records-ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyzLwCrqAjJSxGhXPm.txt Thank youu!!

Your account has been reset and you should receive a link to recreate your account shortly.

its a me problem, the problem lies in permissions (folder creation) and i solved it

i would like a full reset thanks username: gdjkhp

There is a Flask tutorial here which also explains how to request any additional Python modules you may need: https://wiki.helionet.org/Flask I notice you also posted this in Discord an hour later. All helpers are volunteers so asking the same question in 2 places risks duplicate volunteer effort if 2 people give you the same details: https://wiki.helionet.org/FAQ#Where_do_I_ask_for_help? Please check out the above links and let us know if you're still having trouble. 🙂

WSGI control access has been enabled on the domain gdjkhp.heliohost.us. To restart your Flask app and load new code changes in simply edit /home/gdjkhp.heliohost.us/httpdocs/flask.wsgi. Adding a blank line, removing a blank line, adding a space, or removing a space are examples of editing the file. As long as the last modified timestamp changes it will clear the server cache. Let us know if you run into any issues.