what the hells a fsockopen error & another related question
 

my host, only that specific server im on (virtual hosting) has this error, or at least my comus thumbs domain.

And something else, when i type in a domain with subdirs on any of my domains on my host (that also got an index.html file) with www and without a slash on the end, like:
www.mydomain.com/freesite1
it goes to:
mydomain.com/freesite1
so without the www.

Before the trouble started with that fsockopen error this wasnt the deal, any url on my domains u typed in with www it always kept the www, no matter what. I think its related to that fsockopen shit. Anyone know what the hell is wrong and how to solve this? Or what i gotta tell the host support? Because they apparently have no idea too.

thats gotta do with php.ini wasnt set right, do a search ive posted before on this, and to be honest if your host doesnt know what it is, you should change hosts...

Or more likely than not they forgot to enable sockets when compiling php and now they need to update it. Tell them to enable sockets when recompiling. We have full support for Comus on our host. Give me a message if you are interested.

yeah its strange they didnt know it, i had alot of convos with them on icq plus a support ticket thats already unanswered for two weeks.... ill hit them up later and tell em what you guys just told me. Thanks.

That www. thing is an apache issue.
That php issue: post the error.

Fsock error is a File Socket error. Means a script tried to open a file, either locally, or most likely, on another server and it couldn't do it.

Comus's site has been having some trouble the last few days. I've been getting occasional errors when I first go into comus admin and it tries to contact their server to check license and get the welcoming advertisements. You maye just be seeing that. It will not hurt anything (or at least it shouldn't).

To know what the problem is with the WWW stuff you need to be more specific about what exactly is happening. The WWW won't just get dropped by the server. You have to be clicking a link or be getting forwarded by a script that is dropping the www subdomain. If the server was configured wrong it would not work with WWW at all, you'd get a DNS error.

Where exactly are you, and what exactly are you doing when the www suddenly gets dropped?

Ok lets talk about the www. issue, this is exactly what happens:

1) I open the browser IE or firefox.
2) I type in the url of on of my sites in the address bar, lets take:
www.hoehoehoe.net/gals/0050teenblondeshaved
for example. Type it exactly like this in the browser.
Also with http like this:
http://www.hoehoehoe.net/gals/0050teenblondeshaved
will do too.
3) Press enter, then it goes to http://hoehoehoe.net/gals/0050teenblondeshaved/

And this happens with every index file in subdirectories of all my sites on that server.

so theres no WWW anymore.

When i put the slash behind the url i wanna visit it does leave the www:
www.hoehoehoe.net/gals/0050teenblondeshaved/
http://www.hoehoehoe.net/gals/0050teenblondeshaved/