https://gopweet.akaimaple.com.tr Website URL
ERR_CONNECTION_REFUSED Error Message
As i said my website give ERR_CONNECTION_REFUSED error randomly while refreshing the page or going to different page. How can i solve that problem?
for me the site shows no errors and allows me to directly go to it, maybe this is a personally network issue.
3 Likes
I experience exactly the same problem. Is there maybe some other “hits limit” on smaller time periods than one day, say per second or per minute?
My hosting volume is vol2_8.
1 Like
I tried on different networks and locations that’s not the issue.
Please, I would really like to know the reason behind this. Is it a characteristic of infinityfree, something to learn to live with? Or is it a temporary problem with my hosting volume that I could expect to resolve in the future?
I don’t see any issues on my end. I can tell you it’s definitely not a “characteristic of InfinityFree”, because most people don’t have the issues you’re describing. As to whether it’s a problem related to the hosting volume or IP your site is on, I don’t know, because I can’t exactly go and bother a server admin for an issue I cannot confirm even exists.
5 Likes
Thanks for taking time to respond!
The trouble is it’s random behavior, as original poster reported. About every 10th or 20th request ends up with this error, whether it be a normal page opened in a browser, or an XHR request from JS, it simply does not matter. The only difference is that when it is a normal page, browser reports the error over entire window and retries on its own a few seconds later when the request passes. It was also tested from two different physical locations with two different internet providers, with three different browsers on two different computers. This strongly suggests it might not be a problem on my side.
So, ok, I understand your point. I will investigate this further on my own, but I will still assume you would like to be aware of the potential problem with your hosting.
1 Like
Reports like yours can be a good indicator of issues that may have slipped our own detection, so if you see something that looks like a server issue, it can be helpful to bring it up. But if there is a server issue, you would usually see more than one website having the issue, and I don’t see anything to suggest that’s the case.
One option you could consider is to create a new hosting account and move your website to it. A new hosting account would likely be set up on a different server that doesn’t have this issue.
6 Likes
Thank you once again for a thoughtful response! Your idea of testing with a new hosting account is actually quite good.
3 Likes
First, I must correct myself about the frequency of this error. The issue actually comes and goes, there may be several minutes and hundreds of requests without any problem, and then they can come in groups so that about every 10th or 20th fails. This makes it very hard to debug.
As suggested by the admin, I did some (rather intensive) testing on two of my infinityfree hosting accounts simultaneously (two different browsers on the same computer, with two tabs in each, switching between both browsers and my accounts, exactly the same copies of html and php on both). And the result is that the first (vol2_8) behaved the same, randomly reporting refused connections, but the other (vol14_2) worked flawlessly, not a single failure!
Additionally, I managed to locate how the connections get refused - it’s by the browsers. In Edge/Chrome it’s called “stalled”, in Firefox it’s called “blocked”, both suggesting something about stalled/blocked “by/in the queue”. The reasons for this are vaguely described in documentation, presumably the number of already opened connections, but I was not able to conclude what exactly happens. Unfortunately, the network logs that developer tools in browsers provide are not enough for this task. I would need to make some lower level network logs to see the dynamics of actual underlying TCP connections, but this just goes beyond my interest, at least for now.
I am aware of that and it goes without saying - one account working in one of my test sessions does not prove anything. It is practically impossible to prove something does NOT happen, but more testing will surely occur in the following days. I just wanted to present my findings, so the admin has some more material to decide how much he should involve himself. 
1 Like
I’m sorry for the delay.
I had a server admin take a look yesterday. It appears that this server is experiencing a higher load than most servers because a large number of new accounts are being set up on it. This can happen with newly added servers, because the account provisioning system will see that this server has fewer accounts assigned to it than most other servers.
The server is now configured to no longer accept new accounts for a while. This will cause the load to go down as the server calms down, which will solve the stability issues you’ve been seeing.
8 Likes
Thanks!
2 Likes
For me the website works perfectly
Just to let you know that after five days the situation is not much better. I’m not complaining - we actually took advantage of this issue to better test our code against random network errors that actually rarely occur in real life. If the issue persists, we will just switch to another account hoping for better server.
However, since our plan was to upgrade to ifastnet premium hosting after our initial development phase (which is the basic idea of your site, I guess), I would like to ask who is responsible for overloading the servers with new accounts, in other words, should we expect similar issues with ifastnet too, or this stays only on infinityfree?
iFastNet controls the account provisioning system and ultimately chooses where an account is set up. This.
No, I don’t expect you’ll have similar issues on premium hosting, for a few reasons.
First of all, free servers are loaded with a large number of accounts to keep costs down. Premium servers don’t get loaded nearly as much. So servers getting a few more accounts than usual don’t immediately cause overloading issues.
Besides that, the premium hosting infrastructure in general works very differently, which (I assume) includes the account provisioning system. How servers are selected to place accounts on may be so different that an issue like this could not occur.
Finally, many people sign up for free accounts and then abandon them. This is what causes load spikes when a large number of new accounts are setup on a server. I don’t expect premium hosting to exhibit similar behavior, because having to pay for the service means people are less likely to create accounts they don’t intend to use.
5 Likes