Posts: 12
Threads: 4
Joined: Jan 2022
Reputation:
0
Does anyone else have issues with air-source.us? For me, service is unavailable.
Posts: 1,610
Threads: 341
Joined: Nov 2005
Reputation:
2
Appears to be a server issue. Tom or Joe will be looking at it.
Posts: 3,378
Threads: 314
Joined: Nov 2005
Reputation:
0
Hello,
Is it working for you now? It appears some were able to view the site, while some others not. Hopefully our host has cleared this up now?
Posts: 12
Threads: 4
Joined: Jan 2022
Reputation:
0
07-03-2025, 09:53 PM
(This post was last modified: Yesterday, 02:09 AM by AS 387 Harry Perkins.)
Unable to view and it does not allow AAS2 to communicate to the server.
Posts: 3,378
Threads: 314
Joined: Nov 2005
Reputation:
0
Yesterday, 11:52 AM
(This post was last modified: Yesterday, 12:15 PM by AS 2 Tom Little.)
Hello and sorry about the issues you're all seeing. Can you please get a screen snip of the error message you see or at least copy/paste the text of the error) and provide the date/time (GMT) the next time this happens to you? I started dialog with our host but will need more details to give them. I also asked if they can check the logs, which I cannot seem to access. Thank you.
Posts: 3,378
Threads: 314
Joined: Nov 2005
Reputation:
0
All - thank you for your patience and for those who have been reporting the on and off issues with the website. This is a rather strange and harder to trace problem, because it does not seem to affect everyone, and the forums appear to work just fine but the "main site" does not (when the issue arises).
I explained this in a conversation with the host yesterday and I have already received some great feedback and help from them.
1. As you can tell, when we changed to the new forums, I put our new forums on a sub-domain instead of the main site (forums.air-source.us). This was on purpose, the main reason was for testing different versions of php. This is also the reason why the forums work just fine, when the main site may be having problems.
2. Our server host identified from the logs that it seemed to be an out of memory problem due to bots/crawlers. They have assisted in banning the IP's of the top offending crawlers. This alone should help the problem.
3. Our host also gave me some pointers to control the other crawlers, and I have already implemented that fix as well.
So at this point, it seems that *hopefully* the issue may be resolved.
If for some reason it happens again, please provide me with the date/time that you experience the issue (GMT), screen snip or copy/paste text of the error, and the page you are trying to view when the problem occurs.